Skip to content
Merged
Show file tree
Hide file tree
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/copilot-instructions.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@
## Project-Specific Context

- This is a Rust project using cargo workspaces
- Core crates: `goose` (agent logic), `goose-cli` (CLI), `goose-server` (backend), `goose-mcp` (MCP servers)
- Core crates: `goose` (agent logic and ACP server), `goose-cli` (CLI), `goose-mcp` (MCP servers)
- Error handling: Use `anyhow::Result`, not `unwrap()` in production code
- Async runtime: tokio
- MCP protocol implementations require extra scrutiny
Expand Down
292 changes: 0 additions & 292 deletions .github/workflows/docs-update-recipe-ref.yml

This file was deleted.

2 changes: 1 addition & 1 deletion .github/workflows/goose-issue-solver.yml
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ env:
- Deletion is a feature: ask "can I delete code instead of adding?"
- Complete changes: update ALL usages when changing a type. No exceptions.
- When changing message types, update ALL provider format functions.
- When changing server routes, run `just generate-openapi`.
- When changing ACP request/response types, run `just generate-acp-types`.
- Your context degrades. The TODO is your memory. Update it after each step.

Types:
Expand Down
22 changes: 8 additions & 14 deletions BUILDING_LINUX.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,13 +59,7 @@ cd goose
Build Goose CLI:

```bash
cargo build --release -p goose-cli
```

Build Goose Server:

```bash
cargo build --release -p goose-server
cargo build --release -p goose-cli --bin goose
```

This command should give you a list of possible packages in the
Expand All @@ -80,9 +74,9 @@ cargo test -p
cd ui/desktop
pnpm install

# Copy the server binary to the expected location
# Copy the goose binary to the expected location
mkdir -p src/bin
cp ../../target/release/goosed src/bin/
cp ../../target/release/goose src/bin/
```

### 4. Build the Application
Expand Down Expand Up @@ -143,10 +137,10 @@ cd /path/to/goose/ui/desktop/out/goose-linux-x64
./goose 2>&1 | grep -v "GLib-GObject" | grep -v "browser_main_loop"
```

#### Server Binary Not Found
If you see "Could not find goosed binary", ensure you've:
1. Built the Rust backend: `cargo build --release -p goose-server`
2. Copied it to the right location: `cp ../../target/release/goosed src/bin/`
#### Goose Binary Not Found
If you see "Goose binary not found", ensure you've:
1. Built the Rust binary: `cargo build --release -p goose-cli --bin goose`
2. Copied it to the right location: `cp ../../target/release/goose src/bin/`
3. Rebuilt the application: `pnpm run make`

### Distribution-Specific Notes
Expand Down Expand Up @@ -177,7 +171,7 @@ Building as Snap packages is not currently supported but may be added in the fut

For active development:

1. **Backend changes**: Rebuild with `cargo build --release -p goose-server` and copy the binary
1. **Backend changes**: Rebuild with `cargo build --release -p goose-cli --bin goose` and copy the binary
2. **Frontend changes**: Use `pnpm run start` for hot reload during development
3. **Full rebuild**: Run the complete build process above

Expand Down
Loading
Loading