Skip to content

Latest commit

 

History

History
264 lines (177 loc) · 10.3 KB

CONTRIBUTING.md

File metadata and controls

264 lines (177 loc) · 10.3 KB

Contribution Guide

Goose is open source!

We welcome pull requests for general contributions! If you have a larger new feature or any questions on how to develop a fix, we recommend you open an issue before starting.

Tip

Beyond code, check out other ways to contribute

Prerequisites

Goose includes rust binaries alongside an electron app for the GUI. To work on the rust backend, you will need to install rust and cargo. To work on the App, you will also need to install node and npm - we recommend through nvm.

We provide a shortcut to standard commands using just in our justfile.

Windows Subsystem for Linux

For WSL users, you might need to install build-essential and libxcb otherwise you might run into cc linking errors (cc stands for C Compiler). Install them by running these commands:

sudo apt update                   # Refreshes package list (no installs yet)
sudo apt install build-essential  # build-essential is a package that installs all core tools
sudo apt install libxcb1-dev      # libxcb1-dev is the development package for the X C Binding (XCB) library on Linux

Getting Started

Rust

First let's compile goose and try it out

cargo build

when that is done, you should now have debug builds of the binaries like the goose cli:

./target/debug/goose --help

If you haven't used the CLI before, you can use this compiled version to do first time configuration:

./target/debug/goose configure

And then once you have a connection to an LLM provider working, you can run a session!

./target/debug/goose session

These same commands can be recompiled and immediately run using cargo run -p goose-cli for iteration. As you make changes to the rust code, you can try it out on the CLI, or also run checks, tests, and linter:

cargo check  # do your changes compile
cargo test  # do the tests pass with your changes
cargo fmt   # format your code
./scripts/clippy-lint.sh # run the linter

Node

Now let's make sure you can run the app.

just run-ui

The start gui will both build a release build of rust (as if you had done cargo build -r) and start the electron process. You should see the app open a window, and drop you into first time setup. When you've gone through the setup, you can talk to goose!

You can now make changes in the code in ui/desktop to iterate on the GUI half of goose.

Regenerating the OpenAPI schema

The file ui/desktop/openapi.json is automatically generated during the build. It is written by the generate_schema binary in crates/goose-server. If you need to update the spec without starting the UI, run:

just generate-openapi

This command regenerates ui/desktop/openapi.json and then runs the UI's generate-api script to rebuild the TypeScript client from that spec.

Changes to the API should be made in the Rust source under crates/goose-server/src/.

Debugging

To debug the Goose server, you can run it from your preferred IDE. How to configure the command to start the server will depend on your IDE. The command to run is:

export GOOSE_SERVER__SECRET_KEY=test
cargo run --package goose-server --bin goosed -- agent   # or: `just run-server`

The server will start listening on port 3000 by default, but this can be changed by setting the GOOSE_PORT environment variable.

Once the server is running, you can start a UI and connect it to the server by running:

just debug-ui

The UI will now be connected to the server you started in your IDE, allowing you to set breakpoints and step through the server code as you interact with the UI.

Creating a fork

To fork the repository:

  1. Go to https://github.com/block/goose and click “Fork” (top-right corner).
  2. This creates https://github.com//goose under your GitHub account.
  3. Clone your fork (not the main repo):
git clone https://github.com/<your-username>/goose.git
cd goose
  1. Add the main repository as upstream:
git remote add upstream https://github.com/block/goose.git
  1. Create a branch in your fork for your changes:
git checkout -b my-feature-branch
  1. Sync your fork with the main repo:
git fetch upstream

# Merge them into your local branch (e.g., 'main' or 'my-feature-branch')
git checkout main
git merge upstream/main
  1. Push to your fork. Because you’re the owner of the fork, you have permission to push here.
git push origin my-feature-branch
  1. Open a Pull Request from your branch on your fork to block/goose’s main branch.

Keeping Your Fork Up-to-Date

