Prateek 93ff9341be feat: add --continue flag to `ao start` for orchestrator conversation continuity ... When the orchestrator needs a fresh system prompt (e.g. CLAUDE.local.md was updated), `ao start --continue` kills the existing session and respawns with `claude --continue`, preserving conversation history while reloading prompts. Changes: - Add `continue` option to AgentLaunchConfig and OrchestratorSpawnConfig - Claude Code agent plugin passes --continue to CLI when set - Session manager forwards continue option to agent launch config - `ao start --continue` kills existing orchestrator, respawns with continue flag - Other agent plugins unaffected (optional field, backwards-compatible) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-03-02 14:11:12 +05:30
..
agent-orchestrator	feat: publish to npm under @composio scope (#32)	2026-02-15 04:28:57 +05:30
cli	feat: add --continue flag to `ao start` for orchestrator conversation continuity	2026-03-02 14:11:12 +05:30
core	feat: add --continue flag to `ao start` for orchestrator conversation continuity	2026-03-02 14:11:12 +05:30
integration-tests	fix: keep Claude Code interactive after initial prompt (#145)	2026-02-27 18:11:06 +05:30
plugins	feat: add --continue flag to `ao start` for orchestrator conversation continuity	2026-03-02 14:11:12 +05:30
web	Merge pull request #240 from suraj-markup/feat/issue-237	2026-03-02 02:27:39 +05:30