Orchestration records intent and state without knowing which provider runs a thread. Provider protocols, account ownership, permissions, and capabilities belong at the adapter boundary. Normalize there instead of spreading provider checks through reactors and clients.
A driver kind identifies an integration; an instance identifies one configuration and account lifecycle. Route work by instance, so two accounts using the same driver do not share mutable session or catalog state.
T3-managed OpenCode chat uses one server per thread. Its MCP registrations are directory-scoped, while T3's MCP connection is thread-scoped. Sharing a chat server between threads in one directory would let them replace each other's connection. Catalog and text-generation work can share the instance-owned helper, which closes after an idle period. External OpenCode servers remain externally owned and can require an external restart to pick up configuration changes.
OpenCode also stores persistent approval grants per directory. Automatic full-access replies use
once so they cannot widen a supervised thread's permissions on a shared external server.
See the adapter.
Antigravity separates account profiles per instance while sharing installed executables across the environment. It forces file-based credential storage because the native macOS keychain entry would otherwise be shared across instances. The launch environment removes ambient Google credentials, so an instance cannot silently use another account or billing project. See profile isolation.
The Antigravity installer outlives client connections and provider-instance rebuilds. Releases are immutable, with an atomic pointer selecting the version for new processes. Running processes hold leases on their version. Updates and removal must respect those leases instead of replacing executables under a running agent.
Opening a provider session can start MCP servers, run hooks, or launch a login browser. Grok probes avoid authentication and session creation for this reason. Antigravity likewise reserves authenticated catalog sessions for explicit setup or model refresh; background checks use initialization only.
Antigravity sign-in belongs to the initiating T3 auth session. The client carries the return URL back to the environment because the provider's loopback listener may be on another machine. Forward only the callback for the owned pending flow; a successful callback HTTP request is not proof that provider authentication finished. The native process owns token exchange and storage.
Antigravity sign-out closes admission to new processes and stops existing processes before clearing account metadata. Otherwise a helper or resumed session could retain the old account. Cached model lists do not establish current access, and an authoritative empty catalog must clear the old list.
Antigravity text-generation helpers deny tool requests, but native hooks and MCP configuration can run before the prompt. They reject profiles with such configuration before launch. Prompt instructions and tool denial do not create a native sandbox. See helper constraints.
A one-click update is offered only when the resolved executable's path proves which installer owns
it. Homebrew and npm are proven by the real path (symlinks followed): a versioned keg or cask under
brew --prefix, or <prefix>/lib/node_modules/<pkg>/ (Windows: the shim beside node_modules).
Native installer layouts and the global bin directories of pnpm, Bun, and Vite+ may match on either
the resolved path or its real target, since those installers place real files or their own symlinks
there. Anything unproven stays manual-only but still reports the version gap. npm updates pin
--prefix because the npm on PATH can belong to a different Node than the one that owns the
provider. Homebrew
compares against brew info since casks trail npm by hours; native installs share npm's version
train, so the registry stays authoritative for them.
See the resolver.
Ownership is cached per instance and re-read immediately before an update runs. The runner refuses when the lock key changed since the advisory, and reports success only when the refreshed provider is still installed with a readable, current version.
Codex async questions arrive as notifications and are answered with a new user message. There is no pending RPC response to send. Blocking questions still use the request/response path. The adapter distinguishes them; the decider records an async answer and its user message together.
An async question can outlive the turn or a server restart. The engine reads that request's durable activity before resolving it because the in-memory command snapshot omits old activities. Do not infer that a request has disappeared merely because it is outside the recent window.
Capabilities must describe what the provider can actually do. Antigravity can capture workspace checkpoints but cannot roll back its conversation. The checkpoint boundary therefore rejects revert before touching files. Native permission and question option IDs must also survive normalization; a display label is not necessarily a valid reply.
Attachments live outside the project workspace. ProviderService puts their environment-local paths in turn input and lets adapters choose native input formats. A path in the prompt does not grant filesystem access. Keep provider sandbox and approval rules in force; copying uploads into the project to bypass them changes that boundary.
File attachments introduced a replay compatibility limit. Image-only clients cannot decode file-bearing messages, and an image-only server can fail the entire environment's startup when replaying one such event. Rollouts and downgrades must account for persisted history as well as current client support.
Model classification has its own manifest constraints. Assistant-reference handling is documented under citations.