Documentation, tutorials, and answers to common questions about building with your agentic teammates.
Product docs, API references, and tutorials for every Aria surface.
Sign up, BYOK your provider keys, open your first project, and ship your first task in under five minutes.
Connect your Cursor, Claude Code, Windsurf, or Cline editor to Aria's MCP endpoint. See /integrations for the config snippets.
Use AriaForge to stand up a 5โ20 agent team with typed roles (Architect ยท Engineer ยท Inspector ยท Registrar) to ship a single mission together.
Two ways to talk to Aria: the dedicated phone line (brainstorm out loud) and SuperWhisper push-to-talk into any pane. See /voice-ui.
The 5-state lifecycle (INTENT โ BUILD โ REVIEW โ SHIPPED โ CLOSED) with role-typed column owners. The kanban surfaces accountability at a glance.
Drag any skill card from the right-sidebar Skills tab onto a terminal to paste its prompt. 14 production skills bundled at Elite tier.
Verify the JSON snippet at /integrations is in the right per-editor config path (different per editor: ~/.cursor/mcp.json, ~/.claude/mcp.json, ~/.config/cline/cline_mcp_settings.json). Restart the editor after writing the config. Then ask your agent "list my Aria projects" โ if the response uses the list_projects tool, the connection is live.
Yes โ that's the point of the workspace's pane grid. Up to 16 panes per project, each running an independent agent CLI. Use the handoff dropdown on each pane header to switch agents while preserving context. For a true multi-agent team, use AriaForge.
Your provider keys (Anthropic, OpenAI, Grok, Gemini) stay on your own machine โ Aria is runner-local and never stores them on our servers, so there's no server-side key manager to add them to. Set each key in your environment / provider config on the machine where aria-runner runs, and the runner uses your key locally per project. Connect it from the runner setup.
Doctrine: every shipped action gets a SentinelPass JWT-VC receipt signed with our ed25519 issuer key. The Inspector's approval is the human-or-agent gate that authorizes the seal. Skipping review = no receipt = no audit trail = no sovereignty.
Subscription tiers ship monthly + annual cadences via Stripe. Billing portal at Settings โ Billing lets you cancel any time. On cancel, your subscription ends at the close of the current period and ASI skills stop being accessible; your data stays.
Email support@insynctech.io with the subject line "Aria bug" or "Aria feature." Every report lands in our ops_log within an hour.
ASI is the user-facing brand for the skill library โ what shows up in the right-sidebar Skills tab and at /skills. PSR is the gated GitHub repo where the skills physically live. Same library, different surfaces. All skills require Elite tier.
Two paths. Both are first-class. Pick whichever matches how you already pay for AI.
You mint a key from your vendor's developer console and paste it into Aria. We charge nothing on top. Pay-per-token at vendor MSRP.
Where to get a key:
sk-ant-sk-proj- or sk-.xai-AIzaAfter you have a key:
/v1/models with it โ green check if it works, clear error if notAlready paying for Claude Pro/Max or ChatGPT Plus/Pro/Team? Don't open a new payment relationship. aria-runner bridges your local CLI session into Aria. Your subscription pays.
How it works:
claude login / codex login) โ OAuth, browser-basedaria-runner โ a small Python script that opens a WebSocket to Ariaaria-runner (works in tmux/screen so it survives terminal closes)What's supported:
claude CLI (Claude Code)codex CLIHand-holding walkthrough: /connect/openai walks you through ChatGPT in six steps. Anthropic walkthrough is built into the Pro Plan card at /onboarding/credit-source.
Most vendors sell two distinct products under the same brand. Claude Pro / ChatGPT Plus are chat subscriptions โ they include access to the vendor's first-party app + their CLI (Claude Code / Codex). Developer API keys are a separate product, billed per token, accessed via the vendor's api.* endpoints. A ChatGPT Plus account's auth token returns HTTP 403 against the OpenAI Platform API โ they're not interchangeable. Aria supports both paths because most people are paying for one and don't realize the other exists.
Only if you're using the subscription / aria-runner path. The runner is a local WebSocket; if your machine sleeps or disconnects, Aria can't reach your CLI session and the call returns an error with a "your runner is offline" message. BYOK keys are cloud-only โ no install, no machine dependency.
Yes. You might use Pro Plan for heavy daily Claude work (cheaper) and a BYOK xAI key for Grok-specific tasks. Settings โ Billing lets you set a preferred path per vendor.