agentleFS
Sign inStart free
TheOnlyFusionCubeTheOnlyFusionCube/devin-plugin-cc/AGENTS.md

devin-plugin-cc

AGENTS.md2 starsChanged 10 days agoApache-2.0View on GitHub

This repository is a coding-agent integration for Devin. It ships a Claude Code plugin under plugins/devin/, but the entire runtime is a plain Node CLI — any coding agent (Codex CLI, OpenCode, Cursor, Gemini CLI, Amp, Jules, Aider) can drive it directly. There is no daemon and no Claude-specific machinery in the execution path. Run it with cwd set to the repository you want Devin to work on. State is scoped per workspace and stored under <tmp>/devin-companion/<slug>/ (override with CLAUDEPLUGINDATA).…

  • Reads credentials

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run it with cwd set to the repository you want Devin to work on.

    line 15
  2. Very specific:

    Every command accepts --json for machine-readable output.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

devin-plugin-cc — agent instructions

This repository is a coding-agent integration for Devin. It ships a Claude Code plugin under plugins/devin/, but the entire runtime is a plain Node CLI — any coding agent (Codex CLI, OpenCode, Cursor, Gemini CLI, Amp, Jules, Aider) can drive it directly. There is no daemon and no Claude-specific machinery in the execution path.

Universal entry point

node plugins/devin/scripts/devin-companion.mjs <command> [flags] [free text]

Run it with cwd set to the repository you want Devin to work on. State is scoped per workspace and stored under <tmp>/devin-companion/<slug>/ (override with CLAUDE_PLUGIN_DATA). Node >= 18.18 is required.

Flags must come before free text; everything after the first positional is passed through verbatim as prompt text.

Commands

CommandPurposeKey flags
setupCheck devin binary, auth, DEVIN_API_KEY; toggle review gate--enable-review-gate, --disable-review-gate, --json
reviewRead-only review of working tree or --base <ref> diff--wait, --background, --base, --scope, --model
adversarial-reviewRead-only review of design choices, tradeoffs, failure modessame as review
taskDelegate work to local Devin (devin -p); write-capable by default--read-only, --write, --sandbox, --resume, --resume-last, --resume-id, --fresh, --wait, --background, --model, --permission-mode
task-resume-candidateFind the session a task could resume (--json)—
handoffCreate a cloud session at app.devin.ai with repo+branch+diff context--wait, --background, --context, --tag, --poll-interval-ms (both poll to terminal — detach in your own agent loop instead)
statusList jobs; status <id> for one; --wait polls to terminal--json, --timeout-ms
resultPrint a finished job's stored output verbatim--json
cancelKill a running job's process tree (or terminate a cloud session; the job is cancelled only once the stop is confirmed, otherwise cancel_pending, which stays active and can be retried)none

Every command accepts --json for machine-readable output.

Fusion surfaces are agent prompts, not a second runtime command. Claude Code uses /devin:fusion with Claude Opus 5.5 as the frontier lead. Codex uses $fusion from skills/fusion/ with GPT 6 Astra as the frontier lead (Codex skills are invoked with $, not /). Both reuse task for Devin's sidekick work, whose default model remains swe-2-max.

Defaults and safety

  • Model: pinned to swe-2-max (SWE-2 Max). Override per call with --model <id>; see devin models list.
  • Reviews are read-only: review and adversarial-review never modify files. They run devin -p in autonomous mode with --sandbox and fail closed: if the sandbox is unavailable (native Windows, or Linux without bwrap and socat) the job is marked failed with install guidance and is never retried without the sandbox.
  • task is write-capable (accept-edits) unless --read-only is passed. --permission-mode dangerous/yolo/bypass exist but should only be used when the caller explicitly asks for full auto-approval.
  • Handoffs require DEVIN_API_KEY in the environment; nothing writes secrets to disk.
  • DEVIN_API_URL is validated before any authenticated request: it must be unset or exactly https://api.devin.ai (optional trailing slash). Userinfo, paths, queries, fragments, other ports, and other hosts are rejected, and redirects are never followed. Tests only: with DEVIN_COMPANION_ALLOW_LOOPBACK_API=1, an http(s) URL on 127.0.0.1, [::1], or localhost (any port) is accepted. setup reports a rejected URL.

Per-tool wiring

  • Claude Code: install as a plugin (see README). Slash commands, hooks, and the devin-rescue subagent are wired automatically.
  • Codex CLI / Codex IDE: native install — codex plugin marketplace add TheOnlyFusionCube/devin-plugin-cc then codex plugin add devin@devin-plugin-cc. To install only the two portable skills instead: npx skills add TheOnlyFusionCube/devin-plugin-cc -a codex -g -s devin -s fusion -y. Omit -g for project scope. Codex loads skills at session start; the skill bodies teach it the commands and Fusion workflow. (Codex ~/.codex/prompts/ custom prompts are deprecated — use the skill.)
  • Devin CLI / Devin Desktop: the repo doubles as a Devin marketplace — devin plugins install TheOnlyFusionCube/devin-plugin-cc#plugins/devin.
  • OpenCode / Cursor / Gemini CLI / Amp / Jules: these agents read AGENTS.md natively — point them at this file, or drop the skill dir into the project's .agents/skills/ (or the tool's equivalent) so it's loaded as context.
  • Any other agent: the companion CLI above is the whole interface.

Testing

npm test

Uses a fake devin binary fixture (DEVIN_COMPANION_DEVIN_BINARY env var points the companion at any devin-compatible binary). Binary lookup order: DEVIN_COMPANION_DEVIN_BINARY, then devin on PATH, then on macOS the Devin Desktop app-bundle CLI. setup --json reports devin.path and devin.source. DEVIN_COMPANION_DESKTOP_BINARY_CANDIDATE overrides the app-bundle path for tests only.

Download now (ZIP)

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository3 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free