Clarify Acme agent path
This commit is contained in:
parent
d5fa7de244
commit
8402a85bd9
|
|
@ -116,14 +116,14 @@ echo "$prompt" | o "$OLLIE_SESSION/$OLLIE_AGENT" prompt
|
|||
OllieHere: acme/6c460de7
|
||||
```
|
||||
|
||||
The path can be passed to optional Acme UI components that borrow existing `o` functionality:
|
||||
The path can be passed to `win`, which runs an ordinary command inside an embedded Acme terminal window:
|
||||
|
||||
```sh
|
||||
win o acme/6c460de7 read chat
|
||||
win o acme/6c460de7 prompt
|
||||
```
|
||||
|
||||
The first component displays the agent chat stream in an Acme window. The second provides the prompt REPL in Acme. Neither component is required; they are ordinary Acme commands using the session path printed by `OllieHere`.
|
||||
`OllieHere` prints the `session/agent` path. `win` starts the command line in Acme. The remainder is the command and its arguments; `win` runs it and exits when the command exits. The first command displays the agent chat stream in the embedded terminal. The second runs the prompt REPL there. These are ordinary terminal commands, not special Acme UI components.
|
||||
|
||||
### Kate
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue