cbd (server + TUI in one process) and cbd-tui (standalone client) both read cbd-tui.toml, so pointing that file at a remote server for cbd-tui also dragged cbds local TUI to the remote while its in-process server ran unused. cbd now reads its own cbd.toml (same options, same localhost default that matches its embedded server), so a self-contained cbd and a remote-pointed cbd-tui coexist on one machine without their address settings colliding. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||