Get unstuck without
digging through docs.

Getting started

Install, sign in, and open one project.

Download the macOS or Windows app, sign in with the same account used on this site, then create a Mission around a folder or repository you are authorized to use.

• Your account controls plan and managed-access status.
• Your Mission determines which project context is available.
• Free and Basic users connect their own supported provider.

Provider setup

Connect with an API key or supported CLI login.

API mode uses credentials from your own provider account. Supported CLI paths use the provider's local terminal authentication. The setup wizard and desktop Settings guide both connection types.

• Provider API keys are stored in the device OS keychain.
• BYOK usage is billed by the provider, not A(i)GENCY.
• Pro managed requests can route through the A(i)GENCY backend when that path is enabled.

Files & privacy

Project access follows the scope you choose.

Local Missions, settings, and workspace references remain on your device. When a Mission runs, task-relevant prompts, attachments, file snippets, and tool results may be sent to the active provider or connected tool.

• Repository or folder workspaces can permit edits when enabled.
• Knowledge documents are used as retrieval context.
• Remove saved keys and connectors from Settings; remove Missions and sources in the app.

Troubleshooting

Start with the layer reporting the error.