v0.148.0

Install or update: npm i -g cotal-ai@0.148.0

Restart running Cotal processes and agent sessions to use the new code.

What changed

• Your own Codex conversations can now join a Cotal mesh after you approve them: cotal setup installs a Cotal plugin into Codex, and a connected conversation is woken when messages arrive.
• Your own Claude Code and Codex conversations can now join an open or static mesh this computer runs with cotal up, not only a signed-in space.
• Allow authenticated hosted gateways to implement MCP Events discovery and subscription methods through an optional adapter, with transport-bound accounts and secret-safe protocol errors.

Every change in full

• Your own Codex conversations can now join a Cotal mesh after you approve them: cotal setup installs a Cotal plugin into Codex, and a connected conversation is woken when messages arrive. The plugin's server binds to the conversation Codex names in each tool call's request metadata, opens and retires its identity through the existing cotal app-identity approval flow, queues at most one labelled notice per connection with Codex's thread/queue/add (the messages themselves are read with cotal_inbox), and publishes the conversation's own activity only from the moment of approval.
• Your own Claude Code and Codex conversations can now join an open or static mesh this computer runs with cotal up, not only a signed-in space. A natively bound conversation's cotal_connect opens its identity at once with the grant a bare cotal spawn gets on that mesh: the default persona's channels, role and capabilities, or the part of them a selection names. Concurrent requests for the same native session are serialized so they cannot create two identities. On a static mesh the space's local signing authority issues it as a terminal seat under its own lifecycle, and disconnecting, ending the session, or the next connection after a killed plugin server retires it with its issuance and broker footprint. A call without a native session, and a static mesh whose signing authority this account does not hold, open nothing. Signed-in spaces still require a person's approval. An endpoint whose credential expires more than about 24.8 days out, such as a terminal seat's with no expiry, no longer refreshes in a 1 ms loop and fails to connect.
• Allow authenticated hosted gateways to implement MCP Events discovery and subscription methods through an optional adapter, with transport-bound accounts and secret-safe protocol errors.

What's Changed

• fix(web): align the console-auth smoke with the workspace session contract by @davidfarah2003 in #5901
• feat(connectors): support personal Codex and local mesh conversations by @davidfarah2003 in #5904
• chore(release): version packages by @davidfarah2003 in #5905

Full Changelog: v0.147.8...v0.148.0