abbot

abbot is the Rust CLI for the Abbotik API. By default it talks to the public API at https://api.abbotik.com.

The CLI stores its default config at ~/.config/abbot/cli/config.toml. Pass --config <name> to use an isolated profile at ~/.config/abbot/cli/configs/<name>.toml instead.

Two human-first inspection commands now exist:

• abbot config to manage named config profiles and inspect local config state
• abbot doctor to check the live server connection, health, and auth state
• abbot update to refresh the current CLI binary using the install method it detects
• abbot command <path...> to print the embedded markdown doc for a command path

Release and install

The release process is tag-based and publishes GitHub Release assets for:

• x86_64-unknown-linux-gnu
• aarch64-unknown-linux-gnu
• x86_64-apple-darwin
• aarch64-apple-darwin
• Homebrew artifacts mirrored to abbotik/homebrew-releases
• Homebrew formula published in abbotik/tap

Curl install

Install from the latest GitHub release:

curl -fsSL https://raw.githubusercontent.com/abbotik/cli/main/scripts/install.sh | bash

To pin a version:

ABBOTIK_CLI_VERSION=v1.8.0 \
  curl -fsSL https://raw.githubusercontent.com/abbotik/cli/main/scripts/install.sh | bash

Homebrew install

brew install abbotik/tap/abbot

Optional install directory:

ABBOTIK_CLI_INSTALL_DIR="$HOME/bin" \
  curl -fsSL https://raw.githubusercontent.com/abbotik/cli/main/scripts/install.sh | bash

Once installed, abbot update distinguishes the current binary's install path:

• Homebrew installs run brew upgrade abbotik/tap/abbot
• curl installs pull the latest GitHub release asset and replace the current binary in place

Extra update modes:

• abbot update --version-list shows published release versions without installing
• abbot update --version v1.7.0 installs that exact published release for curl-installed binaries

Exact version installs are not supported for Homebrew-managed binaries because the tap formula tracks the current release.

Current state

The CLI now has a shared API helper layer plus command-family dispatch wired up to Abbotik routes. The data family is aligned to Abbotik's model, record, relationship, and nested-child route shapes, with query flags threaded through the request helpers.

For a new user, the intended first steps are:

abbot --config staging auth login --tenant acme --username alice --password secret
abbot --config staging data list rooms
abbot --config staging tui

Each named config keeps its own saved token, base URL overrides, output format, and machine-auth metadata.

For scripting, ABBOTIK_CONFIG=<name> selects the same profile as --config <name>, and the CLI flag wins when both are present.

For a new user, the intended first steps are:

1. abbot auth register --tenant <tenant> --username <user> --email <email> --password <password>
2. abbot auth login --tenant <tenant> --username <user> --password <password> if you need a fresh session later
3. abbot public llms or abbot docs root
4. abbot health

abbot auth register now follows the API contract change by registering first and then immediately completing /auth/login so the CLI still lands with a saved JWT.

For users joining an existing tenant, the invite flow is:

1. Existing root or full user runs abbot user invite --username <user> --invite-type human|machine
2. Human invitees run abbot auth register --tenant <tenant> --username <user> --invite-code <code> --email <email> --password <password>
3. Machine invitees run abbot auth provision --tenant <tenant> --username <user> --invite-code <code> --public-key @~/.config/abbot/abbotik.pub
4. Invited humans can later use abbot auth login; invited machines finish with abbot auth verify or abbot auth machine connect

Machine clients should use:

1. abbot auth machine connect --tenant <tenant> --username <user> --key ~/.config/abbot/abbotik.key
2. abbot auth refresh when the saved machine token expires; abbot auto-detects public-key auth and runs challenge→sign→verify using the saved key path
3. abbot user machine-keys list

TUI

abbot tui opens a terminal operator console over the real Abbotik room and factory APIs.

Current v1 behavior:

• reuses the saved CLI base URL and bearer token
• shows grouped room and factory rails
• loads room history from /llm/room/:id/history
• sends room turns through /v1/responses
• shows read-only factory overview, stage, issue, checkpoint, artifact, and review views

Typical flow:

abbot auth login --tenant acme --username alice --password secret-pass
abbot tui

Low-level machine-auth commands still exist for manual control:

1. abbot auth provision --tenant <tenant> --username <user> --public-key @~/.config/abbot/abbotik.pub --save-private-key-path ~/.config/abbot/abbotik.key
2. Sign the returned nonce with the matching private key
3. abbot auth verify --tenant <tenant> --challenge-id <id> --signature @signature.txt