feat(web): connect native agents and deliver verified applications - #201
shyamsridhar123 wants to merge 1 commit into
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9efab732be
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| (target?.workspaceConnectionId | ||
| ? capability.workspace_connection_id === target.workspaceConnectionId | ||
| : !capability.workspace_connection_id), |
There was a problem hiding this comment.
When target is omitted, this now excludes every connection-bound runtime. App.tsx uses that unscoped result for realAdapters and operatingOfficeAgents, so if the runner's default machine profile is unavailable but a personal saved connection is ready, the onboarding UI reports “No real AI runtime” and hides the corresponding registered crew even though that connection can launch missions. Apply the binding filter only for target-specific dispatch selection, while allowing the unscoped status projection to include all available runtimes.
AGENTS.md reference: AGENTS.md:L14-L14
Useful? React with 👍 / 👎.
| const refreshVisiblePresence = () => { | ||
| if (document.visibilityState === 'visible') snapshotRefresh.request() | ||
| } | ||
| const presenceTimer = window.setInterval(refreshVisiblePresence, 5_000) |
There was a problem hiding this comment.
Every visible browser now requests the complete Corp snapshot every five seconds, even when the connections dialog is closed and the workspace has no saved connections. Because the snapshot includes the full bounded mission, task, run, artifact, and event projections and triggers an application-wide state update, idle clients create a continuous 12-requests-per-minute load each; at multi-user scale this needlessly taxes the server and causes recurring full-app renders. Poll the narrower connection/presence endpoint or enable this timer only while a connection-dependent view is open.
Useful? React with 👍 / 👎.
|
Landed through the owner-authorized batch PR #228 at main commit Closing this original stacked review as superseded by #228, not claiming a separate merge of this PR. This removes duplicate work from the open queue. The branch, native stack #203 and later unfinished work are preserved. Broader source-issue acceptance is not declared complete. Branch protections and auto-merge settings were not changed. |
1 participant
Summary
Layer 2 of 3: an ECorp operator can connect a project and native coding agent, test the connection, then use it to deliver a verified application.
Depends on
codex/issue198-connections-backend. The next layer adds authoritative mission-to-Factory context. Refs #198; #145 / #63 remain open for the complete operating lane.Retained acceptance
Publishing unchanged commit
9efab732bed327f9aea8951a1640ba7d39d15f9f; no additional provider run was launched to publish it.Complete acceptance report, provenance and limitations
Documentation and scope
Includes the project-connections guide and architecture/security updates. This does not claim production identity, real GitHub intake/publication through ECorp, multi-agent Studio acceptance or a one-click hosted result preview.
GitHub Actions credits are exhausted; retained local checks, not hosted CI, are the evidence. Commits retain
[skip ci]. No merge or auto-merge is enabled.