acpbot

Documentation

Repos

Workspace roots via acpbot repo manager and folder browser.

Named workspace roots live in config.toml under [repos].
Telegram /new uses these keys as the repo picker. Without at least one repo, you cannot start a session.

Each key is one project directory (the agent’s cwd). A parent such as ~/Projects or ~/code is not a workspace and does not register the projects inside it.

During acpbot setup the folder browser often opens on that parent. Browse into the project, then Use this folder. Add further projects later:

acpbot repo add
[repos]
acpbot = "/Users/you/code/acpbot"
demo   = "/Users/you/code/demo"

Paths are absolute workspace roots on the machine that runs acp-host for that repo.
To run agents on another machine, bind the repo with table form and host = "…" — see Multi-host.

Commands

acpbot repo                 # interactive manager (list / add / edit / remove)
acpbot repo list            # print keys → paths
acpbot repo add             # key + folder browser
acpbot repo add <key>       # browser for path
acpbot repo add <key> <path>
acpbot repo set <key> [path]
acpbot repo remove <key>
acpbot repo browse          # pick folder first, then key
acpbot repo path <key>      # print path only
acpbot repos …              # alias

Folder browser

When a path is not given on the CLI (or you choose Browse folders…):

  • Arrow keys move; Use this folder (this project, not its subfolders) confirms the cwd for that repo key
  • .. goes up; Home jumps to $HOME
  • Subfolders are listed (non-hidden)
  • Type path… accepts absolute or ~/… paths

acpbot setup uses the same browser. Confirming the parent (the “projects folder”) does not add every child project. Pick the project you want /new to use.

Config write

Only the [repos] table is rewritten; bot token, speech, OAuth, etc. are left alone.
Empty list becomes a commented stub (# [repos]).

Apply changes

Host and worker hot-reload [repos] (and a few other fields) from config.toml when the file changes — usually within ~1s after acpbot repo add / save.

No restart needed for /new to see new keys. Boot logs show hot-reload on.

Still restart if you change bot_token, paths (state_dir / store_path), or OAuth listen bind.