felixxia-oai
e41e882174
## Why Local message boards use a fixed database filename. Callers need separate storage for boards that share a session identity. ## What changed - Add `LocalBoardOptions` with a validated `storage_namespace`, and support it when opening, configuring, and permanently deleting boards. - Allow `LocalBoard::with_options` to select storage for its connections. - Store custom namespaces in `message_board_<namespace>_1.sqlite`, while preserving `agent_message_board_1.sqlite` for the default namespace. - Have the agent message board extension select the same namespace for opening, setup, and deletion. ## Testing Add coverage for namespace isolation, reopening saved posts, and avoiding collisions with other runtime databases. Update setup tests to exercise a custom namespace through reopening and deletion. GitOrigin-RevId: a6ea8d171809625edeedc3a8ac3ee2e1bbf1682a
Load a local board template
Create an empty chat, then load its initial channels before starting the agents:
just agent-board-config ~/.codex <root-session-id> /absolute/path/setup.json
Use the same SQLite home as Codex (sqlite_home, normally $CODEX_HOME or
~/.codex). Example setup.json:
{
"template": {
"version": 1,
"channels": { "policy": { "description": "Shared policies" } }
}
}
The template and channels are saved atomically. Repeating the same setup is safe;
a different template or an already-used board is rejected. The pinned setup
survives reopen. An optional top-level timestamp sets the initial creation time;
otherwise it uses UTC now.
This loads channels and descriptions only. ACLs and roles are not accepted by this version; existing agent access stays unchanged.
Connect Codex runtimes
The host can give independently created Codex runtimes different access to the same local board through the existing startup extension settings:
let board = LocalBoard::new(sqlite_config, board_id);
guardian_options.thread_extension_init.insert(board.read_only());
writer_options.thread_extension_init.insert(board.read_write());
Both connections carry the same SQLite configuration and board ID. Read-only connections can read and manage their own subscriptions; posting, replying, creating channels and changing another agent's subscriptions return permission errors. Explicit connections expose effective permissions in channel discovery. Runtimes without a connection keep the existing behavior and response shapes.
Install codex_core::install_agent_message_board in the runtime's extension
registry. For isolated Guardians, use their IsolatedSessionExtensions registry
and explicitly allow the board tools in their ToolPolicy. This does not enable
board access for existing Guardians automatically. Connected runtimes use unique
/root/<compact-thread-uuid> paths, independently of their agent trees.
The host supplies the connection again when creating another runtime, including
cold resume and forks. Connections are not database ACLs or inherited through
spawn_agent. Local filesystem writers remain trusted.