feat: onboarding UX for the TUI (#8513)
This commit is contained in:
+18
-1
@@ -9,13 +9,30 @@ https://github.com/aaif-goose/goose/discussions/7309
|
||||
|
||||
The TUI automatically launches the goose ACP server using the `goose acp` command.
|
||||
|
||||
### Development (from source)
|
||||
|
||||
When running from source, `npm start` automatically builds the Rust binary from the workspace root if needed:
|
||||
|
||||
```bash
|
||||
cd ui/text
|
||||
npm i
|
||||
npm run start
|
||||
```
|
||||
|
||||
To use a custom server URL instead:
|
||||
The `dev:binary` script checks if the Rust binary needs rebuilding by comparing timestamps of:
|
||||
- `target/release/goose` binary
|
||||
- `Cargo.toml` and `Cargo.lock`
|
||||
- `crates/goose-cli/Cargo.toml`
|
||||
|
||||
If any source files are newer, it runs `cargo build --release -p goose-cli` automatically.
|
||||
|
||||
### Production (with prebuilt binaries)
|
||||
|
||||
In production, the TUI uses prebuilt binaries from the `@aaif/goose-binary-*` packages installed via `postinstall`.
|
||||
|
||||
### Custom server URL
|
||||
|
||||
To use a custom server URL instead of the built-in binary:
|
||||
|
||||
```bash
|
||||
npm run start -- --server http://localhost:8080
|
||||
|
||||
Reference in New Issue
Block a user