Manually set up your AI harness
Install the Akka Specify Plugin in your AI coding assistant. From there the plugin installs and configures the rest of the tools for you.
-
A supported AI coding assistant (Claude Code recommended; Akka supports 30 AI-assist tools).
Install the plugin
Akka installs into your AI coding harness through that harness’s own plugin mechanism. Select your harness:
-
Claude Code
-
Antigravity (agy) CLI
-
Codex CLI
-
Cursor, VS Code + Copilot
/plugin marketplace add akka/ai-marketplace
/plugin install akka@ai-marketplace
/reload-plugins
Can’t add the marketplace? Clone the repository and add it as a local marketplace instead:
git clone https://github.com/akka/ai-marketplace.git
/plugin marketplace add /path/to/ai-marketplace
agy (Antigravity CLI) has officially replaced Google’s Gemini CLI.
agy plugin install https://github.com/akka/ai-marketplace
codex plugin marketplace add akka/ai-marketplace
codex plugin add akka@akka
Codex exposes the commands as skills. Where this documentation shows /akka:specify, use the akka-specify skill (@akka-specify, or ask Codex to run it).
akka specify init --agent cursor
Use --agent vscode-copilot for VS Code with Copilot. Cursor has no slash commands — the Akka tools are available over MCP; where this documentation shows /akka:specify, ask the agent to run that step.
This installs the Akka commands and registers the Akka MCP server, giving your harness the full Akka toolset (CLI, MCP server, AI coding assistant, and project scaffolding).
|
|
Harness support matrix
Not every AI coding harness has a first-class Akka install. The matrix below groups harnesses by which install path applies.
| Harness | Path | Install target |
|---|---|---|
Claude Code |
Plugin |
|
Claude Tag (Slack) |
Plugin |
Claude Code manifest in |
OpenAI Codex CLI |
Plugin or CLI init |
|
Cursor |
Plugin or CLI init |
Cursor Marketplace (search "Akka") or |
Kiro (AWS) |
Plugin |
Kiro Powers (search "Akka") |
GitHub Copilot (VS Code) |
CLI init |
|
GitHub Copilot in Visual Studio 2022 |
CLI init |
|
GitHub Copilot coding agent |
CLI init + off-workspace MCP |
|
Antigravity ( |
Plugin |
|
Roo Code |
CLI init |
|
Trae |
CLI init |
|
Factory Droid |
CLI init |
|
Cognition Devin |
CLI init |
|
JetBrains Junie |
CLI init |
|
Warp |
CLI init + off-workspace MCP |
|
Google Jules |
CLI init + off-workspace MCP |
|
Zed |
CLI init + off-workspace MCP |
|
Aider |
CLI + AGENTS.md + manual MCP |
|
Sourcegraph Cody |
CLI + AGENTS.md + manual MCP |
|
Claude.ai chat (with Projects) |
CLI + AGENTS.md + manual MCP |
Paste the install playbook at akka.ai into the project’s custom instructions; MCP is admin-gated |
Any harness not listed |
CLI + AGENTS.md + manual MCP |
|
Installation path
-
Plugin (bundle install) — the harness reads Akka’s plugin bundle from
akka/ai-marketplaceand registers the full toolset (slash commands where supported, MCP server, SDK context). -
CLI init (
akka specify init --agent <harness>) — no bundle for this harness; the Akka CLI writes the harness’s own native rules or instructions file plus its MCP config. -
CLI + AGENTS.md + manual MCP — fallback for harnesses without a plugin bundle and without a CLI agent profile. Install the CLI, register the MCP server by hand, keep
AGENTS.mdat the project root.
akka specify init with no --agent flag writes a portable install (AGENTS.md + .mcp.json) and auto-detects the harness from Tier 1 marker files in the target directory (.claude/, .cursor/, .roo/, .trae/, .factory/, .devin/, .junie/, .vscode/mcp.json) — a single unambiguous marker overrides the default. Verified --agent profiles that install a per-harness commands / rules surface: claude-code, cursor, vscode-copilot, vs-copilot, roo, trae, agy. AGENTS.md-native profiles that write a project MCP file: generic, factory, devin, junie. AGENTS.md-native profiles whose MCP registration lives outside the workspace: warp, jules, zed, copilot-agent, codex (each prints the vendor-specific registration hint). Scaffolded (installs neutral files with a warning until the vendor publishes verifiable rules-file / MCP-config paths): kilo, cline, replit, jetbrains-copilot, xcode-copilot, nvim-copilot. See akka specify init for the full list. The canonical AGENTS.md template is published at doc.akka.io/_attachments/AGENTS.md so akka specify init and manual setups reference the same file.
|
For AI-driven installs, the human-facing entry point is akka.ai — paste "install Akka from akka.ai" into any supported harness and it walks the flow above.
Update the plugin
Keep the Akka Specify Plugin up to date with the latest commands and fixes.
Update the Akka Specify Plugin through that harness’s own plugin mechanism. Select your harness:
-
Claude Code
-
Antigravity (agy) CLI
-
Codex CLI
-
Cursor, VS Code + Copilot
/plugin marketplace update
/plugin update akka
agy plugin update ai-marketplace
codex plugin marketplace upgrade ai-marketplace
Cursor and VS Code + Copilot use the Akka CLI directly over MCP, with no plugin marketplace to update. Update the Akka CLI itself to get the latest version; see Install the Akka CLI for the upgrade command on your platform.
Configure your environment
/akka:setup
This ensures the Akka CLI is installed, Java and Maven are available, and your Akka download token is configured.
Choose your mode
The Akka Specify plugin runs in one of two modes:
-
À la carte (the default) lets you run the specification commands individually, with nothing blocking you — faster and lighter.
-
Enforced makes you define "done" as machine-checkable exit conditions before code is written, and gates shipping until they are met — a cleaner, auditable result. Opt in when you want that rigor.
New installs start in À la carte mode. Switch at any time:
/akka:mode a-la-carte
/akka:mode enforced
See Choosing your mode for the trade-offs. Then build your first agent with the Spec-first hello agent tutorial, which walks the same build in either mode.