diff --git a/README.md b/README.md index 6ef7d7b..4fd4468 100644 --- a/README.md +++ b/README.md @@ -60,7 +60,8 @@ bundle names them, so there's one copy of each to keep correct. The terminal plugin gives **you** a real shell (xterm.js on a PTY) in the console, next to the chat and the code pane. It's the driver's seat: run the app, poke at it, `git commit`. It isn't an agent tool. The agent runs its own commands through `run_command`, which you -approve. The terminal's WebSocket is gated by the operator bearer. On Windows it needs +approve. The terminal's WebSocket is gated by the operator bearer, via a single-use ticket +so it also works on a fleet member behind the hub (terminal-plugin v0.5.1+). On Windows it needs `pywinpty` (declared with a `sys_platform == 'win32'` marker; the install dialog offers it). macOS and Linux use the stdlib PTY and need nothing. diff --git a/protoagent.bundle.yaml b/protoagent.bundle.yaml index 1c05381..bfb54b9 100644 --- a/protoagent.bundle.yaml +++ b/protoagent.bundle.yaml @@ -75,7 +75,7 @@ plugins: - { id: craft, builtin: true } # /code-review, /grill, /due-diligence — rituals the operator can type - { id: friction, builtin: true } # harness-friction ledger — a rough edge leaves evidence - { id: delegates, builtin: true } # delegate_to — an optional coding agent, only on the operator's say-so - - { id: terminal, url: https://github.com/protoLabsAI/terminal-plugin, ref: v0.4.1 } # the OPERATOR's shell beside chat (not an agent tool) + - { id: terminal, url: https://github.com/protoLabsAI/terminal-plugin, ref: v0.5.1 } # the OPERATOR's shell beside chat (not an agent tool) - { id: github, url: https://github.com/protoLabsAI/github-plugin, ref: v0.8.0 } # READ tools over `gh` (issues, PRs, diffs, CI, files); writes off by default enabled: [engineer, craft, friction, delegates, terminal, github] # suggested turn-on list