desktop version in linux, auto approve in cli

[ali-ghamdan]

Please explain the motivation behind the feature request.
Does this feature solve a particular problem you have been experiencing? What opportunities or use cases would be unlocked with this feature? yes, gui could be simpler and easier than cli

Describe the solution you'd like
linux want the desktop version of goose.

Describe alternatives you've considered
disable auto approve for MCP in cli

Additional context
None

• I have verified this does not duplicate an existing feature request

[Jay4242]

I would even settle for a webui. basic-nodejs-webui was my quick attempt. idk how to load extensions into the bot correctly, among other things.

[Sariel2]

mark

[rcd27]

This is how I've build Goose for my Ubuntu22:

Building Goose on Linux

This guide will help you build and run Goose on Linux systems. The process has been tested on Ubuntu 22.04 LTS.

Prerequisites

1. Node.js and npm

   • Install Node.js version 22 or higher using nvm:

   curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
   source ~/.bashrc
   nvm install 22
   nvm use 22

2. Rust and Cargo

   • Install Rust using rustup:

   curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
   source $HOME/.cargo/env

3. Protobuf Compiler (protoc)

   • Install protoc version 3.12.0 or higher:

   # Download and install protoc 3.12.0
   wget https://github.com/protocolbuffers/protobuf/releases/download/v3.12.0/protoc-3.12.0-linux-x86_64.zip
   unzip protoc-3.12.0-linux-x86_64.zip
   sudo cp bin/protoc /usr/local/bin/
   sudo cp -r include/* /usr/local/include/

4. Additional Dependencies

   sudo apt-get update
   sudo apt-get install -y \
       build-essential \
       pkg-config \
       libssl-dev \
       libclang-dev \
       libgtk-3-dev \
       libwebkit2gtk-4.0-dev \
       libappindicator3-dev \
       librsvg2-dev \
       patchelf

Building the Application

1. Clone the Repository

   git clone git@github.com:block/goose.git
   cd goose

2. Build the Server

   # Build the server in release mode
   cargo build -p goose-server --release
   
   # Copy the server binary to the desktop app directory
   cp target/release/goosed ui/desktop/

3. Build and Run the Desktop Application

   cd ui/desktop
   npm install
   npm run start-gui

Creating a Desktop Shortcut

1. Create a .desktop file

   printf "[Desktop Entry]
   Version=1.0
   Type=Application
   Name=Goose
   Comment=Goose Desktop Application
   Exec=gnome-terminal -- bash -c 'export PATH=/home/\$USER/.nvm/versions/node/v22.15.0/bin:\$PATH && cd /path/to/goose/ui/desktop && npm run start-gui; echo Press Enter to close...; read'
   Path=/path/to/goose/ui/desktop
   Icon=/path/to/goose/ui/desktop/src/images/icon.png
   Terminal=true
   Categories=Development;IDE;
   StartupWMClass=Goose" | sudo tee /usr/share/applications/goose.desktop

2. Make the .desktop file executable

   sudo chmod +x /usr/share/applications/goose.desktop

3. Create a desktop shortcut (optional)

   ln -s /usr/share/applications/goose.desktop ~/Desktop/

Troubleshooting

1. Node.js Version Issues

   • Make sure you're using Node.js version 22 or higher
   • Verify the version with node --version
   • If needed, switch versions using nvm use 22

2. Protoc Version Issues

   • Verify protoc version with protoc --version
   • If the version is incorrect, reinstall using the steps in Prerequisites

3. Build Errors

   • Make sure all dependencies are installed
   • Check that the server binary is copied to the correct location
   • Verify that all paths in the .desktop file are correct for your system

4. Server Binary Issues

   • If the application fails to start, check if goosed exists in ui/desktop/
   • Verify the binary permissions: ls -l ui/desktop/goosed
   • If missing, rebuild and copy the binary again

Notes

• Replace /path/to/goose with the actual path to your Goose installation
• The application requires a terminal window to show output and potential errors
• Make sure to update the Node.js path in the .desktop file if you're using a different version
• Always verify the server binary is present before running the application