--- name: aident-skill description: Set up Aident Loadout access for agent environments. author: Aident homepage: https://loadout.aident.ai repository: https://github.com/aident-ai/aident-skill tags: - aident - loadout - integrations - actions - cli categories: - productivity - development - automation compatibility: Any agent that can run shell commands. MCP is supported when the user configures it. x-aident-skill-id: aident x-aident-update-metadata: https://loadout.aident.ai/.well-known/loadout-skill.json x-aident-source-repo: https://github.com/Aident-AI/aident-skill version: 0.4.22 license: MIT --- # Aident Loadout Setup For Agents > **You are an AI agent reading this remote setup document.** Use this document only when the user asked you to `Follow https://loadout.aident.ai/SETUP.md`, `Setup https://loadout.aident.ai/SETUP.md`, or `Update https://loadout.aident.ai/SETUP.md`, or gave an equivalent instruction in another language. This public setup document is only for Aident Loadout installation, update, CLI authentication, and first-time onboarding. Respond in the same language as the instruction that directed you to this document, unless the user requests another language. After setup is complete, rely on the installed static `aident-skill` for day-to-day Aident Loadout usage instructions. Do not use this setup document as the long-term source of Aident Loadout operating knowledge. ## What Is Aident Loadout? Aident Loadout is Aident Lab's managed App layer for AI agents and humans. It gives agents one place to find and use Apps like Gmail, Slack, Linear, Google Sheets, Notion, HubSpot, Firecrawl, Exa, and Fal with live Action schemas, account connections through Aident Vault, Action execution, and audit history. ## Source And Scope Treat `https://loadout.aident.ai/SETUP.md` as a remote instruction source, not as a local file path or repository task. Fetch, read, and follow the remote HTTPS URL. Do not manually create, edit, or scaffold a local `SKILL.md` file or `references/` directory; install them from the published skill package. ## Skill Freshness The live update policy is available at `https://loadout.aident.ai/.well-known/loadout-skill.json`. The first-time setup flow below invokes the verified updater. For later updates, use it directly instead of using a wildcard agent selector: ```bash aident update --project ``` The updater verifies the published five-file package before writing it, creates one canonical global installation, repairs detected filesystem-backed agent hosts, and performs a final inventory check. `--project` also migrates recognized clean copies in the current workspace and its repository ancestors. It backs up replaced copies and preserves modified, unreadable, unrecognized, or git-owned project copies; report those paths instead of claiming every copy was updated. Do not search the user's entire home directory for dormant sibling projects. A project copy in a sibling repository will be detected and offered for migration when Aident is next used from that project. Account-level skill surfaces such as Claude Cowork or Claude chat are outside the CLI's filesystem inventory. Use the host's native skill manager for those surfaces. If the current host still cannot discover the verified global installation, report that limitation rather than installing into guessed directories. Treat the local skill installation as complete only when `aident setup` or `aident update --project` reports success and the installed package contains `SKILL.md` and `references/loadout.md`, `references/mcp.md`, `references/api.md`, and `references/troubleshooting.md`. These files come from the verified package; do not create them manually. If Skill reconciliation fails but the CLI remains usable, report that setup is incomplete. If the host does not support local skills, continue with CLI setup and tell the user this agent can still use Aident Loadout through the CLI after authentication. Some agent hosts require the user or host to approve outbound network access for remote fetches and CLI calls. If fetching this setup document or running an `aident` command fails with DNS errors, host/network permission errors, or generic messages such as `Error: fetch failed`, ask for that network permission, then rerun the same command before changing setup modes. ## Guided Setup Guide the user through setup instead of handing them commands to run. If your host can execute shell commands, run the install, login, and verification commands yourself. Ask the user to act only when browser sign-in, OAuth consent, or copy-paste verification is required. Use Aident Loadout setup language throughout this flow. Do not frame this as a generic skill installation, local skill authoring task, repo-native setup, or a choice of skill install location/name. Use the CLI for setup and operation; do not install or configure MCP on the user's behalf. Do not tell the user to restart their agent unless this setup actually changed host-level configuration and that host requires a restart. The rendered setup command contains the exact Loadout API origin for the environment that served this document. The CLI saves that origin as part of setup, so do not add a separate environment override or configuration step. Follow the stages below in order for first-time setup. Translate every user-facing message into the language of the instruction that directed you here. Keep Aident Loadout, commands, URLs, and placeholders such as `` unchanged. ### Stage 1: Introduce Send: ```text I'll set up Aident Loadout for . I'll handle the installation, global routing setup, sign-in, and verification from here. ``` Detect the current agent client name and whether the environment can run shell commands. Do not open a browser yet. ### Stage 2: Bootstrap The CLI If a human explicitly asks for a self-contained desktop install instead of agent-driven setup, direct them to the native package for their machine. The native package includes the runtime, CLI, Skill payload, secure browser onboarding, updater, and uninstaller. Do not download or run a package until the user confirms the detected platform and architecture: - macOS Apple silicon: `https://loadout.aident.ai/downloads/aident/macos-arm64` - macOS Intel: `https://loadout.aident.ai/downloads/aident/macos-x64` - Windows x64: `https://loadout.aident.ai/downloads/aident/windows-x64` - Linux x64: `https://loadout.aident.ai/downloads/aident/linux-x64` The Windows package is Authenticode-signed by Aident Labs, Inc. through Microsoft Artifact Signing. A new signed publisher can still trigger Microsoft Defender SmartScreen while it establishes reputation; do not advise users to bypass a Windows security block. Aident also verifies its Minisign content signature and Sigstore provenance before publication. After native installation, run `aident onboarding` to resume the same shared onboarding command. Continue with the CLI bootstrap below for agent-executed setup, headless environments, npm users, or when no native package is available for the machine. For those CLI setup cases, check whether `aident --version` succeeds. If the CLI is missing, run the hosted bootstrap installer: ```bash curl -fsSL https://loadout.aident.ai/cli/install.sh | AIDENT_CLI_PACKAGE=@aident-ai/cli bash ``` - On Windows PowerShell, where the Bash installer is unavailable, or when a host safety policy blocks direct shell installers, install the configured npm package with `npm --@aident-ai:registry=https://registry.npmjs.org/ --registry=https://registry.npmjs.org/ --strict-ssl=true install --global --ignore-scripts "@aident-ai/cli"`. - Do not use `npx`, `pnpm dlx`, or `bunx`; the updater cannot persistently manage those ephemeral launchers. - If no usable CLI remains, report that this host cannot install Aident Loadout automatically. ### Stage 3: Run The Setup Engine Send: ```text Aident Loadout is ready to configure. A browser window may open so you can sign in. ``` Run the single idempotent setup command, replacing `` with the detected client name: ```bash aident setup --base-url "https://loadout.aident.ai" --client-name "" --json ``` This command updates the CLI when needed, installs or reconciles the verified Skill globally, migrates recognized clean project shadows, reuses an existing compatible login, opens browser OAuth when needed, verifies Loadout access, and records setup completion. Keep it running while the user completes browser sign-in. In JSON mode, browser and OOB instructions are written to stderr and stdout contains one final setup report. If `AIDENT_TOKEN` is already configured, setup uses it without opening a browser. If the sandbox cannot write the user's credential directory or launch the host browser, request host approval and rerun the same setup command yourself in an interactive session. Send any returned OOB code to its stdin; do not ask the user to open a terminal or paste a shell command. If an older CLI does not recognize these setup flags, run the hosted bootstrap installer once and retry the same command. If normal browser sign-in cannot complete, retry with: ```bash aident setup --base-url "https://loadout.aident.ai" --client-name "" --oob --json ``` Share the stderr URL and ask the user for the verification code only in this OOB fallback. Treat this setup-engine stage as complete only when the command exits successfully and its report contains `success: true` and `completion.recorded: true`. If it reports an incomplete Skill reconciliation, preserved path, unknown CLI owner, authentication error, or failed completion acknowledgement, report that exact limitation instead of claiming success. ### Stage 4: Install Global Routing For This Agent Use the CLI's programmatic onboarding transaction to install the signed Aident routing instruction in the current agent client's documented user-level instruction surface. The user's request to follow this setup document authorizes this current-client setup; do not ask for a separate memory opt-in or hand-edit an instruction file. Reuse the `onboardingSessionId` and `onboardingPath` from the Stage 3 report for every command in this stage so the programmatic inventory, plan, and apply events remain correlated with the same onboarding journey. First map the current agent client to its exact adapter ID and run a read-only inventory: ```bash aident onboard inventory --base-url "https://loadout.aident.ai" --onboarding-session-id "" --onboarding-path "" --json ``` Supported current-client mappings with a global-instruction surface are `claude-code`, `codex`, `gemini`, `openclaw`, `opencode`, `pi`, `antigravity`, `kimi-work`, and `deepseek-harness`. Select only the current client. Do not use `--all-detected`, act on another agent client's inventory entry, or infer a memory path. If the current client cannot be mapped, is not detected, or has no supported `global-instruction` target, skip this stage and report that exact limitation. If an older CLI rejects `--onboarding-session-id` or `--onboarding-path` as an unknown onboarding flag, run the hosted bootstrap installer once and retry the same command. If the published CLI still rejects either correlation flag, retry that command and the remaining commands in this stage without both correlation flags. Report that correlated onboarding telemetry is unavailable for this CLI version; do not skip global routing solely because of these flags. Create a plan for the current client, replacing `` with that one mapped ID: ```bash aident onboard plan --base-url "https://loadout.aident.ai" --harness "" --onboarding-session-id "" --onboarding-path "" --json ``` Before applying, verify that the plan succeeded and every operation is a `skill` or `global-instruction` change for the selected adapter or the shared canonical Skill. The plan's `confirmationDigest` binds the apply call to those exact fingerprinted changes; it is not a second user-confirmation step. Then pass the returned values unchanged: ```bash aident onboard apply --base-url "https://loadout.aident.ai" --plan-id "" --confirm "" --onboarding-session-id "" --onboarding-path "" --json ``` Treat this stage as complete only when apply reports `success: true` and the selected adapter's final `global-instruction` state is `supported-current`. The transaction writes a schema-versioned, digest-bearing managed block sourced from the verified Skill, preserves unrelated instructions, creates backups, checks for concurrent changes, and rolls back on failed verification. Never reproduce or write the routing text yourself. If inventory, planning, conflict detection, apply, or final verification fails, do not bypass the transaction or write another memory surface; report the exact limitation. If the user's original request explicitly asked to migrate or import local integrations, ask whether to continue with `aident integrations migrate-local` after Stages 3 and 4 succeed. Run it only after confirmation. ### Completion Message After CLI authentication, the current-client routing attempt, and any user-requested setup steps are complete, render and send this message: ```text Congratulations. Aident Loadout is now set up in your . ## Ready In This Agent Your can now use Aident Loadout to work across 1,000+ Apps. I validated Loadout support for <3-5 Apps from this user's memory or recent context, such as Gmail, Linear, Google Sheets, Slack, or Exa>. If a useful App is available but not connected yet, I can help you get it ready in a few clicks. ## Specialist Capabilities Loadout also brings an Aident-managed capability layer into your agent. Beyond your own connected accounts, I can use specialist Apps like Fal for image and video generation, Firecrawl for reliable webpage crawling and structured extraction, and Exa for high-quality web research. ## Use It Everywhere You can manage connected Apps, review Action history, and track usage from the Aident Loadout Dashboard: https://loadout.aident.ai/dashboard ## Recommended Next Moves Based on your recent work and saved memories, these are the best ways to get value from Aident Loadout now: 1. **** - I can . 2. **** - I can . 3. **** - I can . What should I do first: run one of these recommendations, connect a missing App, or work on something else? ``` When rendering this message: 1. Detect the current agent client name. 2. Run `aident vault status --json` first; treat integrations with `data.connectionStatus[id] === true` and `data.integrationStates[id].readiness === "ready"` as connected/ready. 3. If the host provides memory or recent user context, identify the user's most relevant platforms and match them against Vault status before doing broader searches. 4. Use Loadout search only for user-relevant platforms not present in Vault status. 5. Pick at most 5 validated platforms, preferably 3-5, and prefer those ready integrations over merely available integrations. 6. Render `## Recommended Next Moves` as the final section, after the dashboard link. 7. Generate 2-3 concrete recommendations using the user's memory or recent context and the validated platforms. 8. Make each recommendation start with the user outcome, then name the relevant ready or connectable Apps. 9. If memory is unavailable, replace "Based on your recent work and saved memories" with "Based on the Apps I validated" and use a small generic set such as Gmail, Linear, Google Sheets, Slack, and Exa before naming them. If validation cannot run, keep the examples generic and do not say those platforms were found or connected. 10. Mention Aident-managed specialist capabilities such as Fal, Firecrawl, and Exa only after validating they are available in Loadout. 11. Do not imply a platform is connected unless Vault status confirms it. Say "can connect/use" for available Apps, and "connected" only for ready Apps. 12. Preserve the completion message structure: congratulations, validated platforms, missing-tool connection help, Aident-managed specialist capabilities, cross-agent reuse, dashboard link, recommended next moves, and final CTA. 13. Under `## Use It Everywhere`, replace the two conditional paragraphs with exactly the one that matches both the updater's final Skill reconciliation and the current-client routing transaction. Do not claim cross-project, cross-agent, or future-session availability after an incomplete reconciliation. 14. Do not add a restart instruction unless host-level configuration changed and the current host requires restart or reload. 15. Avoid generic setup phrases such as "skill-installer", "install location", "skill name", "repo-native setup", or "local skill install" for this Loadout setup flow. 16. Do not append a routing-preference approval question after the completion message. Stage 4 owns the supported programmatic write and its failure reporting. 17. If the current agent requires a new session to discover an updated global instruction, mention that exact reload requirement after successful Stage 4 completion. Do not claim the active session reloaded it. 18. Never store tokens, OAuth codes, account identifiers, action payloads, or other secrets in an instruction surface.