refactor!: rename project to bot-bottle
Assisted-by: Codex
This commit is contained in:
@@ -15,7 +15,7 @@ What's the cheapest path to that, and where does it bottom out?
|
||||
|
||||
Today the flow is bimodal. `./cli.py start <agent>` brings the
|
||||
bottle up and immediately drops you into an interactive
|
||||
`docker exec -it claude-bottle-<slug> claude ...` — claude-code
|
||||
`docker exec -it bot-bottle-<slug> claude ...` — claude-code
|
||||
owns the whole terminal until you Ctrl-D out, at which point the
|
||||
bottle tears down. The dashboard (`./cli.py dashboard`) is a
|
||||
*separate* invocation that watches across bottles but never
|
||||
@@ -68,7 +68,7 @@ Below are the actual costs.
|
||||
|
||||
The dashboard sees a key (say Enter on a selected agent in the
|
||||
agents pane). It calls `curses.endwin()`, then `subprocess.run(
|
||||
["docker", "exec", "-it", "claude-bottle-<slug>", "claude",
|
||||
["docker", "exec", "-it", "bot-bottle-<slug>", "claude",
|
||||
"--dangerously-skip-permissions"])`. claude-code takes the
|
||||
terminal full-screen. When the operator exits claude-code
|
||||
(Ctrl-D, `/exit`), the subprocess returns; the dashboard calls
|
||||
@@ -192,7 +192,7 @@ want one focused session at a time with proposals visible.
|
||||
## Option 3: External multiplexer
|
||||
|
||||
The dashboard binds a key (e.g. `Enter` on agent) to
|
||||
`tmux split-window -h 'docker exec -it claude-bottle-<slug>
|
||||
`tmux split-window -h 'docker exec -it bot-bottle-<slug>
|
||||
claude'` when run inside a tmux session, or to `osascript`-
|
||||
driven iTerm pane spawning on macOS, or to `wezterm cli
|
||||
spawn` if the user is on wezterm.
|
||||
@@ -278,7 +278,7 @@ interface; the multiplexer is convenience for power users.
|
||||
- PRD 0018 chunk 3 — agent container runs `sleep infinity`;
|
||||
claude is invoked via `docker exec -it` (the
|
||||
attachment-point this doc is layering against)
|
||||
- `claude_bottle/cli/dashboard.py:_operator_edit_flow` — the
|
||||
- `bot_bottle/cli/dashboard.py:_operator_edit_flow` — the
|
||||
existing `curses.endwin` → shell out → `stdscr.refresh()`
|
||||
pattern Option 1 would clone
|
||||
- pyte: <https://pyte.readthedocs.io/> — the candidate
|
||||
|
||||
Reference in New Issue
Block a user