- The CLI can now persist login credentials locally, so repeated commands do not require signing in every time.
- Added managed prompt commands:
aim prompt install,aim prompt update, andaim prompt remove. - Added pull-request workflows to the CLI, including local-versus-remote diffs, pull-request creation for instructions, profiles, and prompts, and bulk diff support with
aim pr diff alland--all.
AIM CLI
Install approved A.I.M. instructions, profiles, and prompts into local project files, reuse stored sign-in, and open pull requests from local edits.
bash -c "$(curl -fsSL https://cli.ben-fischer.dev/installer)" -- aim-cliOverview
Overview
aim-cli installs approved A.I.M. instructions, profiles, and prompts into local project files so teams can reuse reviewed guidance without copying content by hand.
Authenticated commands sign in to the A.I.M. API, let you choose a tenant, and can reuse an opt-in stored login for later runs. The CLI writes instruction and profile content into AGENTS.md, tracks ownership in .aim-instructions.yaml, stores prompts in .aim-prompts, and can open pull requests from local edits.
.aim-prompts.~/.aim-cli/auth.json so repeated commands can skip the email and password prompts.Keep direct installs, profile ownership, and prompt paths in a sibling .aim-instructions.yaml manifest.
USPs & Features
Features
~/.aim-cli/auth.json and fall back to interactive sign-in only when needed.AGENTS.md by hand..aim-prompts.AGENTS.md, track ownership in the manifest, and store prompts in .aim-prompts.A directly installed instruction can be updated or removed on its own. Instructions that only exist because of a profile are managed through that profile, while prompts are managed through the prompt commands.
AIM CLI Guides
Jump into the full documentation hub for setup, workflows, and references.
Latest Releases
View all releasesFirst stable release of A.I.M.