Skip to content

Update docs: live assistants relaunch when a tool-package credential connects #466

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TheGreatAxios merged 1 commit into from
Aug 29, 2026
Merged

Update docs: live assistants relaunch when a tool-package credential connects #466

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions ARCHITECTURE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,6 +167,12 @@ connected event from a system address and does not wake an agent. A
generic in-room connect that an agent asked for still wakes that
agent.

Credential bindings for pinned tool packages fold only at deploy.
Connecting a connector that feeds those packages relaunches live
assistants that already pin them, so the new credential is on the
run — not only on the next invite. The pending-room settle and that
relaunch are separate passes.

## Capability growth and approval gates

An agent's capability set grows through what it is granted, not through
Expand Down
15 changes: 15 additions & 0 deletions IMPLEMENTATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,6 +132,21 @@ template-key-only match posts `connection.connected` from the system
address and does not `dispatchTurn`. A generic pending match still
wakes the asking agent.

That settle is not the whole of a tool-package connect. Bindings for
pinned packages (`pinnedPackageCredentialBindingsFor` in `apps/hub`)
fold only at deploy, so a live assistant launched before the key was
pasted cannot `resolve` the new handle from the old snapshot.
Connecting a `feedsTools` connector (hub `settleServiceConnection`,
e.g. Manus → `@corbits/manus-tools`) therefore also fire-and-forget
relaunches live assistants that pin that package
(`reconcilePinnedToolPackages`). Persist-only — stamp the pin onto the
launch row and leave the run — is the bug that was fixed. Connectors
with no `feedsTools` skip the pass. Same posture as CL-6687 inference
reconcile on provider connect; see
[docs/credential-wiring.md](docs/credential-wiring.md) for the
inference path and the provider plugins (`http-x-manus-api-key` among
them).

## GitHub connect (shipped)

The in-room `connect-github` card and the Plugins/Connections GitHub row
Expand Down
Loading