DevCodex: engineering task workflow for coding agents
DevCodex
A CLI that gives six coding agents project context, over 80 skills, verification and resumable tasks across sessions
- 432 ★ on the repository
- Last commit
- AGPL-3.0
Broad access
Why this level
- Host adapters live in the home directory and apply to all projects at once
- In Auto mode the agent passes confirmations on its own and changes project files, while deletion, push and release stay without permission
- Task state, reports and memory live in the project and may contain code and log fragments
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/devcodexDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Host adapters live in the home directory and apply to all projects at once
- In Auto mode the agent passes confirmations on its own and changes project files, while deletion, push and release stay without permission
- Task state, reports and memory live in the project and may contain code and log fragments
This is third-party code. Review the repository files before installing.
What it does
DevCodex is a Node.js CLI that adds an engineering-task management layer to coding agents. The agent still reasons, writes code and calls tools. DevCodex works out the goal of the request, the project and the boundaries of changes, picks profile skills, runs verification and saves progress, so a task can be continued in another session or by another agent. After `npm install -g devcodex`, user-level adapters are installed for six hosts: GitHub Copilot, Claude Code, Codex, Gemini CLI, Grok and Cursor. The `devcodex init` command in the project root creates a `.devcodex/` directory with the project profile, task state, memory and workspace skills. Tasks go through eight workflows (`dev`, `fix`, `analyze`, `audit`, `resume`, `chat`, `self-fix`, `other`). There are more than eighty profile skills in four groups: routing and stages, domain and architecture, quality and delivery, and runtime governance. Auto mode is switched on by addressing `@devcodex-auto` (alias `@rocky`). It passes confirmations, plan, implementation, verification and report on its own within the granted permission. Auto does not allow deletion, writes outside the project, push, tags and releases.
Who it is for. For developers and teams who work with several coding agents and want one process with confirmations, verification and task resumption.
Good fit when
- The agent re-asks about the project in every new session, and you want context, tasks and reports kept in the repository itself
- A long task was interrupted and must be continued from a saved checkpoint after switching sessions or agents
- You want the agent to agree on the goal, scope and acceptance first and only then change files
- You need analysis or an audit only: the `analyze` and `audit` workflows do not change files by default
- Your team uses Codex, Claude Code and Cursor interchangeably and wants shared working rules
Not a fit when
- You need one small edit: for simple tasks DevCodex picks a shortened path and almost all of its capabilities sit idle
- You expect a new agent or a model gateway: DevCodex is neither an agent nor a model request proxy
- You need autonomous work without limits: Auto gets no rights to deletion, push and release
- You work in Gemini CLI: an adapter exists, but the project documentation has no confirmed checks in real use
Example request
Analyze the current project: name the three most important problems, say what you read, and change nothing in the filesLimitations
Node.js 18.17 or newer and one of the supported hosts are required. Host capabilities differ: hooks, MCP, plugins and permissions vary across the six agents. For Cursor, compatibility of the local app and of the Cloud Agent has to be checked separately. Codex and Claude Code work through the OpenAI and Anthropic APIs, which are unavailable from Russia.
Installation updates user-level host adapters in the home directory, and `devcodex init` creates `.devcodex/` in the project. Neither touches business code. The initial project profile stays a draft: it has to be checked and completed against the real code.
DevCodex does not change the model and does not guarantee that code stays on your computer: the host you choose sends the context. The project is distributed under AGPL-3.0, which matters when embedding it into closed products. The main description is written in Chinese.
How to disable. First preview the plan with `devcodex uninstall --dry-run`, then run `devcodex uninstall --apply` and only after that `npm uninstall -g devcodex`. The `.devcodex/` directory stays in projects because it may hold profiles, reports and task memory. Delete it by hand after making a backup copy.
FAQ
How do I install DevCodex?
Run `npm install -g devcodex` and check `devcodex --version`. Then in the project root run `devcodex init` and `devcodex status`. If the install skipped scripts, `devcodex global-adapters apply` installs the host adapters.
What does DevCodex change in the system and the project?
Business logic source code is not changed, no persistent network service of its own is started, and your own skills and host settings are kept. The `.devcodex/` directory appears only after `devcodex init`.
Can I switch to another agent in the middle of a task?
Yes, if its state is written to the project: requirements, reports, memory and checkpoints live in `.devcodex/`. You can move from Codex to Claude Code or Cursor and start by checking the current state of the code. History that exists only in a chat window is not restored.
How do I switch on Auto mode?
Start a request with `@devcodex-auto` or the alias `@rocky`, for example: `@devcodex-auto fix the failing test, no deletion and no push`. Auto acts within the granted permission, and when the scope grows or verification fails it stops the current action and re-frames the task.
How does DevCodex differ from BMAD Method and Spec Kit?
Those give skills and commands for the stages of development from idea to implementation. DevCodex adds a runtime on top of the host: a project profile, task state, memory, resumption across sessions and an evidence report, and it works on six hosts.
Discussion
No questions or reviews yet.
Related
CLI toolsA layer on top of OpenAI Codex that adds project memory, planning and completion checks before a task counts as done
A kit for porting a Claude Code workflow to OpenAI Codex CLI for multi-tenant PHP/Bitrix24-Marketplace projects
The author's personal set: shared agent rules and dozens of skills for GitHub, the browser, macOS, messaging and releases, plus a sync script
A configurator that reads your repo and sets up agents, skills, MCP servers and rules for its stack across several assistants
A CLI that wires a research-to-delivery pipeline with documents and quality gates into Claude Code, Cursor, Codex and other agents
Work modes for AI coding agents: a light solo mode for daily tasks and /man with a plan, checks and review for big changes
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| DevCodex: engineering task workflow for coding agents (this entry) | no | 432 | |
| BMad Method | no | 54,748 | a skill set for agile development with an agent from idea and PRD through architecture to implementation and review |
| Spec Kit | no | 143,920 | a GitHub toolkit whose specify CLI installs spec-driven commands and skills into a project |
| LongHorizon-Harness | no | 1,788 | a CLI that keeps an existing agent on a long task: plans a step, executes it, verifies and saves progress |
README in short
The description, in Chinese, points to the documentation on the project site: a five-minute start, a CLI reference, the six hosts and a troubleshooting guide. The boundaries section states that DevCodex is not a new agent, not a model gateway and not an orchestrator.