English · 繁體中文
Give your AI assistant a project notebook, so tomorrow’s conversation can pick up today’s work.
Agentflow has verified integrations for Codex and Claude Code and a portable core for any host that provides file and command tools plus enough state retention for capture and closeout. It keeps your requests, decisions, progress, and results in a readable file. You can use it to improve a document, fix a bug, or carry a larger project across several sessions.
-
Start simply: Type
godev, then describe the task in your own words. -
Find the result: Open the notebook named in the assistant’s closing message, usually
.agentflow/devlog.md. -
Get help quickly: Ask your agent, “How do I use the Agentflow skill for this task?” It can explain the controls using your actual project.
You need Node.js 18 or newer and a host with file and command tools. Codex and Claude provide verified hooks; a generic host uses an explicit safe ID, optional known family, and manual capture/closeout because hooks are not available. Git is needed for version history, feature workspaces, and some installation methods. Ordinary notebook work can use a folder that is not a Git repository.
Run this in a terminal and choose your assistant and installation scope:
npx skills add agfnow/agentflowFor the Claude Code plugin route, add the marketplace in Claude Code:
/plugin marketplace add agfnow/agentflow
Then install the agentflow plugin from that marketplace. Plugin updates follow your Claude Code marketplace update settings. Start a new assistant session after installation or updates.
For Codex, we recommend gpt-6.1-sol/medium as the most stable coordinator choice in their use: model gpt-6.1-sol, reasoning effort medium. The coordinator is the assistant you talk to; it organizes the task and checks the result. This recommendation does not change your model settings automatically. Official model reference.
If you installed through npx skills add, periodically run:
npx skills update agentflowThe Skills CLI takes the installed skill name for updates. agfnow/agentflow is the installation source, so npx skills update agfnow/agentflow is not the current name-based update syntax. Add -g for global installs, or run from the project with -p for project installs.
We recommend a weekly crontab job on macOS or Linux if you want automatic updates. Ask your agent to set it up for your installation. The guide includes a Monday-morning example, explicit paths, and logging.
Send this to your assistant:
godev
Rewrite the welcome page for someone visiting for the first time.
Keep the existing links. Let me review the result before uploading it.
Small tasks can stay simple. fast-lane keeps one task with the main assistant and skips separate review while retaining necessary checks and self-review. cross-check requests a separate review of finished work; review-policy: prefer-independent permits a clearly labelled host review only after separate-review unavailability, while require-independent stays strict. ag requests the full development process when the project’s allow-ag setting permits it.
skip-ag [task] or /skip-ag [task] skips the development pipeline and its advisors for the current Ask while keeping devlog records, necessary checks, normal independent review, ordinary delegation, and stream rules. It leaves project settings unchanged and expires when the Ask closes. A bare command waits for a task. no-ag skips the entire Agentflow protocol; fast-lane also skips delegation, new streams, and independent review.
The notebook keeps the conversation, so a fresh session can resume an unfinished request with godev. With Git, Agentflow normally commits completed work and pushes when a remote exists; tell it when you want local work only.
notebook-ownership: on|off is optional and defaults to off, including when omitted. On gives one session control of an active notebook round; off allows sessions to mix messages, decisions and replies. Both modes retain file locks, safe paths, current-round checks, unchanged snapshots and stream routing. Off preserves existing ownership records. Use notebook-ownership: on when a notebook may be shared. Turning it back on may require explicit recovery of a retained record; no noticeable startup speed gain has been proven.
Ask your agent to run agf setup, or run it in a terminal if the shortcut is available. agf setup --fix can add missing shortcuts after backing up shell settings. An unavailable optional worker does not mean installation failed. Follow any restart notice after project hooks are installed.
If the agf shortcut is missing
For a global installation at one of these locations, run the matching setup file. For another installation location, ask your agent to locate its installed skill first.
node "$HOME/.codex/skills/agentflow/scripts/setup.js"node "$HOME/.claude/skills/agentflow/scripts/setup.js"-
Installation does not require running the regression suite. Contributors can find the test commands in the script reference.
-
Portable core tests are verified on native Windows with Node.js 24. Tests requiring Unix terminals or process controls are explicitly skipped. The background looper is not supported on native Windows.
-
Everyday user guide, with the YouTube introduction.
-
Brief for a new assistant, for orientation before using the installed skill.
-
Changelog, newest version first.
-
Script reference, for technical setup and recovery.
Project settings live in ag.json, using the version-8 configuration format. Type settings to inspect them. Startup fills properties missing from the latest template and reports invalid saved values with suggestions; it asks before changing any wrong value. Unsafe invalid settings still stop startup. Existing v7 files migrate conservatively when opened. allowed-worker is an unordered permission list of external, internal, and host routes; its order has no execution meaning. cli-provider filters only external profiles. Model profiles live under external-workers, and advisor choices under pipeline-roles.