@minnio/attune

The Attune CLI, for callers with no browser: a skill running in another repo, a CI step, a post-deploy hook. It talks to the same /api/mcp endpoint Claude does.

Agents propose. Humans release. There is no publish command, because an agent key holds no scope that can publish.

Install

npm install -g @minnio/attune

Then install the skills that drive it:

attune install-skills

That copies five skills into ~/.claude/skills and records the version they came from. Existing skills are kept, not overwritten; pass --force if you want yours replaced.

Connect

In Attune, go to Settings → Agents & CLI and create a key. Copy it. Only a hash is stored, so that is the one and only time it is shown.

echo 'attn_ag_…' | attune login --url https://your-workspace.example

Pipe the key rather than passing --key: a flag lands in your shell history and is visible in ps. In CI, skip the file and set ATTUNE_URL and ATTUNE_API_KEY instead. Set both or neither.

Use

attune help                           # what this CLI can express
attune whoami                         # what this key on this workspace can reach
attune clients                        # ids you can propose against
attune engagements
attune propose <id> --type … --draft --items … --signals …
attune propose-engagement --client … --name …

help is generated offline from the tool registry. whoami asks the server. They differ when a command depends on a workspace setting, which is why the second one exists.

What it cannot do

Publish anything to a client. Create or rename a client. Everything an agent queues waits in Attune's Inbox for a person to release it.