Devin CLI reads ~/.claude/commands/ — conflicts with Claude Code template in mixed install

[kajisha]

Problem

agmsg installs per-agent templates into each agent's dedicated directory:

• Claude Code: ~/.claude/commands/agmsg.md
• Devin CLI: ~/.config/devin/skills/agmsg/SKILL.md

Each template hardcodes the agent type (claude-code or devin-cli) in whoami.sh calls and contains agent-specific instructions (Claude Code's Monitor/TaskList/CLAUDE_CODE_SESSION_ID, sandbox config, etc..

Devin CLI imports configuration from other tools, including Claude Code. It reads as skills (, enabled by default). When both templates exist, Devin CLI picks up the Claude Code template and identifies itself as type, ignoring the template in .

As a result, messages sent to a agent are never visible to the Devin CLI session, because it looks up the inbox instead.

Reproduction

1. Install agmsg with mixed install (no flag) on a machine with both Claude Code and Devin CLI
2. Join a team as type:
3. Send a message to from another agent
4. Run Devin CLI in the project and invoke
5. Devin CLI reports and shows no new messages

Why doesn't help

Running skips , but a subsequent creates it again. There is no way to have both agents working in the same environment — the second install always re-introduces the conflict.

Constraints

Three constraints are in tension:

1. Claude Code users must not be affected. The majority of agmsg users run Claude Code. Mixed install must keep dropping for them.
2. Template overhaul is a large change. Making the Claude Code template type-neutral would require conditional logic for , , , sandbox config, etc. (19+ hardcoded references). High risk of review rejection.
3. Devin CLI's config import is coarse-grained. stops reading, but also disables rules and MCP server imports. There is no per-category toggle.

Possible directions

• A: Devin CLI side — Document as a workaround for users who run both agents. Trade-off: loses rules in Devin CLI.
• B: Template side — Make the Claude Code template type-neutral so a single template works for both agents. Large change, but resolves the root cause.
• C: Install side — Detect Devin CLI presence and skip in mixed install. Affects Claude Code users who also have Devin CLI installed but don't use it with agmsg.

Context

This was discovered while adding agent type support. The type itself works correctly in a Devin CLI-only environment (). The conflict only arises when both Claude Code and Devin CLI templates coexist.