-
Notifications
You must be signed in to change notification settings - Fork 0
Commands
Fifteen, and you need three of them. bothy opens the workspace, bothy doctor says what is wrong, bothy config set changes a setting. The rest are
for a specific afternoon.
bothy --help prints the same list; this page says what each one actually does.
Opens the workspace in the current directory: file browser across the top, the agent and a shell below. First run fills any gaps first — it lists what is missing, asks before downloading, then opens.
| flag | |
|---|---|
--dir <path> |
open somewhere other than the current directory |
--profile <name> |
use a layout profile other than the configured one |
--window |
always open a new Ghostty window |
--in-place |
always run in the terminal you are already in |
--window and --in-place override bothy's own judgement for one run. It
normally decides by asking whether your terminal can draw images. To make the
override permanent, bothy config set workspace.launch here (or window); the
flags still win for a single run.
Reattach to this project's session, which has gone on without you. With no argument it picks the session for the current directory.
Which sessions are running, marking the one you are in:
polite-galaxy
bothy-Workbench
bothy-bothy the one you are in
The bindings worth knowing on a first day. They are Zellij's, not bothy's — bothy leaves them alone.
Twenty-eight checks against the workspace, each with a fix. This is the command the project is built around: The doctor explains the output, the severities and the capability grouping.
Which tools are in use, which version, and where each came from — bothy's own
copy or one already on your PATH:
✓ fd a faster find 10.5.0 supplied by bothy
✓ ripgrep a faster grep 15.2.0 supplied by bothy
Which pinned tools have newer releases upstream. Reports; it does not upgrade.
The pins live in bothy.lock.
Prints the Zellij layout bothy would launch, generated from the profile. For when you doubt what it is about to do.
The version, and whether it is a release or a source build.
bothy config # print the whole config
bothy config get <key> # one value
bothy config set <key> <value>
bothy config edit # open it in $EDITOR
bothy config path # where the file isconfig.toml carries schema = 1, which is bookkeeping rather than a setting —
config set refuses it. Unrecognised keys warn rather than fail, and bothy doctor names a retired key's replacement.
Writes the configs from your settings, then runs the doctor against the result.
Run it after changing a setting, or after replacing the binary. --dry-run
shows what it would write.
Every generated file says it is bothy's and names where to put your own changes.
Prints a blank eleven-token palette to fill in. Point bothy at the result with
bothy config set theme.palette <path>.
Prints a .desktop launcher that opens the workspace in a directory.
--install writes it; --remove deletes it. It lands outside bothy's tree by
necessity, so bothy uninstall names it rather than removing it.
Runs the agent pane in a rootless podman container, with the project directory
and the agent's credentials mounted and nothing else from $HOME. Opt-in;
there is no setting that turns it on. See
Walling off the agent — including what it deliberately
does not stop.
Works out how this copy was installed and prints the right command for it —
brew, dnf, apt, go install, the script, or a source build. It prints;
it does not upgrade.
Removes bothy's tree and the binary, and names the three things it leaves: your
settings, the container image if you confined the agent, and the desktop entry
if you added one. --dry-run shows what would go.