Replace single Config.BotUser with the confirmed multi-identity config shape. Daemon runs multiple bot identities concurrently (each with its own forge token, repo list, model/provider config), dispatching through the existing shared NATS/container pipeline. Validate by migrating the two real carina processes (archie: bot_user=archie, repos=[archie-core,tau], deepseek models; winter: bot_user=winter, repos=[tau], local llama.cpp models) onto one daemon. Per docs/prds/multi-agent-collaboration.md phase B.
Acceptance Criteria
One archied process on carina replaces the current two (archie config.toml + winter.toml), producing the same dispatch behavior (issue polling, task claiming, PR flow) for both identities as the two separate processes did. No regression in existing single-identity config compatibility (old single-BotUser configs still work or have a documented migration path).
Imported from beads archie-core-1786637497825-305-cc16d654 · GitHub #326 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08
Replace single Config.BotUser with the confirmed multi-identity config shape. Daemon runs multiple bot identities concurrently (each with its own forge token, repo list, model/provider config), dispatching through the existing shared NATS/container pipeline. Validate by migrating the two real carina processes (archie: bot_user=archie, repos=[archie-core,tau], deepseek models; winter: bot_user=winter, repos=[tau], local llama.cpp models) onto one daemon. Per docs/prds/multi-agent-collaboration.md phase B.
### Acceptance Criteria
One archied process on carina replaces the current two (archie config.toml + winter.toml), producing the same dispatch behavior (issue polling, task claiming, PR flow) for both identities as the two separate processes did. No regression in existing single-identity config compatibility (old single-BotUser configs still work or have a documented migration path).
---
_Imported from beads `archie-core-1786637497825-305-cc16d654` · GitHub #326 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Replace single Config.BotUser with the confirmed multi-identity config shape. Daemon runs multiple bot identities concurrently (each with its own forge token, repo list, model/provider config), dispatching through the existing shared NATS/container pipeline. Validate by migrating the two real carina processes (archie: bot_user=archie, repos=[archie-core,tau], deepseek models; winter: bot_user=winter, repos=[tau], local llama.cpp models) onto one daemon. Per docs/prds/multi-agent-collaboration.md phase B.
Acceptance Criteria
One archied process on carina replaces the current two (archie config.toml + winter.toml), producing the same dispatch behavior (issue polling, task claiming, PR flow) for both identities as the two separate processes did. No regression in existing single-identity config compatibility (old single-BotUser configs still work or have a documented migration path).
Imported from beads
archie-core-1786637497825-305-cc16d654· GitHub #326 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08