To ensure a smooth integration of your contributions, it's important that your fork is kept up-to-date with the main repository. This helps avoid conflicts and allows us to merge your pull requests more quickly. Here’s how you can sync your fork:

Syncing Your Fork with the Main Repository

  1. Add the Main Repository as a Remote (Skip if you have already set this up):

    git remote add upstream https://github.com/block/goose.git

  2. Fetch the Latest Changes from the Main Repository:

    git fetch upstream

  3. Checkout Your Development Branch:

    git checkout your-branch-name

  4. Merge Changes from the Main Branch into Your Branch:

    git merge upstream/main

    Resolve any conflicts that arise and commit the changes.

  5. Push the Merged Changes to Your Fork:

    git push origin your-branch-name

This process will help you keep your branch aligned with the ongoing changes in the main repository, minimizing integration issues when it comes time to merge!

Before Submitting a Pull Request

Before you submit a pull request, please ensure your fork is synchronized as described above. This check ensures your changes are compatible with the latest in the main repository and streamlines the review process.

If you encounter any issues during this process or have any questions, please reach out by opening an issue here, and we'll be happy to help.

Env Vars

You may want to make more frequent changes to your provider setup or similar to test things out as a developer. You can use environment variables to change things on the fly without redoing your configuration.

Tip

At the moment, we are still updating some of the CLI configuration to make sure this is respected.

You can change the provider goose points to via the GOOSE_PROVIDER env var. If you already have a credential for that provider in your keychain from previously setting up, it should reuse it. For things like automations or to test without doing official setup, you can also set the relevant env vars for that provider. For example ANTHROPIC_API_KEY, OPENAI_API_KEY, or DATABRICKS_HOST. Refer to the provider details for more info on required keys.

Enable traces in Goose with locally hosted Langfuse

  • Start a local Langfuse using the docs here. Create an organization and project and create API credentials.
  • Set the environment variables so that Goose can connect to the langfuse server:
export LANGFUSE_INIT_PROJECT_PUBLIC_KEY=publickey-local
export LANGFUSE_INIT_PROJECT_SECRET_KEY=secretkey-local

Then you can view your traces at http://localhost:3000

Conventional Commits

This project follows the Conventional Commits specification for PR titles. Conventional Commits make it easier to understand the history of a project and facilitate automation around versioning and changelog generation.

Developer Certificate of Origin

This project requires a Developer Certificate of Origin sign-offs on all commits. This is a statement indicating that you are allowed to make the contribution and that the project has the right to distribute it under its license. When you are ready to commit, use the --signoff flag to attach the sign-off to your commit.

git commit --signoff ...

Other Ways to Contribute

There are numerous ways to be an open source contributor and contribute to Goose. We're here to help you on your way! Here are some suggestions to get started. If you have any questions or need help, feel free to reach out to us on Discord.

  • Stars on GitHub: If you resonate with our project and find it valuable, consider starring our Goose on GitHub! 🌟
  • Ask Questions: Your questions not only help us improve but also benefit the community. If you have a question, don't hesitate to ask it on Discord.
  • Give Feedback: Have a feature you want to see or encounter an issue with Goose, click here to open an issue, start a discussion or tell us on Discord.
  • Participate in Community Events: We host a variety of community events and livestreams on Discord every month, ranging from workshops to brainstorming sessions. You can subscribe to our events calendar or follow us on social media to stay in touch.
  • Improve Documentation: Good documentation is key to the success of any project. You can help improve the quality of our existing docs or add new pages.
  • Help Other Members: See another community member stuck? Or a contributor blocked by a question you know the answer to? Reply to community threads or do a code review for others to help.
  • Showcase Your Work: Working on a project or written a blog post recently? Share it with the community in our #share-your-work channel.
  • Give Shoutouts: Is there a project you love or a community/staff who's been especially helpful? Feel free to give them a shoutout in our #general channel.
  • Spread the Word: Help us reach more people by sharing Goose's project, website, YouTube, and/or Twitter/X.