Skip to content

Prefer Colony as coordination companion#449

Merged
NagyVikt merged 1 commit into
mainfrom
agent/codex/replace-cavemem-with-colony-companion-2026-04-28-20-34
Apr 28, 2026
Merged

Prefer Colony as coordination companion#449
NagyVikt merged 1 commit into
mainfrom
agent/codex/replace-cavemem-with-colony-companion-2026-04-28-20-34

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Automated by gx branch finish (PR flow).

Guardex setup and status prompts were still centered on cavemem even though the current coordination contract is Colony-first. The global service list now checks @imdeadpool/colony-cli as the companion and the docs include the runtime registration commands.

Constraint: Keep existing setup/status flow intact while changing only the companion package identity.

Rejected: Keep cavemem as optional alongside Colony | would preserve the stale prompt the user asked to replace.

Confidence: high

Scope-risk: narrow

Tested: node --test --test-name-pattern "setup skips global install when companion npm tools are already installed|setup installs only missing global tools|setup warns when user declines oh-my-claudecode dependency install|setup installs missing local companion tools with explicit approval|setup warns when gh dependency is missing" test/setup.test.js

Tested: node --test test/status.test.js

Tested: node --check bin/multiagent-safety.js

Tested: openspec validate agent-codex-replace-cavemem-with-colony-companion-2026-04-28-20-34 --type change --strict

Tested: git diff --check
@NagyVikt NagyVikt merged commit f5230f0 into main Apr 28, 2026
@NagyVikt NagyVikt deleted the agent/codex/replace-cavemem-with-colony-companion-2026-04-28-20-34 branch April 28, 2026 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant