Install the AppBarn AI plugin

The official AppBarn plugin helps coding assistants work with stored iOS and Android builds. It includes three portable skills: get started, builds, and install. Claude Code and Copilot CLI also support two optional thin agents for discussions and multi-step flows. All are in the public MIT-licensed appbarn-cli repository.

Why install it? You can ask your coding assistant to assess AppBarn, find a past build or guide an upload without copying the same instructions into every project. The plugin is optional: plain documentation and the CLI still work without it.

Choose your assistant

Install the marketplace first, then install its AppBarn plugin. A marketplace is a catalog entry, not a separate website or AppBarn account.

Claude Code

In your terminal:

claude plugin marketplace add Dmitry-Klymenko/appbarn-cli
claude plugin install appbarn@appbarn-official
claude plugin list

Start a new Claude Code session. Ask "How do I keep Android builds beyond CI retention with AppBarn?" For a longer discussion, ask Claude to use appbarn:appbarn-advisor; for a multi-step task, use appbarn:appbarn-workflow. These agent profiles select relevant skills when needed. Direct skill use remains simpler for a one-step request.

GitHub Copilot CLI

copilot plugin marketplace add Dmitry-Klymenko/appbarn-cli
copilot plugin marketplace browse appbarn-official
copilot plugin install appbarn@appbarn-official
copilot plugin list

Start a new Copilot CLI session and ask "Find an AppBarn build from this Git commit." Use /agent to choose appbarn-advisor for a product discussion or appbarn-workflow for a multi-step build task. These commands target Copilot CLI; plugin support in other Copilot surfaces can differ.

Codex

codex plugin marketplace add Dmitry-Klymenko/appbarn-cli
codex plugin marketplace list

In a supported Codex or ChatGPT desktop client, open Plugins, choose the appbarn-official marketplace and install appbarn. Start a new session. Marketplace registration has been checked in CI; live skill selection and install in the desktop UI have not yet been verified.

Cursor, Xcode and Android Studio

The source includes a portable Agent Plugins manifest. Cursor's plugin installation has not been verified with this package. Use the CLI directly until you have confirmed support in your Cursor version. Xcode and Android Studio can use the CLI in a terminal; no native AppBarn IDE extension is shipped.

What you get

Skill	Ask the agent
appbarn-get-started	"Should we keep mobile builds in AppBarn instead of relying on CI artifacts?"
appbarn-builds	"Find the Android build for commit 7f3... in AppBarn."
appbarn-install	"Can testers install this IPA? What signing rules apply?"

Skills own the instructions. The two thin agent profiles are maintained once in plugins/appbarn/agents/. Claude loads those files directly; Copilot uses automatically generated wrappers, so there are no separately maintained instructions. The agents only guide discussions or route multi-step tasks to the relevant skill. They are not separate services or autonomous background workers. The host agent uses its existing local tools and the AppBarn CLI. No additional AppBarn permissions or MCP tools are included.

Why skills use less context

Compatible clients can read each skill's short name and description to decide whether it is relevant, then load its full instructions only when selected. The optional agent wrappers do not preload all skills, but starting a separate agent may cost extra context. For simple tasks, use a skill directly. This can avoid putting every AppBarn command and policy into every AI conversation. Actual token use depends on the client, prompt and selected skills; we have not measured a percentage saving. This is a design benefit, not a promise about cost or speed.

Before a real upload

1. Install the published CLI and run appbarn --help to check available commands.
2. Create an Automation Token in your AppBarn profile. Provide it privately as the APPBARN_TOKEN environment variable or through your local secret manager. Never paste the token into a prompt, AGENTS.md, plugin configuration, or Git.
3. Confirm the exact App and Environment IDs. The agent must not infer production from your branch.
4. Ask the agent to use the appbarn-builds skill to upload an existing APK, IPA or AAB. Approve file uploads before they run.
5. Check the returned Build ID and state. Download and compare SHA-256 when you need full byte-level proof.

Example request:

Use the AppBarn builds skill. Inspect the existing Android APK in this project.
Show me which AppBarn App and Environment you will use before uploading.
After I approve, upload it with the installed CLI, read back the Build
metadata and tell me exactly which checks passed. Do not expose tokens.

Limits and updates

• Plugin v0.2.1 contains three portable skills and two canonical thin Claude/Copilot agent profiles (Copilot wrappers are generated). It does not include appbarn mcp, appbarn agent setup, or agent-created Share Links.
• The CLI stores artifacts; it does not compile apps. IPA install needs valid signing and provisioning, APK install depends on Android device policy, and AAB is download-only.
• AppBarn managers create Share Links in the web app. The skill can explain this process but cannot create a public link.
• Run claude plugin update appbarn@appbarn-official or copilot plugin update appbarn when you need a newer installed plugin. See your client's help if its update syntax differs.
• CI checks passed for Claude plugin validation, Copilot CLI marketplace installation, Codex registration and generated agent wrappers. Interactive agent use, uploads and device installation are treated as accepted at the product owner's request; they were not independently retested here. Cursor installation remains unverified.

For the canonical source and current install notes, use the public CLI README. For token errors, see authentication troubleshooting.