Latest release v2.3.0 Released 2026-06-06 Changelog r/agenticflowx

VS Code extension

AgenticFlowX

Low-barrier spec-driven AI coding.

Chat first in VS Code. Add Code / Explore / Spec structure when the work needs traceability, clickable workflow steps, and repo-owned markdown. Backed by pi.dev today.

Install the extension See how it works

VS Code Marketplace · Open VSX · Changelog · r/agenticflowx

Works in VS Code, VS Code Insiders, VSCodium & Antigravity (pre-2.0).

Open source VS Code extension Code · Explore · Spec modes Plain markdown in your repo
A fast walkthrough from chat to spec, tasks, implementation, and project memory.

Core workflow

Start loose. Leave a trail when it matters.

AgenticFlowX keeps daily coding conversational, then lets serious work become specs, designs, tasks, notes, journals, and code context in the repo.

Fast chat Guardrails on demand Durable repo memory

Working loop

The conversation can become the project record.

A normal coding chat stays lightweight. When the work needs decisions, review, or traceability, AFX turns that same flow into files your team can inspect later.

  1. 01
    Chat

    Keep the fast path fast.

    Ask questions, mention files, switch models, run commands, and follow up while the context is still fresh.

  2. 02
    Structure

    Add guardrails at the moment of risk.

    Move from requirements to design, tasks, implementation, validation, review, and approval without leaving VS Code.

  3. 03
    Repo memory

    Preserve the reason, not just the change.

    Notes, docs, boards, journals, and pipeline views sit over plain markdown files in your workspace.

Result Ship the quick turn, or keep a traceable path from intent to spec, task, and code.

Code / Explore / Spec

Choose how much structure the next turn needs.

AgenticFlowX is not locked into one workflow. Stay loose in Code mode, inspect safely in Explore mode, then switch into Spec mode when the work needs a planned path from requirements to design, tasks, and implementation.

Code mode / Default

Everyday implementation stays conversational.

The default lane keeps chat open for edits, shell commands, tests, debugging, and fast follow-up.

  • Intent rail
  • Mode switch
  • .afx.yaml
Bottom rail: intent, mode, .afx.yaml, and memory stay visible.

Explore mode / Read-only

Inspect before you let the agent edit.

Use Explore when you want behavior tracing, option comparison, and planning without mutation.

  • Default intent
  • PRD lane
  • Read-only input
Read-only status is visible in the prompt, footer, and intent rail.

Spec mode / Planned

Workflow guardrails for traceable work.

Spec mode adds the workflow rail for refining requirements, authoring designs, slicing tasks, validation, review, and approval.

  • Spec workflow
  • Actions
  • spec.md
Spec rail shows phases, document actions, and the active spec file.

AFX Viewer

Markdown that can start the work.

AFX Viewer is not just a nicer markdown preview. It puts workflow commands directly on top of your repo files, so a spec, design, task list, ADR, note, or journal can send focused context to chat, refine a section, or start coding the selected task.

Inline toolbar Code task sections Send to chat
Task and phase commands are available directly inside the rendered markdown view.
  • Run document commands from the page Refine a spec, author a design, validate, review, approve, pick, or code from the rendered document.
  • Code the exact task section Open tasks.md, choose a phase or task row, and draft the focused code command into chat.
  • PM flow and dev flow in one place Review sections like a PM, then send the right context to chat or start implementation like a developer.
Plain markdown on the left, interactive AFX Viewer on the right.

IDE traceability

Code that remembers why it exists.

AFX teaches VS Code to understand @see links in source comments. Hover a requirement or design anchor to preview the linked markdown inline, use CodeLens to open the source document, or jump directly to anchors like [FR-1], [DES-API], and [2.1].

@see links CodeLens Hover previews
Source comments stay plain text; the IDE adds navigation, previews, and trace-aware shortcuts.
  • Preview intent without leaving code Hover a linked anchor to see the matching spec, design, or task section while your editor focus stays put.
  • Jump from implementation to source of truth CodeLens and go-to-definition turn @see references into native VS Code navigation.
  • Keep the trail reviewable in Git The links are ordinary comments pointing at ordinary markdown, so traceability survives outside the extension.
