Using Paqad with Continue

For Continue, the open-source coding assistant for VS Code and JetBrains IDEs, Paqad is advisory: onboarding writes one rule file, .continue/rules/paqad.md, telling the AI how to load your project's rules and workflows. Nothing in Continue makes the AI follow it, and Paqad installs no hooks for Continue.

What Paqad can enforce in Continue

Nothing, during the session. Continue is at the advisory level: the tool is given the rules but nothing stops it ignoring them.

• No edit is refused by Paqad.
• No verification runs when the AI finishes.
• Paqad's evidence files are only written if the AI runs Paqad's commands itself.

Paqad's source records Continue as advisory, with hooks, agents, cache and memory switched off for this adapter.

Files onboarding writes

File	What it is
.continue/rules/paqad.md	The entry file, in Continue's project rules folder. It tells the AI to open .paqad/framework-path.txt and follow the installed framework, or to act as a normal assistant if Paqad is missing or off.
.continue/mcp.json	The MCP servers Paqad suggests for your stack. MCP (Model Context Protocol) lets AI tools connect to extra information sources. The file names servers but holds no start commands, so it connects nothing by itself.

Onboarding does not write or change .continue/config.json, and it does not create slash-command prompts such as /review or /test. Your existing Continue configuration is left alone.

Getting evidence without hooks

Paqad's instructions ask the AI, on advisory tools, to record each stage of feature work by running Paqad's commands in the terminal:

npx paqad-ai stage start planning
npx paqad-ai stage end planning --artifact <plan file>

These write to the ledger, Paqad's evidence files under .paqad/ledger/. Whether they run depends on the AI and on whether your Continue mode can run terminal commands. Check .paqad/ledger/paqad.stage-evidence/ after a change to see what was really recorded.

Independently of the AI, git post-commit and post-merge hooks link commits to their feature, and you can add Paqad's verification script to your CI pipeline. See Adapters overview.

Setting it up

1. Run paqad-ai onboard --providers continue, or tick Continue when onboarding asks.
2. Open the project and check that Continue lists the paqad rule.

If you need edits to be refused when the process is skipped, use Claude Code or Codex CLI.