Experimental

Project Canvas

Think visually without leaving your repo.

Canvas is a freeform workspace for specs, markdown files, notes, ADRs, labels, and architecture ideas. Link cards, follow project context, and send selected canvas material back into chat when an idea is ready to become work.

project.canvas Linked markdown Ideation to spec
A project canvas connects product questions, specs, implementation notes, file context, and chat handoff.
  • Map specs, files, and notes together Use cards and file nodes to sketch how product questions connect to implementation details.
  • Label relationships as the thinking evolves Connect cards with named edges like promote into spec or @see trace.
  • Send selected context to chat Turn the useful part of the canvas into a focused chat handoff instead of rewriting the whole map.
Selected cards expose the small actions needed for ideation: edit, link, comment, clipboard, delete, and resize.
The visual map is still a plain project.canvas file in the workspace.

Providers

Bring the access you already have.

Use subscription-backed sign-ins, API keys, or local-compatible runtimes from one settings surface. Backed by pi.dev today.

Subscription sign-ins API keys Local-compatible runtimes

Already use Pi

Your Pi, your config, your keys.

AgenticFlowX detects your installed Pi CLI and routes every call through Pi RPC. Whatever you’ve configured — providers, models, defaults — stays where it is. Nothing copied, nothing re-entered.

New to Pi

Pi bundled. Bring your keys.

The Pi SDK ships inside the extension. Add provider keys in Settings — they’re stored in VS Code SecretStorage and passed through the bundled SDK. No separate Pi install required.

Subscription accounts Sign in with supported subscription-backed accounts such as Claude/Anthropic, ChatGPT/Codex, and GitHub Copilot.
Bring your own keys Store provider keys in VS Code SecretStorage and choose defaults for hosted API providers.
Local-compatible runtimes Use local and OpenAI-compatible providers, including Ollama and llama.cpp-style runtimes.

Providers Pi supports upstream

OpenAI Anthropic Google Gemini Google Vertex GitHub Copilot OpenRouter Amazon Bedrock Azure OpenAI Groq DeepSeek Mistral MiniMax Kimi Fireworks Cerebras Hugging Face Vercel AI Gateway xAI Z.ai Ollamalocal

Plus presets for OpenAI-compatible endpoints & local runtimes

Ollamalocal LM Studiolocal vLLMlocal OpenRouter Vercel AI Gateway Moonshot / Kimi Anthropic-compatible proxy Google AI Studio Custom (OpenAI-compatible)

Workbench tour

Inspect the surfaces when you need the slower tour.

The main flow is chat first. The workbench is where the repo-owned pieces become visible: documents, analytics, boards, notes, journals, and project context.

Workbench surfaces

A focused tour of the repo views, without repeating the chat mode story above.

Facts

Things worth knowing.

How do pi.dev and provider keys work together?

If you already use pi.dev, AgenticFlowX talks to your installed Pi CLI and uses your existing config. If you don’t, AgenticFlowX stores provider keys in VS Code SecretStorage and passes them through the Pi SDK.

Do I need to install another SDD tool?

No. The VS Code extension includes the chat surface, Spec mode, Workbench views, and AFX workflow actions. Specs, tasks, notes, and journals stay as plain markdown in your workspace.

Do I have to use the spec-driven workflow?

No. Most coding stays in chat. The spec-driven workflow is opt-in — reach for it when a piece of work needs traceability between intent, design, tasks, and code.

Is it free?

AgenticFlowX is open source under Apache 2.0. No vendor billing — you bring your own provider keys, subscription sign-ins, or local runtimes.

Headless

No VS Code? Run the same workflow elsewhere.

AgenticFlowX is a VS Code extension. The workflow behind it — specs, designs, tasks, journals, traceability — also runs headless via the AFX CLI. Same skills, same files, same rules.

One-line install (from your project directory)

curl -sL https://raw.githubusercontent.com/AgenticFlowX/afx/main/afx-cli | bash -s -- .

CLI source & docs

Tested with

  • Claude Code
  • GitHub Codex
  • Gemini CLI
  • GitHub Copilot

Start in chat.
Add structure when the work needs it.

Apache 2.0 open source.

Install the extension Star on GitHub