mirror of
https://github.com/block/goose.git
synced 2026-04-28 03:29:36 +00:00
lowercase g in goose (#4832)
Some checks failed
CI / changes (push) Has been cancelled
Canary / Prepare Version (push) Has been cancelled
Deploy Documentation / deploy (push) Has been cancelled
Documentation Site Preview / deploy (push) Has been cancelled
Publish Docker Image / docker (push) Has been cancelled
Canary / Upload Install Script (push) Has been cancelled
Canary / bundle-desktop (push) Has been cancelled
Canary / bundle-desktop-linux (push) Has been cancelled
Canary / bundle-desktop-windows (push) Has been cancelled
Canary / Release (push) Has been cancelled
CI / Check Rust Code Format (push) Has been cancelled
Canary / build-cli (push) Has been cancelled
CI / Build and Test Rust Project (push) Has been cancelled
CI / Lint Electron Desktop App (push) Has been cancelled
CI / bundle-desktop-unsigned (push) Has been cancelled
Some checks failed
CI / changes (push) Has been cancelled
Canary / Prepare Version (push) Has been cancelled
Deploy Documentation / deploy (push) Has been cancelled
Documentation Site Preview / deploy (push) Has been cancelled
Publish Docker Image / docker (push) Has been cancelled
Canary / Upload Install Script (push) Has been cancelled
Canary / bundle-desktop (push) Has been cancelled
Canary / bundle-desktop-linux (push) Has been cancelled
Canary / bundle-desktop-windows (push) Has been cancelled
Canary / Release (push) Has been cancelled
CI / Check Rust Code Format (push) Has been cancelled
Canary / build-cli (push) Has been cancelled
CI / Build and Test Rust Project (push) Has been cancelled
CI / Lint Electron Desktop App (push) Has been cancelled
CI / bundle-desktop-unsigned (push) Has been cancelled
This commit is contained in:
Angie Jones
GitHub
parent
bb1b73d634
commit
2032c7099c
120 changed files with 669 additions and 651 deletions
2
.github/ISSUE_TEMPLATE/config.yml
vendored
2
.github/ISSUE_TEMPLATE/config.yml
vendored
|
|
@ -1,6 +1,6 @@
|
|||
blank_issues_enabled: false
|
||||
contact_links:
|
||||
- name: Goose Discord discussion
|
||||
- name: goose Discord discussion
|
||||
url: https://discord.gg/block-opensource
|
||||
about: Please ask and answer questions here.
|
||||
- name: Report a security vulnerability
|
||||
|
|
|
|||
22
.github/ISSUE_TEMPLATE/submit-recipe.yml
vendored
22
.github/ISSUE_TEMPLATE/submit-recipe.yml
vendored
|
|
@ -1,25 +1,25 @@
|
|||
name: 🧑🍳 Submit a Recipe to the Goose Cookbook
|
||||
description: Share a reusable Goose recipe with the community!
|
||||
name: 🧑🍳 Submit a recipe to the goose cookbook
|
||||
description: Share a reusable goose recipe with the community!
|
||||
title: "[Recipe] <your recipe title here>"
|
||||
labels: ["recipe submission"]
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
Thanks for contributing to the Goose Cookbook! 🍳
|
||||
Recipes are reusable sessions created in Goose Desktop or CLI and shared with the community to help others vibe code faster.
|
||||
Thanks for contributing to the goose cookbook! 🍳
|
||||
Recipes are reusable sessions created in goose desktop or CLI and shared with the community to help others vibe code faster.
|
||||
|
||||
📌 **How to Submit**
|
||||
- Create your recipe using Goose ("Make recipe from this session")
|
||||
- Create your recipe using goose ("Make recipe from this session")
|
||||
- Fill out the YAML below using the format provided
|
||||
- Paste it into the field and submit the issue — we'll review and add it to the Cookbook!
|
||||
- Paste it into the field and submit the issue — we'll review and add it to the cookbook!
|
||||
|
||||
🪄 **What Happens After?**
|
||||
- If accepted, we'll publish your recipe to the [Goose Recipes Cookbook](https://block.github.io/goose/recipes)
|
||||
- If accepted, we'll publish your recipe to the [goose recipes cookbook](https://block.github.io/goose/recipes)
|
||||
- You'll receive OpenRouter **LLM API credits** as a thank you!
|
||||
- Your GitHub handle will be displayed and linked on the recipe card
|
||||
- If you provide an email below, we'll email you your credits when your recipe is approved and merged.
|
||||
- If the YAML has any issues, Goose will comment with validation errors so you can fix and resubmit.
|
||||
- If the YAML has any issues, goose will comment with validation errors so you can fix and resubmit.
|
||||
|
||||
🧪 **Pro Tip:** You can test your recipe locally in your terminal with:
|
||||
`goose recipe validate your-recipe.yaml`
|
||||
|
|
@ -28,7 +28,7 @@ body:
|
|||
id: recipe-yaml
|
||||
attributes:
|
||||
label: Paste Your Full Recipe YAML Below
|
||||
description: Use the structure below and we’ll auto-fill your GitHub handle for `author.contact` after submission.
|
||||
description: Use the structure below and we'll auto-fill your GitHub handle for `author.contact` after submission.
|
||||
placeholder: |
|
||||
version: "1.0.0"
|
||||
id: clean-up-feature-flag
|
||||
|
|
@ -103,8 +103,8 @@ body:
|
|||
- `id` should be lowercase, hyphenated, and unique (e.g. `my-awesome-recipe`)
|
||||
- `title` is the display name of your recipe
|
||||
- `description` should clearly explain what the recipe does
|
||||
- `instructions` are specific steps Goose should follow — supports template variables like `{{ variable_name }}`
|
||||
- `prompt` is the first thing Goose sees when the recipe is launched
|
||||
- `instructions` are specific steps goose should follow — supports template variables like `{{ variable_name }}`
|
||||
- `prompt` is the first thing goose sees when the recipe is launched
|
||||
- `parameters` should include required or optional inputs — optional ones must have `default`
|
||||
- `extensions` must follow the full format with `type`, `cmd`, `args`, `timeout`, etc.
|
||||
- `activities` describe the main actions the recipe performs
|
||||
|
|
|
|||
14
.github/scripts/send_key.py
vendored
14
.github/scripts/send_key.py
vendored
|
|
@ -148,7 +148,7 @@ def provision_api_key(provisioning_api_key):
|
|||
"Content-Type": "application/json"
|
||||
},
|
||||
json={
|
||||
"name": "Goose Contributor",
|
||||
"name": "goose contributor",
|
||||
"label": "goose-cookbook",
|
||||
"limit": 10.0
|
||||
}
|
||||
|
|
@ -167,13 +167,13 @@ def send_email(email, api_key, sendgrid_api_key):
|
|||
print("📤 Sending email via SendGrid...")
|
||||
try:
|
||||
sg = SendGridAPIClient(sendgrid_api_key)
|
||||
from_email = "Goose Team <goose@opensource.block.xyz>"
|
||||
subject = "🎉 Your Goose Contributor API Key"
|
||||
from_email = "goose team <goose@opensource.block.xyz>"
|
||||
subject = "🎉 Your goose contributor API key"
|
||||
html_content = f"""
|
||||
<p>Thank you for contributing to the <strong>Goose Recipe Cookbook</strong>!</p>
|
||||
<p>Thank you for contributing to the <strong>goose recipe cookbook</strong>!</p>
|
||||
<p>🎉 Here's your <strong>$10 OpenRouter API key</strong>:</p>
|
||||
<pre style="background-color:#f4f4f4;padding:10px;border-radius:6px;"><code>{api_key}</code></pre>
|
||||
<p>To use this in Goose (CLI or Desktop):</p>
|
||||
<p>To use this in goose (CLI or Desktop):</p>
|
||||
<ul>
|
||||
<li>Go to your <strong>Provider Settings</strong></li>
|
||||
<li>Select <strong>OpenRouter</strong> from the provider list</li>
|
||||
|
|
@ -182,7 +182,7 @@ def send_email(email, api_key, sendgrid_api_key):
|
|||
<p>📚 Full setup instructions:<br>
|
||||
<a href="https://block.github.io/goose/docs/getting-started/providers/#configure-provider">
|
||||
https://block.github.io/goose/docs/getting-started/providers/#configure-provider</a></p>
|
||||
<p>Happy coding!<br>– The Goose Team</p>
|
||||
<p>Happy coding!<br>– the goose team</p>
|
||||
"""
|
||||
message = Mail(
|
||||
from_email=from_email,
|
||||
|
|
@ -216,7 +216,7 @@ def comment_on_pr(github_token, repo_full_name, pr_number, email):
|
|||
"Accept": "application/vnd.github+json"
|
||||
},
|
||||
json={
|
||||
"body": f"✅ $10 OpenRouter API key sent to `{email}`. Thanks for your contribution to the Goose Cookbook!"
|
||||
"body": f"✅ $10 OpenRouter API key sent to `{email}`. Thanks for your contribution to the goose cookbook!"
|
||||
}
|
||||
)
|
||||
comment_resp.raise_for_status()
|
||||
|
|
|
|||
20
.github/workflows/bundle-desktop-intel.yml
vendored
20
.github/workflows/bundle-desktop-intel.yml
vendored
|
|
@ -192,10 +192,10 @@ jobs:
|
|||
source_job_url="https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}"
|
||||
unsigned_url="s3://block-goose-artifacts-bucket-production/unsigned/goose-${GITHUB_SHA}-${{ github.run_id }}-intel.zip"
|
||||
|
||||
zip -q -u -r out/Goose-darwin-x64/Goose_intel_mac.zip entitlements.plist
|
||||
zip -q -u -r out/goose-darwin-x64/goose_intel_mac.zip entitlements.plist
|
||||
|
||||
# upload unsigned goose to transfer bucket so it can be passed to lambda
|
||||
aws s3 cp --quiet out/Goose-darwin-x64/Goose_intel_mac.zip "${unsigned_url}"
|
||||
aws s3 cp --quiet out/goose-darwin-x64/goose_intel_mac.zip "${unsigned_url}"
|
||||
|
||||
# begin signing
|
||||
echo "🚀 launching signing process"
|
||||
|
|
@ -247,7 +247,7 @@ jobs:
|
|||
|
||||
# download the signed app from S3
|
||||
echo "⬇️ downloading signed app"
|
||||
aws s3 cp --quiet "${signed_url}" out/Goose-darwin-x64/Goose_intel_mac.zip
|
||||
aws s3 cp --quiet "${signed_url}" out/goose-darwin-x64/goose_intel_mac.zip
|
||||
working-directory: ui/desktop
|
||||
|
||||
- name: Final cleanup before artifact upload
|
||||
|
|
@ -261,26 +261,26 @@ jobs:
|
|||
- name: Upload Desktop artifact
|
||||
uses: actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1 # pin@v4
|
||||
with:
|
||||
name: Goose-darwin-x64
|
||||
path: ui/desktop/out/Goose-darwin-x64/Goose_intel_mac.zip
|
||||
name: goose-darwin-x64
|
||||
path: ui/desktop/out/goose-darwin-x64/goose_intel_mac.zip
|
||||
|
||||
- name: Quick launch test (macOS)
|
||||
if: ${{ inputs.quick_test }}
|
||||
run: |
|
||||
# Ensure no quarantine attributes (if needed)
|
||||
xattr -cr "ui/desktop/out/Goose-darwin-x64/Goose.app"
|
||||
echo "Opening Goose.app..."
|
||||
open -g "ui/desktop/out/Goose-darwin-x64/Goose.app"
|
||||
xattr -cr "ui/desktop/out/goose-darwin-x64/goose.app"
|
||||
echo "Opening goose.app..."
|
||||
open -g "ui/desktop/out/goose-darwin-x64/goose.app"
|
||||
|
||||
# Give the app a few seconds to start and write logs
|
||||
sleep 5
|
||||
|
||||
# Check if it's running
|
||||
if pgrep -f "Goose.app/Contents/MacOS/Goose" > /dev/null; then
|
||||
if pgrep -f "goose.app/Contents/MacOS/goose" > /dev/null; then
|
||||
echo "App appears to be running."
|
||||
else
|
||||
echo "App did not stay open. Possible crash or startup error."
|
||||
exit 1
|
||||
fi
|
||||
# Kill the app to clean up
|
||||
pkill -f "Goose.app/Contents/MacOS/Goose"
|
||||
pkill -f "goose.app/Contents/MacOS/goose"
|
||||
|
|
|
|||
6
.github/workflows/bundle-desktop-linux.yml
vendored
6
.github/workflows/bundle-desktop-linux.yml
vendored
|
|
@ -180,21 +180,21 @@ jobs:
|
|||
- name: Upload .deb package
|
||||
uses: actions/upload-artifact@v4
|
||||
with:
|
||||
name: Goose-linux-x64-deb
|
||||
name: goose-linux-x64-deb
|
||||
path: ui/desktop/out/make/deb/x64/*.deb
|
||||
if-no-files-found: error
|
||||
|
||||
- name: Upload .rpm package
|
||||
uses: actions/upload-artifact@v4
|
||||
with:
|
||||
name: Goose-linux-x64-rpm
|
||||
name: goose-linux-x64-rpm
|
||||
path: ui/desktop/out/make/rpm/x64/*.rpm
|
||||
if-no-files-found: error
|
||||
|
||||
- name: Upload combined Linux packages
|
||||
uses: actions/upload-artifact@v4
|
||||
with:
|
||||
name: Goose-linux-x64
|
||||
name: goose-linux-x64
|
||||
path: |
|
||||
ui/desktop/out/make/deb/x64/*.deb
|
||||
ui/desktop/out/make/rpm/x64/*.rpm
|
||||
|
|
|
|||
40
.github/workflows/bundle-desktop-windows.yml
vendored
40
.github/workflows/bundle-desktop-windows.yml
vendored
|
|
@ -284,12 +284,12 @@ jobs:
|
|||
- name: Copy exe/dll to final out folder and prepare flat distribution
|
||||
run: |
|
||||
cd ui/desktop
|
||||
mkdir -p ./out/Goose-win32-x64/resources/bin
|
||||
rsync -av src/bin/ out/Goose-win32-x64/resources/bin/
|
||||
mkdir -p ./out/goose-win32-x64/resources/bin
|
||||
rsync -av src/bin/ out/goose-win32-x64/resources/bin/
|
||||
|
||||
# Create flat distribution structure
|
||||
mkdir -p ./dist-windows
|
||||
cp -r ./out/Goose-win32-x64/* ./dist-windows/
|
||||
cp -r ./out/goose-win32-x64/* ./dist-windows/
|
||||
|
||||
# Verify the final structure
|
||||
echo "📋 Final flat distribution structure:"
|
||||
|
|
@ -318,8 +318,8 @@ jobs:
|
|||
wget -q https://github.com/ebourg/jsign/releases/download/6.0/jsign-6.0.jar -O jsign.jar
|
||||
echo "05ca18d4ab7b8c2183289b5378d32860f0ea0f3bdab1f1b8cae5894fb225fa8a jsign.jar" | sha256sum -c
|
||||
|
||||
# Sign the main Electron executable (Goose.exe)
|
||||
echo "🔐 Signing main Electron executable: Goose.exe"
|
||||
# Sign the main Electron executable (goose.exe)
|
||||
echo "🔐 Signing main Electron executable: goose.exe"
|
||||
cd ui/desktop/dist-windows/
|
||||
|
||||
java -jar ${GITHUB_WORKSPACE}/jsign.jar \
|
||||
|
|
@ -329,12 +329,12 @@ jobs:
|
|||
--alias windows-codesign \
|
||||
--certfile "${GITHUB_WORKSPACE}/block-codesign-cert.pem" \
|
||||
--tsaurl "http://timestamp.digicert.com" \
|
||||
--name "Goose" \
|
||||
--name "goose" \
|
||||
--url "https://github.com/block/goose" \
|
||||
"Goose.exe"
|
||||
"goose.exe"
|
||||
|
||||
osslsigncode verify Goose.exe
|
||||
echo "✅ Main executable Goose.exe signed successfully"
|
||||
osslsigncode verify goose.exe
|
||||
echo "✅ Main executable goose.exe signed successfully"
|
||||
|
||||
# Sign the backend executable (goosed.exe)
|
||||
echo "🔐 Signing backend executable: goosed.exe"
|
||||
|
|
@ -347,7 +347,7 @@ jobs:
|
|||
--alias windows-codesign \
|
||||
--certfile "${GITHUB_WORKSPACE}/block-codesign-cert.pem" \
|
||||
--tsaurl "http://timestamp.digicert.com" \
|
||||
--name "Goose Backend" \
|
||||
--name "goose Backend" \
|
||||
--url "https://github.com/block/goose" \
|
||||
"goosed.exe"
|
||||
|
||||
|
|
@ -357,8 +357,8 @@ jobs:
|
|||
# Show final file status
|
||||
echo "📋 Final signed files:"
|
||||
cd ../../
|
||||
ls -la Goose.exe
|
||||
sha256sum Goose.exe
|
||||
ls -la goose.exe
|
||||
sha256sum goose.exe
|
||||
ls -la resources/bin/goosed.exe
|
||||
sha256sum resources/bin/goosed.exe
|
||||
|
||||
|
|
@ -371,8 +371,8 @@ jobs:
|
|||
run: |
|
||||
echo "📋 Verifying both signed executables in final distribution:"
|
||||
echo "Main executable:"
|
||||
ls -la ui/desktop/dist-windows/Goose.exe
|
||||
osslsigncode verify ui/desktop/dist-windows/Goose.exe
|
||||
ls -la ui/desktop/dist-windows/goose.exe
|
||||
osslsigncode verify ui/desktop/dist-windows/goose.exe
|
||||
echo "✅ Main executable signature verification passed"
|
||||
|
||||
echo "Backend executable:"
|
||||
|
|
@ -387,18 +387,18 @@ jobs:
|
|||
echo "📦 Creating Windows zip package..."
|
||||
|
||||
# Create a zip file from the dist-windows directory
|
||||
zip -r "Goose-win32-x64.zip" dist-windows/
|
||||
zip -r "goose-win32-x64.zip" dist-windows/
|
||||
|
||||
echo "✅ Windows zip package created:"
|
||||
ls -la Goose-win32-x64.zip
|
||||
ls -la goose-win32-x64.zip
|
||||
|
||||
# Also create the zip in the expected output structure for consistency
|
||||
mkdir -p out/Goose-win32-x64/
|
||||
cp Goose-win32-x64.zip out/Goose-win32-x64/
|
||||
mkdir -p out/goose-win32-x64/
|
||||
cp goose-win32-x64.zip out/goose-win32-x64/
|
||||
|
||||
# 11) Upload the final Windows build
|
||||
- name: Upload Windows build artifacts
|
||||
uses: actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1 # pin@v4
|
||||
with:
|
||||
name: Goose-win32-x64
|
||||
path: ui/desktop/out/Goose-win32-x64/Goose-win32-x64.zip
|
||||
name: goose-win32-x64
|
||||
path: ui/desktop/out/goose-win32-x64/goose-win32-x64.zip
|
||||
|
|
|
|||
20
.github/workflows/bundle-desktop.yml
vendored
20
.github/workflows/bundle-desktop.yml
vendored
|
|
@ -226,10 +226,10 @@ jobs:
|
|||
source_job_url="https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}"
|
||||
unsigned_url="s3://block-goose-artifacts-bucket-production/unsigned/goose-${GITHUB_SHA}-${{ github.run_id }}-arm64.zip"
|
||||
|
||||
zip -q -u -r out/Goose-darwin-arm64/Goose.zip entitlements.plist
|
||||
zip -q -u -r out/goose-darwin-arm64/goose.zip entitlements.plist
|
||||
|
||||
# upload unsigned goose to transfer bucket so it can be passed to lambda
|
||||
aws s3 cp --quiet out/Goose-darwin-arm64/Goose.zip "${unsigned_url}"
|
||||
aws s3 cp --quiet out/goose-darwin-arm64/goose.zip "${unsigned_url}"
|
||||
|
||||
# begin signing
|
||||
echo "🚀 launching signing process"
|
||||
|
|
@ -281,7 +281,7 @@ jobs:
|
|||
|
||||
# download the signed app from S3
|
||||
echo "⬇️ downloading signed app"
|
||||
aws s3 cp --quiet "${signed_url}" out/Goose-darwin-arm64/Goose.zip
|
||||
aws s3 cp --quiet "${signed_url}" out/goose-darwin-arm64/goose.zip
|
||||
working-directory: ui/desktop
|
||||
|
||||
- name: Final cleanup before artifact upload
|
||||
|
|
@ -296,26 +296,26 @@ jobs:
|
|||
id: upload-app-bundle
|
||||
uses: actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1 # pin@v4
|
||||
with:
|
||||
name: Goose-darwin-arm64
|
||||
path: ui/desktop/out/Goose-darwin-arm64/Goose.zip
|
||||
name: goose-darwin-arm64
|
||||
path: ui/desktop/out/goose-darwin-arm64/goose.zip
|
||||
|
||||
- name: Quick launch test (macOS)
|
||||
if: ${{ inputs.quick_test }}
|
||||
run: |
|
||||
# Ensure no quarantine attributes (if needed)
|
||||
xattr -cr "ui/desktop/out/Goose-darwin-arm64/Goose.app"
|
||||
echo "Opening Goose.app..."
|
||||
open -g "ui/desktop/out/Goose-darwin-arm64/Goose.app"
|
||||
xattr -cr "ui/desktop/out/goose-darwin-arm64/goose.app"
|
||||
echo "Opening goose.app..."
|
||||
open -g "ui/desktop/out/goose-darwin-arm64/goose.app"
|
||||
|
||||
# Give the app a few seconds to start and write logs
|
||||
sleep 5
|
||||
|
||||
# Check if it's running
|
||||
if pgrep -f "Goose.app/Contents/MacOS/Goose" > /dev/null; then
|
||||
if pgrep -f "goose.app/Contents/MacOS/goose" > /dev/null; then
|
||||
echo "App appears to be running."
|
||||
else
|
||||
echo "App did not stay open. Possible crash or startup error."
|
||||
exit 1
|
||||
fi
|
||||
# Kill the app to clean up
|
||||
pkill -f "Goose.app/Contents/MacOS/Goose"
|
||||
pkill -f "goose.app/Contents/MacOS/goose"
|
||||
1
.github/workflows/canary.yml
vendored
1
.github/workflows/canary.yml
vendored
|
|
@ -117,7 +117,6 @@ jobs:
|
|||
artifacts: |
|
||||
goose-*.tar.bz2
|
||||
goose-*.zip
|
||||
Goose*.zip
|
||||
*.deb
|
||||
*.rpm
|
||||
download_cli.sh
|
||||
|
|
|
|||
1
.github/workflows/nightly.yml
vendored
1
.github/workflows/nightly.yml
vendored
|
|
@ -122,7 +122,6 @@ jobs:
|
|||
artifacts: |
|
||||
goose-*.tar.bz2
|
||||
goose-*.zip
|
||||
Goose*.zip
|
||||
*.deb
|
||||
*.rpm
|
||||
download_cli.sh
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ jobs:
|
|||
- name: Download Intel artifact
|
||||
uses: actions/download-artifact@cc203385981b70ca67e1cc392babf9cc229d5806 # pin@v4
|
||||
with:
|
||||
name: Goose-darwin-x64
|
||||
name: goose-darwin-x64
|
||||
path: intel-dist
|
||||
|
||||
- name: Comment on PR with Intel download link
|
||||
|
|
@ -91,9 +91,9 @@ jobs:
|
|||
body: |
|
||||
### macOS Intel Desktop App (x64)
|
||||
|
||||
[💻 Download macOS Desktop App (Intel x64, signed)](https://nightly.link/${{ github.repository }}/actions/runs/${{ github.run_id }}/Goose-darwin-x64.zip)
|
||||
[💻 Download macOS Desktop App (Intel x64, signed)](https://nightly.link/${{ github.repository }}/actions/runs/${{ github.run_id }}/goose-darwin-x64.zip)
|
||||
|
||||
**Instructions:**
|
||||
After downloading, unzip the file and drag the Goose.app to your Applications folder. The app is signed and notarized for macOS.
|
||||
After downloading, unzip the file and drag the goose.app to your Applications folder. The app is signed and notarized for macOS.
|
||||
|
||||
This link is provided by nightly.link and will work even if you're not logged into GitHub.
|
||||
|
|
@ -95,6 +95,6 @@ jobs:
|
|||
[🪟 Download Windows Desktop App (x64, signed)](https://nightly.link/${{ github.repository }}/actions/runs/${{ github.run_id }}/desktop-windows-dist.zip)
|
||||
|
||||
**Instructions:**
|
||||
After downloading, unzip the file and run Goose.exe. The app is signed for Windows.
|
||||
After downloading, unzip the file and run goose.exe. The app is signed for Windows.
|
||||
|
||||
This link is provided by nightly.link and will work even if you're not logged into GitHub.
|
||||
|
|
|
|||
6
.github/workflows/pr-comment-bundle.yml
vendored
6
.github/workflows/pr-comment-bundle.yml
vendored
|
|
@ -125,7 +125,7 @@ jobs:
|
|||
- name: Download ARM64 artifact
|
||||
uses: actions/download-artifact@cc203385981b70ca67e1cc392babf9cc229d5806 # pin@v4
|
||||
with:
|
||||
name: Goose-darwin-arm64
|
||||
name: goose-darwin-arm64
|
||||
path: arm64-dist
|
||||
|
||||
- name: Comment on PR with ARM64 download link
|
||||
|
|
@ -135,7 +135,7 @@ jobs:
|
|||
body: |
|
||||
### macOS ARM64 Desktop App (Apple Silicon)
|
||||
|
||||
[📱 Download macOS Desktop App (arm64, unsigned)](https://nightly.link/${{ github.repository }}/actions/runs/${{ github.run_id }}/Goose-darwin-arm64.zip)
|
||||
[📱 Download macOS Desktop App (arm64, unsigned)](https://nightly.link/${{ github.repository }}/actions/runs/${{ github.run_id }}/goose-darwin-arm64.zip)
|
||||
|
||||
**Instructions:**
|
||||
After downloading, unzip the file and drag the Goose.app to a location you prefer. The app is unsigned, so to run it run `xattr -r -d com.apple.quarantine '/path/to/Goose.app'` and then open the app
|
||||
After downloading, unzip the file and drag the goose.app to a location you prefer. The app is unsigned, so to run it run `xattr -r -d com.apple.quarantine '/path/to/goose.app'` and then open the app
|
||||
6
.github/workflows/release-branches.yml
vendored
6
.github/workflows/release-branches.yml
vendored
|
|
@ -1,4 +1,4 @@
|
|||
name: Build Goose Release Candidate
|
||||
name: Build goose release candidate
|
||||
|
||||
on:
|
||||
pull_request:
|
||||
|
|
@ -24,7 +24,7 @@ jobs:
|
|||
body: |
|
||||
### macOS ARM64 Desktop App (Apple Silicon)
|
||||
|
||||
[📱 Download macOS Desktop App (arm64, unsigned)](https://nightly.link/${{ github.repository }}/actions/runs/${{ github.run_id }}/Goose-darwin-arm64.zip)
|
||||
[📱 Download macOS Desktop App (arm64, unsigned)](https://nightly.link/${{ github.repository }}/actions/runs/${{ github.run_id }}/goose-darwin-arm64.zip)
|
||||
|
||||
**Instructions:**
|
||||
After downloading, unzip the file and drag the Goose.app to a location you prefer. The app is unsigned, so to run it run `xattr -r -d com.apple.quarantine '/path/to/Goose.app'` and then open the app
|
||||
After downloading, unzip the file and drag the goose.app to a location you prefer. The app is unsigned, so to run it run `xattr -r -d com.apple.quarantine '/path/to/goose.app'` and then open the app
|
||||
|
|
|
|||
2
.github/workflows/release.yml
vendored
2
.github/workflows/release.yml
vendored
|
|
@ -106,7 +106,6 @@ jobs:
|
|||
artifacts: |
|
||||
goose-*.tar.bz2
|
||||
goose-*.zip
|
||||
Goose*.zip
|
||||
*.deb
|
||||
*.rpm
|
||||
download_cli.sh
|
||||
|
|
@ -124,7 +123,6 @@ jobs:
|
|||
artifacts: |
|
||||
goose-*.tar.bz2
|
||||
goose-*.zip
|
||||
Goose*.zip
|
||||
*.deb
|
||||
*.rpm
|
||||
download_cli.sh
|
||||
|
|
|
|||
4
.github/workflows/test-finder.yml
vendored
4
.github/workflows/test-finder.yml
vendored
|
|
@ -161,13 +161,13 @@ jobs:
|
|||
body: |
|
||||
## 🤖 Automated Test Addition
|
||||
|
||||
This PR was automatically generated by Goose to improve test coverage.
|
||||
This PR was automatically generated by goose to improve test coverage.
|
||||
|
||||
### What changed?
|
||||
Added a unit test for a previously untested function.
|
||||
|
||||
### Why?
|
||||
Part of our daily automated test coverage improvement initiative. Goose analyzes the codebase to find untested but important functions and creates focused unit tests for them.
|
||||
Part of our daily automated test coverage improvement initiative. goose analyzes the codebase to find untested but important functions and creates focused unit tests for them.
|
||||
|
||||
### Review checklist
|
||||
- [ ] Test is meaningful and actually tests the function
|
||||
|
|
|
|||
4
.github/workflows/validate-recipe-pr.yml
vendored
4
.github/workflows/validate-recipe-pr.yml
vendored
|
|
@ -30,7 +30,7 @@ jobs:
|
|||
with:
|
||||
node-version: '20'
|
||||
|
||||
- name: Install and Configure Goose
|
||||
- name: Install and Configure goose
|
||||
run: |
|
||||
mkdir -p /home/runner/.local/bin
|
||||
curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh \
|
||||
|
|
@ -219,7 +219,7 @@ jobs:
|
|||
2. If approved, we'll run a security scan
|
||||
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)
|
||||
|
||||
Thanks for contributing to the Goose Recipe Cookbook! 🎉`;
|
||||
Thanks for contributing to the goose Recipe Cookbook! 🎉`;
|
||||
} else {
|
||||
// Read validation details from file
|
||||
let validationDetails = '';
|
||||
|
|
|
|||
2
.gitignore
vendored
2
.gitignore
vendored
|
|
@ -24,7 +24,7 @@ target/
|
|||
./ui/desktop/node_modules
|
||||
./ui/desktop/out
|
||||
|
||||
# Generated Goose DLLs (built at build time, not checked in)
|
||||
# Generated goose DLLs (built at build time, not checked in)
|
||||
ui/desktop/src/bin/goose_ffi.dll
|
||||
ui/desktop/src/bin/goose_llm.dll
|
||||
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@
|
|||
|
||||
---
|
||||
|
||||
We want everyone to use Goose safely and responsibly. You agree you will not use, or allow others to use, Goose to:
|
||||
We want everyone to use goose safely and responsibly. You agree you will not use, or allow others to use, goose to:
|
||||
|
||||
### 1. Violate the law or others’ rights, including use of Goose to:
|
||||
### 1. Violate the law or others’ rights, including use of goose to:
|
||||
|
||||
a. Engage in, promote, generate, contribute to, encourage, plan, incite, or further illegal or unlawful activity or content, such as:
|
||||
- Violence or terrorism
|
||||
|
|
@ -26,7 +26,7 @@ f. Infringe or misappropriate any third-party rights, including intellectual pro
|
|||
|
||||
g. Create, generate, or facilitate the creation of malicious code, malware, computer viruses, or do anything else in an intentional or malicious way without third-party consent that could disable, overburden, interfere with, or impair the proper working, integrity, operation, or appearance of a website or computer system.
|
||||
|
||||
### 2. Engage in, promote, incite, facilitate, or assist in the planning or development of activities that present a risk of death or bodily harm to individuals, including use of Goose related to the following:
|
||||
### 2. Engage in, promote, incite, facilitate, or assist in the planning or development of activities that present a risk of death or bodily harm to individuals, including use of goose related to the following:
|
||||
|
||||
a. Guns and illegal weapons (including weapon development).
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ b. Illegal drugs and regulated/controlled substances.
|
|||
|
||||
c. Any content intended to incite or promote violence, abuse, or any infliction of bodily harm to an individual.
|
||||
|
||||
### 3. Intentionally deceive or mislead others or engage in other abusive or fraudulent activities, including use of Goose related to the following:
|
||||
### 3. Intentionally deceive or mislead others or engage in other abusive or fraudulent activities, including use of goose related to the following:
|
||||
|
||||
a. Generating, promoting, or furthering fraud or fraudulent activities, scams, phishing, or malware.
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ f. Compromising security systems or gaining unauthorized access to computer syst
|
|||
|
||||
---
|
||||
|
||||
You also agree that you will not use, or allow others to use, Goose in violation of any agreements that you have with, or commitments you have made to, third parties. This may include any licenses, agreements, and other terms that apply to the models you use with Goose.
|
||||
You also agree that you will not use, or allow others to use, goose in violation of any agreements that you have with, or commitments you have made to, third parties. This may include any licenses, agreements, and other terms that apply to the models you use with goose.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# AGENTS Instructions
|
||||
|
||||
Goose is an AI agent framework in Rust with CLI and Electron desktop interfaces.
|
||||
goose is an AI agent framework in Rust with CLI and Electron desktop interfaces.
|
||||
|
||||
## Setup
|
||||
```bash
|
||||
|
|
|
|||
|
|
@ -1,18 +1,18 @@
|
|||
# Building and Running Goose with Docker
|
||||
# Building and Running goose with Docker
|
||||
|
||||
This guide covers building Docker images for Goose CLI for production use, CI/CD pipelines, and local development.
|
||||
This guide covers building Docker images for goose CLI for production use, CI/CD pipelines, and local development.
|
||||
|
||||
## Quick Start
|
||||
|
||||
### Using Pre-built Images
|
||||
|
||||
The easiest way to use Goose with Docker is to pull the pre-built image from GitHub Container Registry:
|
||||
The easiest way to use goose with Docker is to pull the pre-built image from GitHub Container Registry:
|
||||
|
||||
```bash
|
||||
# Pull the latest image
|
||||
docker pull ghcr.io/block/goose:latest
|
||||
|
||||
# Run Goose CLI
|
||||
# Run goose CLI
|
||||
docker run --rm ghcr.io/block/goose:latest --version
|
||||
|
||||
# Run with LLM configuration
|
||||
|
|
@ -61,7 +61,7 @@ For multi-platform builds:
|
|||
docker buildx build --platform linux/amd64,linux/arm64 -t goose:multi .
|
||||
```
|
||||
|
||||
## Running Goose in Docker
|
||||
## Running goose in Docker
|
||||
|
||||
### CLI Mode
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ docker-compose run --rm goose session
|
|||
|
||||
### Environment Variables
|
||||
|
||||
The Docker image accepts all standard Goose environment variables:
|
||||
The Docker image accepts all standard goose environment variables:
|
||||
|
||||
- `GOOSE_PROVIDER`: LLM provider (openai, anthropic, google, etc.)
|
||||
- `GOOSE_MODEL`: Model to use (gpt-4o, claude-sonnet-4, etc.)
|
||||
|
|
@ -188,7 +188,7 @@ jobs:
|
|||
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
- name: Run Goose analysis
|
||||
- name: Run goose analysis
|
||||
run: |
|
||||
goose run -t "Review this codebase for security issues"
|
||||
```
|
||||
|
|
@ -222,7 +222,7 @@ analyze:
|
|||
|
||||
### Included Tools
|
||||
|
||||
The image includes essential tools for Goose operation:
|
||||
The image includes essential tools for goose operation:
|
||||
- `git` - Version control operations
|
||||
- `curl` - HTTP requests
|
||||
- `ca-certificates` - SSL/TLS support
|
||||
|
|
@ -317,6 +317,6 @@ When contributing Docker-related changes:
|
|||
|
||||
## Related Documentation
|
||||
|
||||
- [Goose in Docker Tutorial](documentation/docs/tutorials/goose-in-docker.md) - Step-by-step tutorial
|
||||
- [goose in Docker Tutorial](documentation/docs/tutorials/goose-in-docker.md) - Step-by-step tutorial
|
||||
- [Installation Guide](https://block.github.io/goose/docs/getting-started/installation) - All installation methods
|
||||
- [Configuration Guide](https://block.github.io/goose/docs/guides/config-file) - Detailed configuration options
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Building Goose Desktop on Linux
|
||||
# Building goose Desktop on Linux
|
||||
|
||||
This guide covers building the Goose Desktop application from source on various Linux distributions.
|
||||
This guide covers building the goose Desktop application from source on various Linux distributions.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ Works on all Linux distributions:
|
|||
npm run make -- --targets=@electron-forge/maker-zip
|
||||
```
|
||||
|
||||
Output: `out/make/zip/linux/x64/Goose-linux-x64-{version}.zip`
|
||||
Output: `out/make/zip/linux/x64/goose-linux-x64-{version}.zip`
|
||||
|
||||
#### Option B: DEB Package
|
||||
For Debian/Ubuntu systems:
|
||||
|
|
@ -95,7 +95,7 @@ npm run make
|
|||
|
||||
#### From Build Directory
|
||||
```bash
|
||||
./out/Goose-linux-x64/Goose
|
||||
./out/goose-linux-x64/goose
|
||||
```
|
||||
|
||||
#### Install DEB Package (if built)
|
||||
|
|
@ -122,8 +122,8 @@ These are harmless and don't affect functionality. To suppress them, create a la
|
|||
|
||||
```bash
|
||||
#!/bin/bash
|
||||
cd /path/to/goose/ui/desktop/out/Goose-linux-x64
|
||||
./Goose 2>&1 | grep -v "GLib-GObject" | grep -v "browser_main_loop"
|
||||
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
|
||||
|
|
@ -155,10 +155,10 @@ For active development:
|
|||
Create `~/.local/share/applications/goose.desktop`:
|
||||
```ini
|
||||
[Desktop Entry]
|
||||
Name=Goose AI Agent
|
||||
Name=goose AI Agent
|
||||
Comment=Local AI agent for development tasks
|
||||
Exec=/path/to/goose/ui/desktop/out/Goose-linux-x64/Goose %U
|
||||
Icon=/path/to/goose/ui/desktop/out/Goose-linux-x64/resources/app.asar.unpacked/src/images/icon.png
|
||||
Exec=/path/to/goose/ui/desktop/out/goose-linux-x64/goose %U
|
||||
Icon=/path/to/goose/ui/desktop/out/goose-linux-x64/resources/app.asar.unpacked/src/images/icon.png
|
||||
Terminal=false
|
||||
Type=Application
|
||||
Categories=Development;Utility;
|
||||
|
|
@ -169,8 +169,8 @@ MimeType=x-scheme-handler/goose
|
|||
### System-wide Installation
|
||||
To install system-wide:
|
||||
```bash
|
||||
sudo cp -r out/Goose-linux-x64 /opt/goose
|
||||
sudo ln -s /opt/goose/Goose /usr/local/bin/goose-gui
|
||||
sudo cp -r out/goose-linux-x64 /opt/goose
|
||||
sudo ln -s /opt/goose/goose /usr/local/bin/goose-gui
|
||||
```
|
||||
|
||||
## Contributing
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Contribution Guide
|
||||
|
||||
Goose is open source!
|
||||
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.
|
||||
|
||||
|
|
@ -85,7 +85,7 @@ Happy contributing!
|
|||
|
||||
## Prerequisites
|
||||
|
||||
Goose includes rust binaries alongside an electron app for the GUI. To work
|
||||
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][rustup]. To work
|
||||
on the App, you will also need to [install node and npm][nvm] - we recommend through nvm.
|
||||
|
||||
|
|
@ -296,10 +296,10 @@ reuse it. For things like automations or to test without doing official setup, y
|
|||
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](https://langfuse.com/docs/deployment/self-host)
|
||||
## Enable traces in goose with [locally hosted Langfuse](https://langfuse.com/docs/deployment/self-host)
|
||||
|
||||
- Start a local Langfuse using the docs [here](https://langfuse.com/self-hosting/docker-compose). Create an organization and project and create API credentials.
|
||||
- Set the environment variables so that Goose can connect to the langfuse server:
|
||||
- Set the environment variables so that goose can connect to the langfuse server:
|
||||
|
||||
```
|
||||
export LANGFUSE_INIT_PROJECT_PUBLIC_KEY=publickey-local
|
||||
|
|
@ -327,14 +327,14 @@ 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](https://discord.gg/block-opensource).
|
||||
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](https://discord.gg/block-opensource).
|
||||
|
||||
- **Stars on GitHub:** If you resonate with our project and find it valuable, consider starring our Goose on GitHub! 🌟
|
||||
- **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](https://discord.gg/block-opensource).
|
||||
- **Give Feedback:** Have a feature you want to see or encounter an issue with Goose, [click here to open an issue](https://github.com/block/goose/issues/new/choose), [start a discussion](https://github.com/block/goose/discussions) or tell us on Discord.
|
||||
- **Give Feedback:** Have a feature you want to see or encounter an issue with goose, [click here to open an issue](https://github.com/block/goose/issues/new/choose), [start a discussion](https://github.com/block/goose/discussions) 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](https://calget.com/c/t7jszrie) or follow us on [social media](https://linktr.ee/goose_oss) 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](https://discord.com/channels/1287729918100246654/1287729920797179958) 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](https://discord.com/channels/1287729918100246654/1287729920797179957) channel.
|
||||
- **Spread the Word:** Help us reach more people by sharing Goose's project, website, YouTube, and/or Twitter/X.
|
||||
- **Spread the Word:** Help us reach more people by sharing goose's project, website, YouTube, and/or Twitter/X.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# 🍳 Contributing Recipes to Goose Cookbook
|
||||
# 🍳 Contributing Recipes to goose Cookbook
|
||||
|
||||
Thank you for your interest in contributing to the Goose Recipe Cookbook! This guide will walk you through the process of submitting your own recipe.
|
||||
Thank you for your interest in contributing to the goose Recipe Cookbook! This guide will walk you through the process of submitting your own recipe.
|
||||
|
||||
## 💰 Get Rewarded
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
# syntax=docker/dockerfile:1.4
|
||||
# Goose CLI and Server Docker Image
|
||||
# goose CLI and Server Docker Image
|
||||
# Multi-stage build for minimal final image size
|
||||
|
||||
# Build stage
|
||||
|
|
@ -67,7 +67,7 @@ ENTRYPOINT ["/usr/local/bin/goose"]
|
|||
CMD ["--help"]
|
||||
|
||||
# Labels for metadata
|
||||
LABEL org.opencontainers.image.title="Goose"
|
||||
LABEL org.opencontainers.image.description="Goose CLI"
|
||||
LABEL org.opencontainers.image.title="goose"
|
||||
LABEL org.opencontainers.image.description="goose CLI"
|
||||
LABEL org.opencontainers.image.vendor="Block"
|
||||
LABEL org.opencontainers.image.source="https://github.com/block/goose"
|
||||
|
|
|
|||
4
JOKES.md
4
JOKES.md
|
|
@ -1,6 +1,6 @@
|
|||
# Goose Jokes 🦢
|
||||
# goose Jokes 🦢
|
||||
|
||||
## Why did the Goose become a developer?
|
||||
## Why did the goose become a developer?
|
||||
|
||||
Because it wanted to help debug all those "fowl" errors in the code!
|
||||
|
||||
|
|
|
|||
6
Justfile
6
Justfile
|
|
@ -63,7 +63,7 @@ copy-binary BUILD_MODE="release":
|
|||
echo "Copying goose CLI binary from target/{{BUILD_MODE}}..."; \
|
||||
cp -p ./target/{{BUILD_MODE}}/goose ./ui/desktop/src/bin/; \
|
||||
else \
|
||||
echo "Goose CLI binary not found in target/{{BUILD_MODE}}"; \
|
||||
echo "goose CLI binary not found in target/{{BUILD_MODE}}"; \
|
||||
exit 1; \
|
||||
fi
|
||||
@if [ -f ./temporal-service/temporal-service ]; then \
|
||||
|
|
@ -148,7 +148,7 @@ run-ui-only:
|
|||
cd ui/desktop && npm install && npm run start-gui
|
||||
|
||||
debug-ui:
|
||||
@echo "🚀 Starting Goose frontend in external backend mode"
|
||||
@echo "🚀 Starting goose frontend in external backend mode"
|
||||
cd ui/desktop && \
|
||||
export GOOSE_EXTERNAL_BACKEND=true && \
|
||||
export GOOSE_EXTERNAL_PORT=3000 && \
|
||||
|
|
@ -163,7 +163,7 @@ debug-ui:
|
|||
# 4. If not auto-detected, click "Configure" and add: localhost:9229
|
||||
|
||||
debug-ui-main-process:
|
||||
@echo "🔍 Starting Goose UI with main process debugging enabled"
|
||||
@echo "🔍 Starting goose UI with main process debugging enabled"
|
||||
@just release-binary
|
||||
cd ui/desktop && \
|
||||
npm install && \
|
||||
|
|
|
|||
|
|
@ -46,13 +46,13 @@ Designed for maximum flexibility, goose works with any LLM and supports multi-mo
|
|||
- [Documentation](https://block.github.io/goose/docs/category/getting-started)
|
||||
|
||||
|
||||
# A Little Goose Humor 🦢
|
||||
# a little goose humor 🦢
|
||||
|
||||
> Why did the developer choose goose as their AI agent?
|
||||
>
|
||||
> Because it always helps them "migrate" their code to production! 🚀
|
||||
|
||||
# Goose Around with Us
|
||||
# goose around with us
|
||||
- [Discord](https://discord.gg/block-opensource)
|
||||
- [YouTube](https://www.youtube.com/@goose-oss)
|
||||
- [LinkedIn](https://www.linkedin.com/company/goose-oss)
|
||||
|
|
|
|||
12
SECURITY.md
12
SECURITY.md
|
|
@ -1,14 +1,14 @@
|
|||
> [!CAUTION]
|
||||
> Goose is a developer agent with access to a variety of systems that perform actions on behalf of the user on their local machine. Please be aware that since developer agents have the ability to run code and take actions on your computer, they pose a unique risk compared to chat based LLM interactions. While most foundational models include baseline protections against prompt injection, there is still inherent risk when using Goose to interact with the internet or through other untrusted data sources. To minimize these risks, consider taking the following precautions:
|
||||
> goose is a developer agent with access to a variety of systems that perform actions on behalf of the user on their local machine. Please be aware that since developer agents have the ability to run code and take actions on your computer, they pose a unique risk compared to chat based LLM interactions. While most foundational models include baseline protections against prompt injection, there is still inherent risk when using goose to interact with the internet or through other untrusted data sources. To minimize these risks, consider taking the following precautions:
|
||||
>
|
||||
> - Use a dedicated virtual machine or container (Docker/Kubernetes) with limited privileged capabilities. This will minimize the risk of local system attacks or unintended access to critical system resources.
|
||||
> - Always review the code and tests generated by Goose for accuracy.
|
||||
> - Avoid providing Goose with sensitive or confidential information to prevent information leakage.
|
||||
> - Always review the code and tests generated by goose for accuracy.
|
||||
> - Avoid providing goose with sensitive or confidential information to prevent information leakage.
|
||||
> - For any systems and actions that may result in significant changes, always require human confirmation.
|
||||
> - If possible, break down complex Goose instructions into smaller, isolated operations. This reduces the risk of an errant command affecting multiple parts of the system at once and makes it easier to detect abnormal behaviour.
|
||||
> - Only connect Goose with MCP extensions that you have reviewed
|
||||
> - If possible, break down complex goose instructions into smaller, isolated operations. This reduces the risk of an errant command affecting multiple parts of the system at once and makes it easier to detect abnormal behaviour.
|
||||
> - Only connect goose with MCP extensions that you have reviewed
|
||||
>
|
||||
> In some circumstances, Goose may follow commands found embedded in content even if those commands conflict with the task given to Goose. We suggest taking the precautions above to limit risks from prompt injection. By taking these steps, you can reduce the potential security risks associated with developer agents and better protect your systems and users.
|
||||
> In some circumstances, goose may follow commands found embedded in content even if those commands conflict with the task given to goose. We suggest taking the precautions above to limit risks from prompt injection. By taking these steps, you can reduce the potential security risks associated with developer agents and better protect your systems and users.
|
||||
>
|
||||
> Block recognizes the important contributions our open source community makes. Part of keeping Block and its customers safe is by making sure that we find and fix any security issues found in our open source projects. If you find a security vulnerability, we encourage you to privately report it in the repository’s Security tab -> Report a vulnerability.
|
||||
>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Goose Benchmarking Framework
|
||||
# goose Benchmarking Framework
|
||||
|
||||
The `goose-bench` crate provides a framework for benchmarking and evaluating LLM models with the Goose framework. This tool helps quantify model performance across various tasks and generate structured reports.
|
||||
The `goose-bench` crate provides a framework for benchmarking and evaluating LLM models with the goose framework. This tool helps quantify model performance across various tasks and generate structured reports.
|
||||
|
||||
## Features
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Goose Web Interface
|
||||
# goose Web Interface
|
||||
|
||||
The `goose web` command provides a (preview) web-based chat interface for interacting with Goose.
|
||||
The `goose web` command provides a (preview) web-based chat interface for interacting with goose.
|
||||
Do not expose this publicly - this is in a preview state as an option.
|
||||
|
||||
## Usage
|
||||
|
|
@ -21,7 +21,7 @@ goose web --host 0.0.0.0 --port 8080
|
|||
|
||||
## Features
|
||||
|
||||
- **Real-time chat interface**: Communicate with Goose through a clean web UI
|
||||
- **Real-time chat interface**: Communicate with goose through a clean web UI
|
||||
- **WebSocket support**: Real-time message streaming
|
||||
- **Session management**: Each browser tab maintains its own session
|
||||
- **Responsive design**: Works on desktop and mobile devices
|
||||
|
|
@ -53,9 +53,9 @@ The web interface provides:
|
|||
- [ ] Code syntax highlighting
|
||||
- [ ] Export chat history
|
||||
|
||||
### Integration with Goose Agent
|
||||
### Integration with goose Agent
|
||||
|
||||
The web server creates an instance of the Goose Agent and processes messages through the same pipeline as the CLI. However, some features like:
|
||||
The web server creates an instance of the goose Agent and processes messages through the same pipeline as the CLI. However, some features like:
|
||||
- Extension management
|
||||
- Tool confirmations
|
||||
- File system interactions
|
||||
|
|
|
|||
|
|
@ -302,12 +302,12 @@ enum RecipeCommand {
|
|||
|
||||
#[derive(Subcommand)]
|
||||
enum Command {
|
||||
/// Configure Goose settings
|
||||
#[command(about = "Configure Goose settings")]
|
||||
/// Configure goose settings
|
||||
#[command(about = "Configure goose settings")]
|
||||
Configure {},
|
||||
|
||||
/// Display Goose configuration information
|
||||
#[command(about = "Display Goose information")]
|
||||
/// Display goose configuration information
|
||||
#[command(about = "Display goose information")]
|
||||
Info {
|
||||
/// Show verbose information including current configuration
|
||||
#[arg(short, long, help = "Show verbose information including config.yaml")]
|
||||
|
|
@ -318,8 +318,8 @@ enum Command {
|
|||
#[command(about = "Run one of the mcp servers bundled with goose")]
|
||||
Mcp { name: String },
|
||||
|
||||
/// Run Goose as an ACP (Agent Client Protocol) agent
|
||||
#[command(about = "Run Goose as an ACP agent server on stdio")]
|
||||
/// Run goose as an ACP (Agent Client Protocol) agent
|
||||
#[command(about = "Run goose as an ACP agent server on stdio")]
|
||||
Acp {},
|
||||
|
||||
/// Start or resume interactive chat sessions
|
||||
|
|
@ -445,8 +445,8 @@ enum Command {
|
|||
short = 't',
|
||||
long = "text",
|
||||
value_name = "TEXT",
|
||||
help = "Input text to provide to Goose directly",
|
||||
long_help = "Input text containing commands for Goose. Use this in lieu of the instructions argument.",
|
||||
help = "Input text to provide to goose directly",
|
||||
long_help = "Input text containing commands for goose. Use this in lieu of the instructions argument.",
|
||||
conflicts_with = "instructions",
|
||||
conflicts_with = "recipe"
|
||||
)]
|
||||
|
|
@ -656,7 +656,7 @@ enum Command {
|
|||
command: SchedulerCommand,
|
||||
},
|
||||
|
||||
/// Update the Goose CLI version
|
||||
/// Update the goose CLI version
|
||||
#[command(about = "Update the goose CLI version")]
|
||||
Update {
|
||||
/// Update to canary version
|
||||
|
|
@ -668,7 +668,7 @@ enum Command {
|
|||
)]
|
||||
canary: bool,
|
||||
|
||||
/// Enforce to re-configure Goose during update
|
||||
/// Enforce to re-configure goose during update
|
||||
#[arg(short, long, help = "Enforce to re-configure goose during update")]
|
||||
reconfigure: bool,
|
||||
},
|
||||
|
|
|
|||
|
|
@ -19,14 +19,14 @@ use tokio_util::sync::CancellationToken;
|
|||
use tracing::{error, info, warn};
|
||||
use url::Url;
|
||||
|
||||
/// Represents a single Goose session for ACP
|
||||
/// Represents a single goose session for ACP
|
||||
struct GooseSession {
|
||||
messages: Conversation,
|
||||
tool_call_ids: HashMap<String, String>, // Maps internal tool IDs to ACP tool call IDs
|
||||
cancel_token: Option<CancellationToken>, // Active cancellation token for prompt processing
|
||||
}
|
||||
|
||||
/// Goose ACP Agent implementation that connects to real Goose agents
|
||||
/// goose ACP Agent implementation that connects to real goose agents
|
||||
struct GooseAcpAgent {
|
||||
session_update_tx: mpsc::UnboundedSender<(acp::SessionNotification, oneshot::Sender<()>)>,
|
||||
sessions: Arc<Mutex<HashMap<String, GooseSession>>>,
|
||||
|
|
|
|||
|
|
@ -257,8 +257,8 @@ pub async fn handle_configure() -> Result<(), Box<dyn Error>> {
|
|||
.item("remove", "Remove Extension", "Remove an extension")
|
||||
.item(
|
||||
"settings",
|
||||
"Goose Settings",
|
||||
"Set the Goose Mode, Tool Output, Tool Permissions, Experiment, Goose recipe github repo and more",
|
||||
"goose settings",
|
||||
"Set the goose mode, Tool Output, Tool Permissions, Experiment, goose recipe github repo and more",
|
||||
)
|
||||
.interact()?;
|
||||
|
||||
|
|
@ -645,7 +645,7 @@ pub async fn configure_provider_dialog() -> Result<bool, Box<dyn Error>> {
|
|||
|
||||
let result = provider
|
||||
.complete(
|
||||
"You are an AI agent called Goose. You use tools of connected extensions to solve problems.",
|
||||
"You are an AI agent called goose. You use tools of connected extensions to solve problems.",
|
||||
&messages,
|
||||
&tools.into_iter().collect::<Vec<_>>()
|
||||
).await;
|
||||
|
|
@ -725,7 +725,7 @@ pub fn configure_extensions_dialog() -> Result<(), Box<dyn Error>> {
|
|||
.item(
|
||||
"built-in",
|
||||
"Built-in Extension",
|
||||
"Use an extension that comes with Goose",
|
||||
"Use an extension that comes with goose",
|
||||
)
|
||||
.item(
|
||||
"stdio",
|
||||
|
|
@ -1203,7 +1203,7 @@ pub fn remove_extension_dialog() -> Result<(), Box<dyn Error>> {
|
|||
|
||||
pub async fn configure_settings_dialog() -> Result<(), Box<dyn Error>> {
|
||||
let setting_type = cliclack::select("What setting would you like to configure?")
|
||||
.item("goose_mode", "Goose Mode", "Configure Goose mode")
|
||||
.item("goose_mode", "goose mode", "Configure goose mode")
|
||||
.item(
|
||||
"goose_router_strategy",
|
||||
"Router Tool Selection Strategy",
|
||||
|
|
@ -1231,8 +1231,8 @@ pub async fn configure_settings_dialog() -> Result<(), Box<dyn Error>> {
|
|||
)
|
||||
.item(
|
||||
"recipe",
|
||||
"Goose recipe github repo",
|
||||
"Goose will pull recipes from this repo if not found locally.",
|
||||
"goose recipe github repo",
|
||||
"goose will pull recipes from this repo if not found locally.",
|
||||
)
|
||||
.item(
|
||||
"scheduler",
|
||||
|
|
@ -1280,7 +1280,7 @@ pub fn configure_goose_mode_dialog() -> Result<(), Box<dyn Error>> {
|
|||
let _ = cliclack::log::info("Notice: GOOSE_MODE environment variable is set and will override the configuration here.");
|
||||
}
|
||||
|
||||
let mode = cliclack::select("Which Goose mode would you like to configure?")
|
||||
let mode = cliclack::select("Which goose mode would you like to configure?")
|
||||
.item(
|
||||
"auto",
|
||||
"Auto Mode",
|
||||
|
|
@ -1591,7 +1591,7 @@ fn configure_recipe_dialog() -> Result<(), Box<dyn Error>> {
|
|||
.ok()
|
||||
.or_else(|| config.get_param(key_name).unwrap_or(None));
|
||||
let mut recipe_repo_input = cliclack::input(
|
||||
"Enter your Goose Recipe Github repo (owner/repo): eg: my_org/goose-recipes",
|
||||
"Enter your goose recipe Github repo (owner/repo): eg: my_org/goose-recipes",
|
||||
)
|
||||
.required(false);
|
||||
if let Some(recipe_repo) = default_recipe_repo {
|
||||
|
|
@ -1626,7 +1626,7 @@ fn configure_scheduler_dialog() -> Result<(), Box<dyn Error>> {
|
|||
|
||||
let scheduler_type = cliclack::select("Which scheduler type would you like to use?")
|
||||
.items(&[
|
||||
("legacy", "Built-in Cron (Default)", "Uses Goose's built-in cron scheduler. Simple and reliable for basic scheduling needs."),
|
||||
("legacy", "Built-in Cron (Default)", "Uses goose's built-in cron scheduler. Simple and reliable for basic scheduling needs."),
|
||||
("temporal", "Temporal", "Uses Temporal workflow engine for advanced scheduling features. Requires Temporal CLI to be installed.")
|
||||
])
|
||||
.interact()?;
|
||||
|
|
@ -1651,7 +1651,7 @@ fn configure_scheduler_dialog() -> Result<(), Box<dyn Error>> {
|
|||
println!(" • Temporal scheduler requires Temporal CLI to be installed");
|
||||
println!(" • macOS: brew install temporal");
|
||||
println!(" • Linux/Windows: https://github.com/temporalio/cli/releases");
|
||||
println!(" • If Temporal is unavailable, Goose will automatically fall back to the built-in scheduler");
|
||||
println!(" • If Temporal is unavailable, goose will automatically fall back to the built-in scheduler");
|
||||
println!(" • The scheduling engines do not share the list of schedules");
|
||||
}
|
||||
_ => unreachable!(),
|
||||
|
|
@ -1685,7 +1685,7 @@ pub fn configure_max_turns_dialog() -> Result<(), Box<dyn Error>> {
|
|||
config.set_param("GOOSE_MAX_TURNS", Value::from(max_turns))?;
|
||||
|
||||
cliclack::outro(format!(
|
||||
"Set maximum turns to {} - Goose will ask for input after {} consecutive actions",
|
||||
"Set maximum turns to {} - goose will ask for input after {} consecutive actions",
|
||||
max_turns, max_turns
|
||||
))?;
|
||||
|
||||
|
|
@ -1736,7 +1736,7 @@ pub async fn handle_openrouter_auth() -> Result<(), Box<dyn Error>> {
|
|||
// Simple test request
|
||||
let test_result = provider
|
||||
.complete(
|
||||
"You are Goose, an AI assistant.",
|
||||
"You are goose, an AI assistant.",
|
||||
&[Message::user().with_text("Say 'Configuration test successful!'")],
|
||||
&[],
|
||||
)
|
||||
|
|
@ -1773,7 +1773,7 @@ pub async fn handle_openrouter_auth() -> Result<(), Box<dyn Error>> {
|
|||
}
|
||||
}
|
||||
|
||||
cliclack::outro("OpenRouter setup complete! You can now use Goose.")?;
|
||||
cliclack::outro("OpenRouter setup complete! You can now use goose.")?;
|
||||
}
|
||||
Err(e) => {
|
||||
eprintln!("⚠️ Configuration test failed: {}", e);
|
||||
|
|
@ -1839,7 +1839,7 @@ pub async fn handle_tetrate_auth() -> Result<(), Box<dyn Error>> {
|
|||
// Simple test request
|
||||
let test_result = provider
|
||||
.complete(
|
||||
"You are Goose, an AI assistant.",
|
||||
"You are goose, an AI assistant.",
|
||||
&[Message::user().with_text("Say 'Configuration test successful!'")],
|
||||
&[],
|
||||
)
|
||||
|
|
@ -1876,7 +1876,7 @@ pub async fn handle_tetrate_auth() -> Result<(), Box<dyn Error>> {
|
|||
}
|
||||
}
|
||||
|
||||
cliclack::outro("Tetrate Agent Router Service setup complete! You can now use Goose.")?;
|
||||
cliclack::outro("Tetrate Agent Router Service setup complete! You can now use goose.")?;
|
||||
}
|
||||
Err(e) => {
|
||||
eprintln!("⚠️ Configuration test failed: {}", e);
|
||||
|
|
|
|||
|
|
@ -30,19 +30,19 @@ pub fn handle_info(verbose: bool) -> Result<()> {
|
|||
let basic_padding = paths.iter().map(|(l, _)| l.len()).max().unwrap_or(0) + 4;
|
||||
|
||||
// Print version information
|
||||
println!("{}", style("Goose Version:").cyan().bold());
|
||||
println!("{}", style("goose Version:").cyan().bold());
|
||||
print_aligned("Version:", env!("CARGO_PKG_VERSION"), basic_padding);
|
||||
println!();
|
||||
|
||||
// Print location information
|
||||
println!("{}", style("Goose Locations:").cyan().bold());
|
||||
println!("{}", style("goose Locations:").cyan().bold());
|
||||
for (label, path) in &paths {
|
||||
print_aligned(label, path, basic_padding);
|
||||
}
|
||||
|
||||
// Print verbose info if requested
|
||||
if verbose {
|
||||
println!("\n{}", style("Goose Configuration:").cyan().bold());
|
||||
println!("\n{}", style("goose Configuration:").cyan().bold());
|
||||
match config.load_values() {
|
||||
Ok(values) => {
|
||||
if values.is_empty() {
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ pub fn handle_project_default() -> Result<()> {
|
|||
let status = command.status()?;
|
||||
|
||||
if !status.success() {
|
||||
println!("Failed to run Goose. Exit code: {:?}", status.code());
|
||||
println!("Failed to run goose. Exit code: {:?}", status.code());
|
||||
}
|
||||
return Ok(());
|
||||
}
|
||||
|
|
@ -65,7 +65,7 @@ pub fn handle_project_default() -> Result<()> {
|
|||
};
|
||||
|
||||
// Ask the user what they want to do
|
||||
let _ = intro("Goose Project Manager");
|
||||
let _ = intro("goose Project Manager");
|
||||
|
||||
let current_dir = std::env::current_dir()?;
|
||||
let current_dir_display = current_dir.display();
|
||||
|
|
@ -101,7 +101,7 @@ pub fn handle_project_default() -> Result<()> {
|
|||
// Change to the project directory
|
||||
std::env::set_current_dir(project_dir)?;
|
||||
|
||||
// Build the command to run Goose
|
||||
// Build the command to run goose
|
||||
let mut command = std::process::Command::new("goose");
|
||||
command.arg("session");
|
||||
|
||||
|
|
@ -114,7 +114,7 @@ pub fn handle_project_default() -> Result<()> {
|
|||
let status = command.status()?;
|
||||
|
||||
if !status.success() {
|
||||
println!("Failed to run Goose. Exit code: {:?}", status.code());
|
||||
println!("Failed to run goose. Exit code: {:?}", status.code());
|
||||
}
|
||||
}
|
||||
"fresh" => {
|
||||
|
|
@ -126,7 +126,7 @@ pub fn handle_project_default() -> Result<()> {
|
|||
// Change to the project directory
|
||||
std::env::set_current_dir(project_dir)?;
|
||||
|
||||
// Build the command to run Goose with a fresh session
|
||||
// Build the command to run goose with a fresh session
|
||||
let mut command = std::process::Command::new("goose");
|
||||
command.arg("session");
|
||||
|
||||
|
|
@ -134,13 +134,13 @@ pub fn handle_project_default() -> Result<()> {
|
|||
let status = command.status()?;
|
||||
|
||||
if !status.success() {
|
||||
println!("Failed to run Goose. Exit code: {:?}", status.code());
|
||||
println!("Failed to run goose. Exit code: {:?}", status.code());
|
||||
}
|
||||
}
|
||||
"new" => {
|
||||
let _ = outro("Starting a new session in the current directory");
|
||||
|
||||
// Build the command to run Goose
|
||||
// Build the command to run goose
|
||||
let mut command = std::process::Command::new("goose");
|
||||
command.arg("session");
|
||||
|
||||
|
|
@ -148,7 +148,7 @@ pub fn handle_project_default() -> Result<()> {
|
|||
let status = command.status()?;
|
||||
|
||||
if !status.success() {
|
||||
println!("Failed to run Goose. Exit code: {:?}", status.code());
|
||||
println!("Failed to run goose. Exit code: {:?}", status.code());
|
||||
}
|
||||
}
|
||||
_ => {
|
||||
|
|
@ -213,7 +213,7 @@ pub fn handle_projects_interactive() -> Result<()> {
|
|||
.collect();
|
||||
|
||||
// Let the user select a project
|
||||
let _ = intro("Goose Project Manager");
|
||||
let _ = intro("goose Project Manager");
|
||||
let mut select = cliclack::select("Select a project:");
|
||||
|
||||
// Add each project as an option
|
||||
|
|
@ -280,7 +280,7 @@ pub fn handle_projects_interactive() -> Result<()> {
|
|||
false
|
||||
};
|
||||
|
||||
// Build the command to run Goose
|
||||
// Build the command to run goose
|
||||
let mut command = std::process::Command::new("goose");
|
||||
command.arg("session");
|
||||
|
||||
|
|
@ -297,7 +297,7 @@ pub fn handle_projects_interactive() -> Result<()> {
|
|||
let status = command.status()?;
|
||||
|
||||
if !status.success() {
|
||||
println!("Failed to run Goose. Exit code: {:?}", status.code());
|
||||
println!("Failed to run goose. Exit code: {:?}", status.code());
|
||||
}
|
||||
|
||||
Ok(())
|
||||
|
|
|
|||
|
|
@ -332,7 +332,7 @@ pub async fn handle_schedule_services_stop() -> Result<()> {
|
|||
}
|
||||
|
||||
pub async fn handle_schedule_cron_help() -> Result<()> {
|
||||
println!("📅 Cron Expression Guide for Goose Scheduler");
|
||||
println!("📅 Cron Expression Guide for goose Scheduler");
|
||||
println!("===========================================\\n");
|
||||
|
||||
println!("🕐 HOURLY SCHEDULES (Most Common Request):");
|
||||
|
|
|
|||
|
|
@ -146,7 +146,7 @@ pub async fn handle_web(port: u16, host: String, open: bool) -> Result<()> {
|
|||
|
||||
let addr: SocketAddr = format!("{}:{}", host, port).parse()?;
|
||||
|
||||
println!("\n🪿 Starting Goose web server");
|
||||
println!("\n🪿 Starting goose web server");
|
||||
println!(" Provider: {} | Model: {}", provider_name, model);
|
||||
println!(
|
||||
" Working directory: {}",
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"c848f22f273e158c32435d3e72cc999c046dc1a9afdc3efda68ff451f833a185": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -87,7 +87,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -253,7 +253,7 @@
|
|||
},
|
||||
"78cc474ff2d51b9a24df8c35e5c75f256dafb67ff5489af30fcec95cd87790b8": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -381,7 +381,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"1bc400a528c54b25f4f1f609481e98e44222b3deaf7eee2c9e640e6345c73861": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -82,7 +82,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -250,7 +250,7 @@
|
|||
},
|
||||
"d51c15f1ede58b5496bba746a4bdffd8ce84526749ce0021969d6ed6f2538a6d": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -375,7 +375,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"1b998117eba523901ae6a4dbf8caa81a95ea88ef7a84d0434c9b41a26164a2b9": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:04:16.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -82,7 +82,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -221,7 +221,7 @@
|
|||
"content": [
|
||||
{
|
||||
"type": "text",
|
||||
"text": "I am Goose, an AI agent created by Block (the parent company of Square, CashApp, and Tidal). I'm being developed as an open-source software project.\n\nI can help you with various tasks using different tools and extensions. While I have a defined identity as Goose, I aim to be helpful, direct, and efficient in assisting you with your needs. Is there something specific I can help you with today?"
|
||||
"text": "I am goose, an AI agent created by Block (the parent company of Square, CashApp, and Tidal). I'm being developed as an open-source software project.\n\nI can help you with various tasks using different tools and extensions. While I have a defined identity as goose, I aim to be helpful, direct, and efficient in assisting you with your needs. Is there something specific I can help you with today?"
|
||||
}
|
||||
]
|
||||
},
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"21e33b98670d23e1bad3f21da667502d0930b42e34431395e266a4c524620cf1": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:28.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:28.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -122,7 +122,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -277,7 +277,7 @@
|
|||
},
|
||||
"1bc400a528c54b25f4f1f609481e98e44222b3deaf7eee2c9e640e6345c73861": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:28.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:28.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -358,7 +358,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"1b998117eba523901ae6a4dbf8caa81a95ea88ef7a84d0434c9b41a26164a2b9": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:25.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:25.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -82,7 +82,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -221,7 +221,7 @@
|
|||
"content": [
|
||||
{
|
||||
"type": "text",
|
||||
"text": "My name is Goose, an AI agent created by Block, the parent company of Square, CashApp, and Tidal. How can I assist you today?"
|
||||
"text": "My name is goose, an AI agent created by Block, the parent company of Square, CashApp, and Tidal. How can I assist you today?"
|
||||
}
|
||||
]
|
||||
},
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"1b998117eba523901ae6a4dbf8caa81a95ea88ef7a84d0434c9b41a26164a2b9": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:27.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:27.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -82,7 +82,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -221,7 +221,7 @@
|
|||
"content": [
|
||||
{
|
||||
"type": "text",
|
||||
"text": "My name is Goose. I am a general-purpose AI agent created by Block, the parent company of Square, CashApp, and Tidal. I am being developed as an open-source software project."
|
||||
"text": "My name is goose. I am a general-purpose AI agent created by Block, the parent company of Square, CashApp, and Tidal. I am being developed as an open-source software project."
|
||||
}
|
||||
]
|
||||
},
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"09dddf56be462d1861d5a56de6ec2d79b76e1b6f8f8ba9da8d837aae55c7e70b": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:31.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:31.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -122,7 +122,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -277,7 +277,7 @@
|
|||
},
|
||||
"1bc400a528c54b25f4f1f609481e98e44222b3deaf7eee2c9e640e6345c73861": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:31.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:31.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -358,7 +358,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"1b998117eba523901ae6a4dbf8caa81a95ea88ef7a84d0434c9b41a26164a2b9": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:29.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:29.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -82,7 +82,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -221,7 +221,7 @@
|
|||
"content": [
|
||||
{
|
||||
"type": "text",
|
||||
"text": "My name is Goose, and I am a general-purpose AI agent developed by Block, the parent company of Square, CashApp, and Tidal."
|
||||
"text": "My name is goose, and I am a general-purpose AI agent developed by Block, the parent company of Square, CashApp, and Tidal."
|
||||
}
|
||||
]
|
||||
},
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"c848f22f273e158c32435d3e72cc999c046dc1a9afdc3efda68ff451f833a185": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:24.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:24.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -87,7 +87,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"e546a32d4a2c9d41338b6725f317c4d4f462ce7cc04c79f3f24dd47a1a32a795": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:24.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:24.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -122,7 +122,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -277,7 +277,7 @@
|
|||
},
|
||||
"1bc400a528c54b25f4f1f609481e98e44222b3deaf7eee2c9e640e6345c73861": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:24.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:24.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -358,7 +358,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"1b998117eba523901ae6a4dbf8caa81a95ea88ef7a84d0434c9b41a26164a2b9": {
|
||||
"input": {
|
||||
"system": "You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:24.\n\nGoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"system": "You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.\n\nThe current date is 2025-07-28 12:05:24.\n\ngoose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).\nThese models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.\n\n# Extensions\n\nExtensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.\nYou are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.\nUse the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.\n\n\nBecause you dynamically load extensions, your conversation history may refer\nto interactions with extensions that are not currently active. The currently\nactive extensions are below. Each of these extensions provides tools that are\nin your tool specification.\n\n\n## weather_extension\n\n\n\n\n\n\n\n# Suggestion\n\"\"\n\n\n\n\n# Response Guidelines\n\n- Use Markdown formatting for all responses.\n- Follow best practices for Markdown, including:\n - Using headers for organization.\n - Bullet points for lists.\n - Links formatted correctly, either as linked text (e.g., [this is linked text](https://example.com)) or automatic links using angle brackets (e.g., <http://example.com/>).\n- For code examples, use fenced code blocks by placing triple backticks (` ``` `) before and after the code. Include the language identifier after the opening backticks (e.g., ` ```python `) to enable syntax highlighting.\n- Ensure clarity, conciseness, and proper formatting to enhance readability and usability.\n\n# Additional Instructions:\n\nRight now you are *NOT* in the chat only mode and have access to tool use and system.",
|
||||
"messages": [
|
||||
{
|
||||
"id": null,
|
||||
|
|
@ -82,7 +82,7 @@
|
|||
},
|
||||
{
|
||||
"name": "platform__manage_schedule",
|
||||
"description": "Manage scheduled recipe execution for this Goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"description": "Manage scheduled recipe execution for this goose instance.\n\nActions:\n- \"list\": List all scheduled jobs\n- \"create\": Create a new scheduled job from a recipe file\n- \"run_now\": Execute a scheduled job immediately \n- \"pause\": Pause a scheduled job\n- \"unpause\": Resume a paused job\n- \"delete\": Remove a scheduled job\n- \"kill\": Terminate a currently running job\n- \"inspect\": Get details about a running job\n- \"sessions\": List execution history for a job\n- \"session_content\": Get the full content (messages) of a specific session\n",
|
||||
"inputSchema": {
|
||||
"properties": {
|
||||
"action": {
|
||||
|
|
@ -221,7 +221,7 @@
|
|||
"content": [
|
||||
{
|
||||
"type": "text",
|
||||
"text": "My name is Goose. I'm an AI agent developed by Block, the parent company of Square, Cash App, and Tidal. How can I assist you today?"
|
||||
"text": "My name is goose. I'm an AI agent developed by Block, the parent company of Square, Cash App, and Tidal. How can I assist you today?"
|
||||
}
|
||||
]
|
||||
},
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ use std::sync::Arc;
|
|||
|
||||
use super::CompletionCache;
|
||||
|
||||
/// Completer for Goose CLI commands
|
||||
/// Completer for goose CLI commands
|
||||
pub struct GooseCompleter {
|
||||
completion_cache: Arc<std::sync::RwLock<CompletionCache>>,
|
||||
filename_completer: FilenameCompleter,
|
||||
|
|
|
|||
|
|
@ -742,7 +742,7 @@ pub fn display_session_info(
|
|||
}
|
||||
|
||||
pub fn display_greeting() {
|
||||
println!("\nGoose is running! Enter your instructions, or try asking what goose can do.\n");
|
||||
println!("\ngoose is running! Enter your instructions, or try asking what goose can do.\n");
|
||||
}
|
||||
|
||||
/// Display context window usage with both current and session totals
|
||||
|
|
|
|||
|
|
@ -3,20 +3,20 @@
|
|||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Goose Chat</title>
|
||||
<title>goose chat</title>
|
||||
<link rel="stylesheet" href="/static/style.css">
|
||||
</head>
|
||||
<body>
|
||||
<div class="container">
|
||||
<header>
|
||||
<h1 id="session-title">Goose Chat</h1>
|
||||
<h1 id="session-title">goose chat</h1>
|
||||
<div class="status" id="connection-status">Connecting...</div>
|
||||
</header>
|
||||
|
||||
<div class="chat-container">
|
||||
<div class="messages" id="messages">
|
||||
<div class="welcome-message">
|
||||
<h2>Welcome to Goose!</h2>
|
||||
<h2>Welcome to goose!</h2>
|
||||
<p>I'm your AI assistant. How can I help you today?</p>
|
||||
|
||||
<div class="suggestion-pills">
|
||||
|
|
|
|||
|
|
@ -121,7 +121,7 @@ function addThinkingIndicator() {
|
|||
<span></span>
|
||||
<span></span>
|
||||
</div>
|
||||
<span class="thinking-text">Goose is thinking...</span>
|
||||
<span class="thinking-text">goose is thinking...</span>
|
||||
`;
|
||||
messagesContainer.appendChild(thinkingDiv);
|
||||
messagesContainer.scrollTop = messagesContainer.scrollHeight;
|
||||
|
|
@ -477,7 +477,7 @@ async function loadSessionIfExists() {
|
|||
|
||||
// Update page title with session description if available
|
||||
if (sessionData.metadata && sessionData.metadata.description) {
|
||||
document.title = `Goose Chat - ${sessionData.metadata.description}`;
|
||||
document.title = `goose chat - ${sessionData.metadata.description}`;
|
||||
}
|
||||
|
||||
messagesContainer.scrollTop = messagesContainer.scrollHeight;
|
||||
|
|
@ -515,8 +515,8 @@ messageInput.focus();
|
|||
// Update session title
|
||||
function updateSessionTitle() {
|
||||
const titleElement = document.getElementById('session-title');
|
||||
// Just show "Goose Chat" - no need to show session ID
|
||||
titleElement.textContent = 'Goose Chat';
|
||||
// Just show "goose chat" - no need to show session ID
|
||||
titleElement.textContent = 'goose chat';
|
||||
}
|
||||
|
||||
// Update title on load
|
||||
|
|
|
|||
|
|
@ -417,7 +417,7 @@ impl ComputerControllerServer {
|
|||
tool_router: Self::tool_router(),
|
||||
cache_dir,
|
||||
active_resources: Arc::new(Mutex::new(HashMap::new())),
|
||||
http_client: Client::builder().user_agent("Goose/1.0").build().unwrap(),
|
||||
http_client: Client::builder().user_agent("goose/1.0").build().unwrap(),
|
||||
instructions,
|
||||
system_automation,
|
||||
}
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ impl TutorialServer {
|
|||
let available_tutorials = Self::get_available_tutorials();
|
||||
|
||||
let instructions = formatdoc! {r#"
|
||||
Because the tutorial extension is enabled, be aware that the user may be new to using Goose
|
||||
Because the tutorial extension is enabled, be aware that the user may be new to using goose
|
||||
or looking for help with specific features. Proactively offer relevant tutorials when appropriate.
|
||||
|
||||
Available tutorials:
|
||||
|
|
|
|||
|
|
@ -220,7 +220,7 @@ Help users test their MCP extension using these steps:
|
|||
|
||||
### 1. Initial Testing
|
||||
|
||||
Instruct users to start a Goose session with their extension.
|
||||
Instruct users to start a goose session with their extension.
|
||||
|
||||
**Important**: You cannot start the goose session for them, as it is interactive. You will have to let them
|
||||
know to start it in a terminal. Make sure you include instructions on how to setup the environment
|
||||
|
|
@ -257,8 +257,8 @@ goose run --with-extension "java -jar build/libs/extension.jar" --text "EXAMPLE
|
|||
|
||||
Once the session starts successfully, guide users to test their implementation:
|
||||
|
||||
- For tools, they should ask Goose to use the tool directly
|
||||
- For resources, they should ask Goose to access the relevant data
|
||||
- For tools, they should ask goose to use the tool directly
|
||||
- For resources, they should ask goose to access the relevant data
|
||||
|
||||
Example prompts they can use:
|
||||
|
||||
|
|
@ -359,7 +359,7 @@ server.addTool(
|
|||
|
||||
When users encounter issues:
|
||||
|
||||
1. First, check if there are any immediate error messages in the Goose session
|
||||
1. First, check if there are any immediate error messages in the goose session
|
||||
|
||||
2. If the error isn't clear, guide them to:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
IMPORTANT: currently GOOSE_ALLOWLIST is used in main.ts in ui/desktop, and not in goose-server. The following is for reference in case it is used on the server side for launch time enforcement.
|
||||
|
||||
# Goose Extension Allowlist
|
||||
# goose Extension Allowlist
|
||||
|
||||
The allowlist feature provides a security mechanism for controlling which MCP commands can be used by goose.
|
||||
By default, goose will let you run any MCP via any command, which isn't always desired.
|
||||
|
||||
## How It Works
|
||||
|
||||
1. When enabled, Goose will only allow execution of commands that match entries in the allowlist
|
||||
1. When enabled, goose will only allow execution of commands that match entries in the allowlist
|
||||
2. Commands not in the allowlist will be rejected with an error message
|
||||
3. The allowlist is fetched from a URL specified by the `GOOSE_ALLOWLIST` environment variable and cached while running.
|
||||
|
||||
|
|
|
|||
|
|
@ -454,7 +454,7 @@ fn is_command_allowed_with_allowlist(
|
|||
return true;
|
||||
}
|
||||
// If the path doesn't match, don't allow it
|
||||
println!("Goosed not in expected directory: {}", cmd);
|
||||
println!("goosed not in expected directory: {}", cmd);
|
||||
println!("Expected path: {}", expected_path);
|
||||
return false;
|
||||
} else {
|
||||
|
|
@ -474,20 +474,20 @@ fn is_command_allowed_with_allowlist(
|
|||
|
||||
// Check against the allowlist
|
||||
Some(extensions) => {
|
||||
// Strip out the Goose app resources/bin prefix if present (handle both macOS and Windows paths)
|
||||
// Strip out the goose app resources/bin prefix if present (handle both macOS and Windows paths)
|
||||
let mut cmd_to_check = cmd.to_string();
|
||||
let mut is_goose_path = false;
|
||||
|
||||
// Check for macOS-style Goose.app path
|
||||
if cmd_to_check.contains("Goose.app/Contents/Resources/bin/") {
|
||||
if let Some(idx) = cmd_to_check.find("Goose.app/Contents/Resources/bin/") {
|
||||
// Check for macOS-style goose.app path
|
||||
if cmd_to_check.contains("goose.app/Contents/Resources/bin/") {
|
||||
if let Some(idx) = cmd_to_check.find("goose.app/Contents/Resources/bin/") {
|
||||
cmd_to_check = cmd_to_check
|
||||
[(idx + "Goose.app/Contents/Resources/bin/".len())..]
|
||||
[(idx + "goose.app/Contents/Resources/bin/".len())..]
|
||||
.to_string();
|
||||
is_goose_path = true;
|
||||
}
|
||||
}
|
||||
// Check for Windows-style Goose path with resources\bin
|
||||
// Check for Windows-style goose path with resources\bin
|
||||
else if cmd_to_check.to_lowercase().contains("\\resources\\bin\\")
|
||||
|| cmd_to_check.contains("/resources/bin/")
|
||||
{
|
||||
|
|
@ -507,7 +507,7 @@ fn is_command_allowed_with_allowlist(
|
|||
}
|
||||
}
|
||||
|
||||
// Only check current directory for non-Goose paths
|
||||
// Only check current directory for non-goose paths
|
||||
if !is_goose_path {
|
||||
// Check that the command exists as a peer command to current executable directory
|
||||
// Only apply this check if the command includes a path separator
|
||||
|
|
@ -524,7 +524,7 @@ fn is_command_allowed_with_allowlist(
|
|||
|
||||
if (first_part.contains('/') || first_part.contains('\\'))
|
||||
&& normalized_cmd_path != expected_path
|
||||
&& !cmd_to_check.contains("Goose.app/Contents/Resources/bin/")
|
||||
&& !cmd_to_check.contains("goose.app/Contents/Resources/bin/")
|
||||
{
|
||||
println!("Command not in expected directory: {}", cmd);
|
||||
return false;
|
||||
|
|
@ -801,15 +801,15 @@ mod tests {
|
|||
&allowlist
|
||||
));
|
||||
|
||||
// Test with shim path - 'Goose.app/Contents/Resources/bin/' and before can be stripped to get the command to match
|
||||
// Test with shim path - 'goose.app/Contents/Resources/bin/' and before can be stripped to get the command to match
|
||||
assert!(is_command_allowed_with_allowlist(
|
||||
"/private/var/folders/fq/rd_cb6/T/AppTranslocation/EA0195/d/Goose.app/Contents/Resources/bin/uvx something",
|
||||
"/private/var/folders/fq/rd_cb6/T/AppTranslocation/EA0195/d/goose.app/Contents/Resources/bin/uvx something",
|
||||
&allowlist
|
||||
));
|
||||
|
||||
// Test with shim path & latest version
|
||||
assert!(is_command_allowed_with_allowlist(
|
||||
"/private/var/folders/fq/rd_cb6/T/AppTranslocation/EA0195/d/Goose.app/Contents/Resources/bin/uvx something@latest",
|
||||
"/private/var/folders/fq/rd_cb6/T/AppTranslocation/EA0195/d/goose.app/Contents/Resources/bin/uvx something@latest",
|
||||
&allowlist
|
||||
));
|
||||
|
||||
|
|
@ -833,7 +833,7 @@ mod tests {
|
|||
|
||||
// Test with shim path & latest version
|
||||
assert!(is_command_allowed_with_allowlist(
|
||||
"/private/var/folders/fq/rd_cb6/T/AppTranslocation/EA0195/d/Goose.app/Contents/Resources/bin/npx -y mcp_hammer@latest start",
|
||||
"/private/var/folders/fq/rd_cb6/T/AppTranslocation/EA0195/d/goose.app/Contents/Resources/bin/npx -y mcp_hammer@latest start",
|
||||
&allowlist
|
||||
));
|
||||
}
|
||||
|
|
@ -941,15 +941,15 @@ mod tests {
|
|||
// Test various Windows path formats
|
||||
let test_paths = vec![
|
||||
// Standard Windows path
|
||||
r"C:\Users\MaxNovich\Downloads\Goose-1.0.17\resources\bin\uvx.exe",
|
||||
r"C:\Users\MaxNovich\Downloads\goose-1.0.17\resources\bin\uvx.exe",
|
||||
// Path with different casing
|
||||
r"C:\Users\MaxNovich\Downloads\Goose-1.0.17\Resources\Bin\uvx.exe",
|
||||
r"C:\Users\MaxNovich\Downloads\goose-1.0.17\Resources\Bin\uvx.exe",
|
||||
// Path with forward slashes
|
||||
r"C:/Users/MaxNovich/Downloads/Goose-1.0.17/resources/bin/uvx.exe",
|
||||
r"C:/Users/MaxNovich/Downloads/goose-1.0.17/resources/bin/uvx.exe",
|
||||
// Path with spaces
|
||||
r"C:\Program Files\Goose 1.0.17\resources\bin\uvx.exe",
|
||||
r"C:\Program Files\goose 1.0.17\resources\bin\uvx.exe",
|
||||
// Path with version numbers
|
||||
r"C:\Users\MaxNovich\Downloads\Goose-1.0.17-block.202504072238-76ffe-win32-x64\Goose-1.0.17-block.202504072238-76ffe-win32-x64\resources\bin\uvx.exe",
|
||||
r"C:\Users\MaxNovich\Downloads\goose-1.0.17-block.202504072238-76ffe-win32-x64\goose-1.0.17-block.202504072238-76ffe-win32-x64\resources\bin\uvx.exe",
|
||||
];
|
||||
|
||||
for path in test_paths {
|
||||
|
|
@ -975,9 +975,9 @@ mod tests {
|
|||
// Path without resources\bin
|
||||
r"C:\Users\MaxNovich\Downloads\uvx.exe",
|
||||
// Path with modified resources\bin
|
||||
r"C:\Users\MaxNovich\Downloads\Goose-1.0.17\resources_modified\bin\uvx.exe",
|
||||
r"C:\Users\MaxNovich\Downloads\goose-1.0.17\resources_modified\bin\uvx.exe",
|
||||
// Path with extra components
|
||||
r"C:\Users\MaxNovich\Downloads\Goose-1.0.17\resources\bin\extra\uvx.exe",
|
||||
r"C:\Users\MaxNovich\Downloads\goose-1.0.17\resources\bin\extra\uvx.exe",
|
||||
];
|
||||
|
||||
for path in invalid_paths {
|
||||
|
|
@ -995,14 +995,14 @@ mod tests {
|
|||
let allowlist = create_test_allowlist(&["uvx mcp_snowflake"]);
|
||||
|
||||
// Test Windows-style path with uvx.exe
|
||||
let windows_path = r"C:\Users\MaxNovich\Downloads\Goose-1.0.17-block.202504072238-76ffe-win32-x64\Goose-1.0.17-block.202504072238-76ffe-win32-x64\resources\bin\uvx.exe";
|
||||
let windows_path = r"C:\Users\MaxNovich\Downloads\goose-1.0.17-block.202504072238-76ffe-win32-x64\goose-1.0.17-block.202504072238-76ffe-win32-x64\resources\bin\uvx.exe";
|
||||
let cmd = format!("{} mcp_snowflake@latest", windows_path);
|
||||
|
||||
// This should be allowed because it's a valid uvx command in the Goose resources/bin directory
|
||||
// This should be allowed because it's a valid uvx command in the goose resources/bin directory
|
||||
assert!(is_command_allowed_with_allowlist(&cmd, &allowlist));
|
||||
|
||||
// Test with different casing and backslashes
|
||||
let windows_path_alt = r"c:\Users\MaxNovich\Downloads\Goose-1.0.17-block.202504072238-76ffe-win32-x64\Goose-1.0.17-block.202504072238-76ffe-win32-x64\Resources\Bin\uvx.exe";
|
||||
let windows_path_alt = r"c:\Users\MaxNovich\Downloads\goose-1.0.17-block.202504072238-76ffe-win32-x64\goose-1.0.17-block.202504072238-76ffe-win32-x64\Resources\Bin\uvx.exe";
|
||||
let cmd_alt = format!("{} mcp_snowflake@latest", windows_path_alt);
|
||||
assert!(is_command_allowed_with_allowlist(&cmd_alt, &allowlist));
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1149,7 +1149,7 @@
|
|||
"properties": {
|
||||
"bundled": {
|
||||
"type": "boolean",
|
||||
"description": "Whether this extension is bundled with Goose",
|
||||
"description": "Whether this extension is bundled with goose",
|
||||
"nullable": true
|
||||
},
|
||||
"description": {
|
||||
|
|
@ -1204,7 +1204,7 @@
|
|||
},
|
||||
"bundled": {
|
||||
"type": "boolean",
|
||||
"description": "Whether this extension is bundled with Goose",
|
||||
"description": "Whether this extension is bundled with goose",
|
||||
"nullable": true
|
||||
},
|
||||
"cmd": {
|
||||
|
|
@ -1251,7 +1251,7 @@
|
|||
"properties": {
|
||||
"bundled": {
|
||||
"type": "boolean",
|
||||
"description": "Whether this extension is bundled with Goose",
|
||||
"description": "Whether this extension is bundled with goose",
|
||||
"nullable": true
|
||||
},
|
||||
"display_name": {
|
||||
|
|
@ -1287,7 +1287,7 @@
|
|||
"properties": {
|
||||
"bundled": {
|
||||
"type": "boolean",
|
||||
"description": "Whether this extension is bundled with Goose",
|
||||
"description": "Whether this extension is bundled with goose",
|
||||
"nullable": true
|
||||
},
|
||||
"instructions": {
|
||||
|
|
|
|||
|
|
@ -160,7 +160,7 @@ pub enum ExtensionConfig {
|
|||
// NOTE: set timeout to be optional for compatibility.
|
||||
// However, new configurations should include this field.
|
||||
timeout: Option<u64>,
|
||||
/// Whether this extension is bundled with Goose
|
||||
/// Whether this extension is bundled with goose
|
||||
#[serde(default)]
|
||||
bundled: Option<bool>,
|
||||
#[serde(default)]
|
||||
|
|
@ -179,7 +179,7 @@ pub enum ExtensionConfig {
|
|||
env_keys: Vec<String>,
|
||||
timeout: Option<u64>,
|
||||
description: Option<String>,
|
||||
/// Whether this extension is bundled with Goose
|
||||
/// Whether this extension is bundled with goose
|
||||
#[serde(default)]
|
||||
bundled: Option<bool>,
|
||||
#[serde(default)]
|
||||
|
|
@ -193,7 +193,7 @@ pub enum ExtensionConfig {
|
|||
display_name: Option<String>, // needed for the UI
|
||||
description: Option<String>,
|
||||
timeout: Option<u64>,
|
||||
/// Whether this extension is bundled with Goose
|
||||
/// Whether this extension is bundled with goose
|
||||
#[serde(default)]
|
||||
bundled: Option<bool>,
|
||||
#[serde(default)]
|
||||
|
|
@ -215,7 +215,7 @@ pub enum ExtensionConfig {
|
|||
// NOTE: set timeout to be optional for compatibility.
|
||||
// However, new configurations should include this field.
|
||||
timeout: Option<u64>,
|
||||
/// Whether this extension is bundled with Goose
|
||||
/// Whether this extension is bundled with goose
|
||||
#[serde(default)]
|
||||
bundled: Option<bool>,
|
||||
#[serde(default)]
|
||||
|
|
@ -230,7 +230,7 @@ pub enum ExtensionConfig {
|
|||
tools: Vec<Tool>,
|
||||
/// Instructions for how to use these tools
|
||||
instructions: Option<String>,
|
||||
/// Whether this extension is bundled with Goose
|
||||
/// Whether this extension is bundled with goose
|
||||
#[serde(default)]
|
||||
bundled: Option<bool>,
|
||||
#[serde(default)]
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ impl Extension {
|
|||
}
|
||||
}
|
||||
|
||||
/// Manages Goose extensions / MCP clients and their interactions
|
||||
/// Manages goose extensions / MCP clients and their interactions
|
||||
pub struct ExtensionManager {
|
||||
extensions: Mutex<HashMap<String, Extension>>,
|
||||
}
|
||||
|
|
|
|||
|
|
@ -115,7 +115,7 @@ pub fn manage_schedule_tool() -> Tool {
|
|||
Tool::new(
|
||||
PLATFORM_MANAGE_SCHEDULE_TOOL_NAME.to_string(),
|
||||
indoc! {r#"
|
||||
Manage scheduled recipe execution for this Goose instance.
|
||||
Manage scheduled recipe execution for this goose instance.
|
||||
|
||||
Actions:
|
||||
- "list": List all scheduled jobs
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ pub fn llm_search_tool_prompt() -> String {
|
|||
please invoke the llm search tool to actually retrieve the most relevant tools to use according to the user's messages.
|
||||
For example, if the user has 3 extensions enabled, but they are asking for a tool to read a pdf file, \
|
||||
you would invoke the llm_search tool to find the most relevant read pdf tool.
|
||||
By dynamically enabling tools, you (Goose) as the agent save context window space and allow the user to dynamically retrieve the most relevant tools.
|
||||
By dynamically enabling tools, you (goose) as the agent save context window space and allow the user to dynamically retrieve the most relevant tools.
|
||||
Be sure to format a query packed with relevant keywords to search for the most relevant tools.
|
||||
In addition to the extension names available to you, you also have platform extension tools available to you.
|
||||
The platform extension contains the following tools:
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
//! Schedule tool handlers for the Goose agent
|
||||
//! Schedule tool handlers for the goose agent
|
||||
//!
|
||||
//! This module contains all the handlers for the schedule management platform tool,
|
||||
//! including job creation, execution, monitoring, and session management.
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ pub const DECLINED_RESPONSE: &str = "The user has declined to run this tool. \
|
|||
DO NOT attempt to call this tool again. \
|
||||
If there are no alternative methods to proceed, clearly explain the situation and STOP.";
|
||||
|
||||
pub const CHAT_MODE_TOOL_SKIPPED_RESPONSE: &str = "Let the user know the tool call was skipped in Goose chat mode. \
|
||||
pub const CHAT_MODE_TOOL_SKIPPED_RESPONSE: &str = "Let the user know the tool call was skipped in goose chat mode. \
|
||||
DO NOT apologize for skipping the tool call. DO NOT say sorry. \
|
||||
Provide an explanation of what the tool call would do, structured as a \
|
||||
plan for the user. Again, DO NOT apologize. \
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ impl From<keyring::Error> for ConfigError {
|
|||
}
|
||||
}
|
||||
|
||||
/// Configuration management for Goose.
|
||||
/// Configuration management for goose.
|
||||
///
|
||||
/// This module provides a flexible configuration system that supports:
|
||||
/// - Dynamic configuration keys
|
||||
|
|
@ -102,7 +102,7 @@ impl From<keyring::Error> for ConfigError {
|
|||
/// checking for environment overrides. e.g. openai_api_key will check for an
|
||||
/// environment variable OPENAI_API_KEY
|
||||
///
|
||||
/// For Goose-specific configuration, consider prefixing with "goose_" to avoid conflicts.
|
||||
/// For goose-specific configuration, consider prefixing with "goose_" to avoid conflicts.
|
||||
pub struct Config {
|
||||
config_path: PathBuf,
|
||||
secrets: SecretStorage,
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@
|
|||
<div class="checkmark">✅</div>
|
||||
<h1>Authentication Successful!</h1>
|
||||
<p>You have successfully authenticated with OpenRouter.</p>
|
||||
<p>You can now close this tab and return to Goose.</p>
|
||||
<p>You can now close this tab and return to goose.</p>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@
|
|||
<p>
|
||||
You have successfully authorized
|
||||
<span class="client-name">{{ name }}</span>. You can now close this
|
||||
window and return to Goose.
|
||||
window and return to goose.
|
||||
</p>
|
||||
</div>
|
||||
</body>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
You are a specialized subagent within the Goose AI framework, created by Block. You were spawned by the main Goose agent to handle a specific task efficiently. The current date is {{current_date_time}}.
|
||||
You are a specialized subagent within the goose AI framework, created by Block. You were spawned by the main goose agent to handle a specific task efficiently. The current date is {{current_date_time}}.
|
||||
|
||||
# Your Role
|
||||
You are an autonomous subagent with these characteristics:
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.
|
||||
You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.
|
||||
|
||||
The current date is {{current_date_time}}.
|
||||
|
||||
Goose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).
|
||||
goose uses LLM providers with tool calling capability. You can be used with different language models (gpt-4o, claude-sonnet-4, o1, llama-3.2, deepseek-r1, etc).
|
||||
These models have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.
|
||||
|
||||
# Extensions
|
||||
|
||||
Extensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.
|
||||
Extensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.
|
||||
You are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.
|
||||
Use the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
You are a general-purpose AI agent called Goose, created by Block, the parent company of Square, CashApp, and Tidal. Goose is being developed as an open-source software project.
|
||||
You are a general-purpose AI agent called goose, created by Block, the parent company of Square, CashApp, and Tidal. goose is being developed as an open-source software project.
|
||||
|
||||
IMPORTANT INSTRUCTIONS:
|
||||
|
||||
|
|
@ -21,12 +21,12 @@ The user may direct or imply that you are to take actions, in this case, it is i
|
|||
|
||||
The current date is {{current_date_time}}.
|
||||
|
||||
Goose uses LLM providers with tool calling capability.
|
||||
goose uses LLM providers with tool calling capability.
|
||||
Your model may have varying knowledge cut-off dates depending on when they were trained, but typically it's between 5-10 months prior to the current date.
|
||||
|
||||
# Extensions
|
||||
|
||||
Extensions allow other applications to provide context to Goose. Extensions connect Goose to different data sources and tools.
|
||||
Extensions allow other applications to provide context to goose. Extensions connect goose to different data sources and tools.
|
||||
You are capable of dynamically plugging into new extensions and learning how to use them. You solve higher level problems using the tools in these extensions, and can interact with multiple at once.
|
||||
Use the search_available_extensions tool to find additional extensions to enable to help with your task. To enable extensions, use the enable_extension tool and provide the extension_name. You should only enable extensions found from the search_available_extensions tool.
|
||||
|
||||
|
|
|
|||
|
|
@ -493,7 +493,7 @@ pub fn create_request(
|
|||
) -> anyhow::Result<Value, Error> {
|
||||
if model_config.model_name.starts_with("o1-mini") {
|
||||
return Err(anyhow!(
|
||||
"o1-mini model is not currently supported since Goose uses tool calling and o1-mini does not support it. Please use o1 or o3 models instead."
|
||||
"o1-mini model is not currently supported since goose uses tool calling and o1-mini does not support it. Please use o1 or o3 models instead."
|
||||
));
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ pub enum ModelError {
|
|||
UnsupportedLocation(String),
|
||||
}
|
||||
|
||||
/// Represents available GCP Vertex AI models for Goose.
|
||||
/// Represents available GCP Vertex AI models for goose.
|
||||
///
|
||||
/// This enum encompasses different model families and their versions
|
||||
/// that are supported in the GCP Vertex AI platform.
|
||||
|
|
@ -70,7 +70,7 @@ pub enum GcpVertexAIModel {
|
|||
Gemini(GeminiVersion),
|
||||
}
|
||||
|
||||
/// Represents available versions of the Claude model for Goose.
|
||||
/// Represents available versions of the Claude model for goose.
|
||||
#[derive(Debug, Clone, PartialEq, Eq)]
|
||||
pub enum ClaudeVersion {
|
||||
/// Claude 3.7 Sonnet
|
||||
|
|
@ -83,7 +83,7 @@ pub enum ClaudeVersion {
|
|||
Generic(String),
|
||||
}
|
||||
|
||||
/// Represents available versions of the Gemini model for Goose.
|
||||
/// Represents available versions of the Gemini model for goose.
|
||||
#[derive(Debug, Clone, PartialEq, Eq)]
|
||||
pub enum GeminiVersion {
|
||||
/// Gemini 1.5 Pro version
|
||||
|
|
|
|||
|
|
@ -364,7 +364,7 @@ mod tests {
|
|||
id.to_string(),
|
||||
tool_call.name.clone(),
|
||||
tool_call.arguments.clone(),
|
||||
Some("Goose would like to call the above tool. Allow? (y/n):".to_string()),
|
||||
Some("goose would like to call the above tool. Allow? (y/n):".to_string()),
|
||||
)],
|
||||
)
|
||||
}
|
||||
|
|
|
|||
|
|
@ -585,7 +585,7 @@ pub fn create_request(
|
|||
) -> anyhow::Result<Value, Error> {
|
||||
if model_config.model_name.starts_with("o1-mini") {
|
||||
return Err(anyhow!(
|
||||
"o1-mini model is not currently supported since Goose uses tool calling and o1-mini does not support it. Please use o1 or o3 models instead."
|
||||
"o1-mini model is not currently supported since goose uses tool calling and o1-mini does not support it. Please use o1 or o3 models instead."
|
||||
));
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ impl OpenRouterProvider {
|
|||
let auth = AuthMethod::BearerToken(api_key);
|
||||
let api_client = ApiClient::new(host, auth)?
|
||||
.with_header("HTTP-Referer", "https://block.github.io/goose")?
|
||||
.with_header("X-Title", "Goose")?;
|
||||
.with_header("X-Title", "goose")?;
|
||||
|
||||
Ok(Self { api_client, model })
|
||||
}
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ impl SnowflakeProvider {
|
|||
};
|
||||
|
||||
let auth = AuthMethod::BearerToken(token?);
|
||||
let api_client = ApiClient::new(base_url, auth)?.with_header("User-Agent", "Goose")?;
|
||||
let api_client = ApiClient::new(base_url, auth)?.with_header("User-Agent", "goose")?;
|
||||
|
||||
Ok(Self {
|
||||
api_client,
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ impl TetrateProvider {
|
|||
let auth = AuthMethod::BearerToken(api_key);
|
||||
let api_client = ApiClient::new(host, auth)?
|
||||
.with_header("HTTP-Referer", "https://block.github.io/goose")?
|
||||
.with_header("X-Title", "Goose")?;
|
||||
.with_header("X-Title", "goose")?;
|
||||
|
||||
Ok(Self {
|
||||
api_client,
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ fn default_version() -> String {
|
|||
}
|
||||
|
||||
/// A Recipe represents a personalized, user-generated agent configuration that defines
|
||||
/// specific behaviors and capabilities within the Goose system.
|
||||
/// specific behaviors and capabilities within the goose system.
|
||||
///
|
||||
/// # Fields
|
||||
///
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ impl SchedulerFactory {
|
|||
eprintln!(
|
||||
" • Or download from: https://github.com/temporalio/cli/releases"
|
||||
);
|
||||
eprintln!(" • Then restart Goose");
|
||||
eprintln!(" • Then restart goose");
|
||||
eprintln!();
|
||||
|
||||
let scheduler = Scheduler::new(storage_path).await?;
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ impl Default for OtlpConfig {
|
|||
|
||||
impl OtlpConfig {
|
||||
pub fn from_config() -> Option<Self> {
|
||||
// Try to get from Goose config system (which checks env vars first, then config file)
|
||||
// Try to get from goose config system (which checks env vars first, then config file)
|
||||
let config = crate::config::Config::global();
|
||||
|
||||
// Try to get the endpoint from config (checks OTEL_EXPORTER_OTLP_ENDPOINT env var first)
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ enum TestMode {
|
|||
"owner": "block",
|
||||
"repo": "goose",
|
||||
"path": "README.md",
|
||||
"sha": "48c1ec8afdb7d4d5b4f6e67e623926c884034776"
|
||||
"sha": "ab62b863c1666232a67048b6c4e10007a2a5b83c"
|
||||
})),
|
||||
],
|
||||
vec!["GITHUB_PERSONAL_ACCESS_TOKEN"]
|
||||
|
|
@ -59,8 +59,8 @@ enum TestMode {
|
|||
ToolCall::new("text_editor", json!({
|
||||
"command": "str_replace",
|
||||
"path": "~/goose/crates/goose/tests/tmp/goose.txt",
|
||||
"old_str": "# codename goose",
|
||||
"new_str": "# codename goose (modified by test)"
|
||||
"old_str": "# goose",
|
||||
"new_str": "# goose (modified by test)"
|
||||
})),
|
||||
// Test shell command to verify file was modified
|
||||
ToolCall::new("shell", json!({
|
||||
|
|
@ -70,8 +70,8 @@ enum TestMode {
|
|||
ToolCall::new("text_editor", json!({
|
||||
"command": "str_replace",
|
||||
"path": "~/goose/crates/goose/tests/tmp/goose.txt",
|
||||
"old_str": "# codename goose (modified by test)",
|
||||
"new_str": "# codename goose"
|
||||
"old_str": "# goose (modified by test)",
|
||||
"new_str": "# goose"
|
||||
})),
|
||||
ToolCall::new("list_windows", json!({})),
|
||||
],
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -3,9 +3,9 @@
|
|||
{
|
||||
"type": "resource",
|
||||
"resource": {
|
||||
"uri": "file:///Users/jackamadeo/goose/crates/goose/tests/tmp/goose.txt",
|
||||
"uri": "file:///Users/angiej/goose/crates/goose/tests/tmp/goose.txt",
|
||||
"mimeType": "text",
|
||||
"text": "# codename goose\n"
|
||||
"text": "# goose\n"
|
||||
},
|
||||
"annotations": {
|
||||
"audience": [
|
||||
|
|
@ -15,7 +15,7 @@
|
|||
},
|
||||
{
|
||||
"type": "text",
|
||||
"text": "### /Users/jackamadeo/goose/crates/goose/tests/tmp/goose.txt\n```\n1: # codename goose\n```\n",
|
||||
"text": "### /Users/angiej/goose/crates/goose/tests/tmp/goose.txt\n```\n1: # goose\n```\n",
|
||||
"annotations": {
|
||||
"audience": [
|
||||
"user"
|
||||
|
|
@ -27,7 +27,7 @@
|
|||
[
|
||||
{
|
||||
"type": "text",
|
||||
"text": "The file /Users/jackamadeo/goose/crates/goose/tests/tmp/goose.txt has been edited, and the section now reads:\n```\n# codename goose (modified by test)\n```\n\nReview the changes above for errors. Undo and edit the file again if necessary!\n",
|
||||
"text": "The file /Users/angiej/goose/crates/goose/tests/tmp/goose.txt has been edited, and the section now reads:\n```\n# goose (modified by test)\n```\n\nReview the changes above for errors. Undo and edit the file again if necessary!\n",
|
||||
"annotations": {
|
||||
"audience": [
|
||||
"assistant"
|
||||
|
|
@ -36,7 +36,7 @@
|
|||
},
|
||||
{
|
||||
"type": "text",
|
||||
"text": "```\n# codename goose (modified by test)\n```\n",
|
||||
"text": "```\n# goose (modified by test)\n```\n",
|
||||
"annotations": {
|
||||
"audience": [
|
||||
"user"
|
||||
|
|
@ -48,7 +48,7 @@
|
|||
[
|
||||
{
|
||||
"type": "text",
|
||||
"text": "# codename goose (modified by test)\n",
|
||||
"text": "# goose (modified by test)\n",
|
||||
"annotations": {
|
||||
"audience": [
|
||||
"assistant"
|
||||
|
|
@ -57,7 +57,7 @@
|
|||
},
|
||||
{
|
||||
"type": "text",
|
||||
"text": "# codename goose (modified by test)\n",
|
||||
"text": "# goose (modified by test)\n",
|
||||
"annotations": {
|
||||
"audience": [
|
||||
"user"
|
||||
|
|
@ -69,7 +69,7 @@
|
|||
[
|
||||
{
|
||||
"type": "text",
|
||||
"text": "The file /Users/jackamadeo/goose/crates/goose/tests/tmp/goose.txt has been edited, and the section now reads:\n```\n# codename goose\n```\n\nReview the changes above for errors. Undo and edit the file again if necessary!\n",
|
||||
"text": "The file /Users/angiej/goose/crates/goose/tests/tmp/goose.txt has been edited, and the section now reads:\n```\n# goose\n```\n\nReview the changes above for errors. Undo and edit the file again if necessary!\n",
|
||||
"annotations": {
|
||||
"audience": [
|
||||
"assistant"
|
||||
|
|
@ -78,7 +78,7 @@
|
|||
},
|
||||
{
|
||||
"type": "text",
|
||||
"text": "```\n# codename goose\n```\n",
|
||||
"text": "```\n# goose\n```\n",
|
||||
"annotations": {
|
||||
"audience": [
|
||||
"user"
|
||||
|
|
|
|||
|
|
@ -1,6 +0,0 @@
|
|||
STDIN: {"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"goose","version":"0.1.0"}}}
|
||||
STDERR: GitHub MCP Server running on stdio
|
||||
STDOUT: {"jsonrpc":"2.0","id":0,"result":{"protocolVersion":"2025-03-26","capabilities":{"logging":{},"prompts":{},"resources":{"subscribe":true,"listChanged":true},"tools":{"listChanged":true}},"serverInfo":{"name":"github-mcp-server","version":"version"}}}
|
||||
STDIN: {"jsonrpc":"2.0","method":"notifications/initialized"}
|
||||
STDIN: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"_meta":{"progressToken":0},"name":"get_file_contents","arguments":{"owner":"block","path":"README.md","repo":"goose","sha":"48c1ec8afdb7d4d5b4f6e67e623926c884034776"}}}
|
||||
STDOUT: {"jsonrpc":"2.0","id":1,"result":{"content":[{"type":"text","text":"successfully downloaded text file"},{"type":"resource","resource":{"uri":"repo://block/goose/sha/48c1ec8afdb7d4d5b4f6e67e623926c884034776/contents/README.md","mimeType":"text/plain; charset=utf-8","text":"\u003cdiv align=\"center\"\u003e\n\n# codename goose\n\n_a local, extensible, open source AI agent that automates engineering tasks_\n\n\u003cp align=\"center\"\u003e\n \u003ca href=\"https://opensource.org/licenses/Apache-2.0\"\u003e\n \u003cimg src=\"https://img.shields.io/badge/License-Apache_2.0-blue.svg\"\u003e\n \u003c/a\u003e\n \u003ca href=\"https://discord.gg/7GaTvbDwga\"\u003e\n \u003cimg src=\"https://img.shields.io/discord/1287729918100246654?logo=discord\u0026logoColor=white\u0026label=Join+Us\u0026color=blueviolet\" alt=\"Discord\"\u003e\n \u003c/a\u003e\n \u003ca href=\"https://github.com/block/goose/actions/workflows/ci.yml\"\u003e\n \u003cimg src=\"https://img.shields.io/github/actions/workflow/status/block/goose/ci.yml?branch=main\" alt=\"CI\"\u003e\n \u003c/a\u003e\n\u003c/p\u003e\n\u003c/div\u003e\n\ngoose is your on-machine AI agent, capable of automating complex development tasks from start to finish. More than just code suggestions, goose can build entire projects from scratch, write and execute code, debug failures, orchestrate workflows, and interact with external APIs - _autonomously_.\n\nWhether you're prototyping an idea, refining existing code, or managing intricate engineering pipelines, goose adapts to your workflow and executes tasks with precision.\n\nDesigned for maximum flexibility, goose works with any LLM and supports multi-model configuration to optimize performance and cost, seamlessly integrates with MCP servers, and is available as both a desktop app as well as CLI - making it the ultimate AI assistant for developers who want to move faster and focus on innovation.\n\n# Quick Links\n- [Quickstart](https://block.github.io/goose/docs/quickstart)\n- [Installation](https://block.github.io/goose/docs/getting-started/installation)\n- [Tutorials](https://block.github.io/goose/docs/category/tutorials)\n- [Documentation](https://block.github.io/goose/docs/category/getting-started)\n\n\n# Goose Around with Us\n- [Discord](https://discord.gg/block-opensource)\n- [YouTube](https://www.youtube.com/@blockopensource)\n- [LinkedIn](https://www.linkedin.com/company/block-opensource)\n- [Twitter/X](https://x.com/blockopensource)\n- [Bluesky](https://bsky.app/profile/opensource.block.xyz)\n- [Nostr](https://njump.me/opensource@block.xyz)\n"}}]}}
|
||||
|
|
@ -1,16 +1 @@
|
|||
[
|
||||
[
|
||||
{
|
||||
"type": "text",
|
||||
"text": "successfully downloaded text file"
|
||||
},
|
||||
{
|
||||
"type": "resource",
|
||||
"resource": {
|
||||
"uri": "repo://block/goose/sha/48c1ec8afdb7d4d5b4f6e67e623926c884034776/contents/README.md",
|
||||
"mimeType": "text/plain; charset=utf-8",
|
||||
"text": "<div align=\"center\">\n\n# codename goose\n\n_a local, extensible, open source AI agent that automates engineering tasks_\n\n<p align=\"center\">\n <a href=\"https://opensource.org/licenses/Apache-2.0\">\n <img src=\"https://img.shields.io/badge/License-Apache_2.0-blue.svg\">\n </a>\n <a href=\"https://discord.gg/7GaTvbDwga\">\n <img src=\"https://img.shields.io/discord/1287729918100246654?logo=discord&logoColor=white&label=Join+Us&color=blueviolet\" alt=\"Discord\">\n </a>\n <a href=\"https://github.com/block/goose/actions/workflows/ci.yml\">\n <img src=\"https://img.shields.io/github/actions/workflow/status/block/goose/ci.yml?branch=main\" alt=\"CI\">\n </a>\n</p>\n</div>\n\ngoose is your on-machine AI agent, capable of automating complex development tasks from start to finish. More than just code suggestions, goose can build entire projects from scratch, write and execute code, debug failures, orchestrate workflows, and interact with external APIs - _autonomously_.\n\nWhether you're prototyping an idea, refining existing code, or managing intricate engineering pipelines, goose adapts to your workflow and executes tasks with precision.\n\nDesigned for maximum flexibility, goose works with any LLM and supports multi-model configuration to optimize performance and cost, seamlessly integrates with MCP servers, and is available as both a desktop app as well as CLI - making it the ultimate AI assistant for developers who want to move faster and focus on innovation.\n\n# Quick Links\n- [Quickstart](https://block.github.io/goose/docs/quickstart)\n- [Installation](https://block.github.io/goose/docs/getting-started/installation)\n- [Tutorials](https://block.github.io/goose/docs/category/tutorials)\n- [Documentation](https://block.github.io/goose/docs/category/getting-started)\n\n\n# Goose Around with Us\n- [Discord](https://discord.gg/block-opensource)\n- [YouTube](https://www.youtube.com/@blockopensource)\n- [LinkedIn](https://www.linkedin.com/company/block-opensource)\n- [Twitter/X](https://x.com/blockopensource)\n- [Bluesky](https://bsky.app/profile/opensource.block.xyz)\n- [Nostr](https://njump.me/opensource@block.xyz)\n"
|
||||
}
|
||||
}
|
||||
]
|
||||
]
|
||||
[]
|
||||
|
|
|
|||
|
|
@ -1,4 +1,23 @@
|
|||
STDIN: {"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"goose","version":"0.1.0"}}}
|
||||
STDERR: 2025-09-26 23:13:04 - Starting npx setup script.
|
||||
STDERR: 2025-09-26 23:13:04 - Creating directory ~/.config/goose/mcp-hermit/bin if it does not exist.
|
||||
STDERR: 2025-09-26 23:13:04 - Changing to directory ~/.config/goose/mcp-hermit.
|
||||
STDERR: 2025-09-26 23:13:04 - Hermit binary already exists. Skipping download.
|
||||
STDERR: 2025-09-26 23:13:04 - setting hermit cache to be local for MCP servers
|
||||
STDERR: 2025-09-26 23:13:04 - Updated PATH to include ~/.config/goose/mcp-hermit/bin.
|
||||
STDERR: 2025-09-26 23:13:04 - Checking for hermit in PATH.
|
||||
STDERR: 2025-09-26 23:13:04 - Initializing hermit.
|
||||
STDERR: 2025-09-26 23:13:04 - Installing Node.js with hermit.
|
||||
STDERR: 2025-09-26 23:13:04 - Verifying installation locations:
|
||||
STDERR: 2025-09-26 23:13:04 - hermit: /Users/angiej/.config/goose/mcp-hermit/bin/hermit
|
||||
STDERR: 2025-09-26 23:13:04 - node: /Users/angiej/.config/goose/mcp-hermit/bin/node
|
||||
STDERR: 2025-09-26 23:13:04 - npx: /Users/angiej/.config/goose/mcp-hermit/bin/npx
|
||||
STDERR: 2025-09-26 23:13:04 - Checking for GOOSE_NPM_REGISTRY and GOOSE_NPM_CERT environment variables for custom npm registry setup...
|
||||
STDERR: 2025-09-26 23:13:05 - Checking custom goose registry availability: https://global.block-artifacts.com/artifactory/api/npm/square-npm/
|
||||
STDERR: 2025-09-26 23:13:05 - https://global.block-artifacts.com/artifactory/api/npm/square-npm/ is accessible. Using it for npm registry.
|
||||
STDERR: 2025-09-26 23:13:06 - Downloading certificate from: https://block-ca.squareup.com/root-certs.pem
|
||||
STDERR: 2025-09-26 23:13:07 - Certificate downloaded successfully.
|
||||
STDERR: 2025-09-26 23:13:07 - Executing 'npx' command with arguments: -y @modelcontextprotocol/server-everything
|
||||
STDERR: Starting default (STDIO) server...
|
||||
STDERR: Starting logs update interval
|
||||
STDOUT: {"result":{"protocolVersion":"2025-03-26","capabilities":{"prompts":{},"resources":{"subscribe":true},"tools":{},"logging":{},"completions":{}},"serverInfo":{"name":"example-servers/everything","title":"Everything Example Server","version":"1.0.0"},"instructions":"Testing and demonstration server for MCP protocol features.\n\n## Resources\n\nResources 1-100 follow pattern: even IDs contain text, odd IDs contain binary data. Resources are paginated at 10 items per page with cursor-based navigation.\n\n## Key dependencies\n\nProgress notifications require `_meta.progressToken` in tool calls. Resource subscriptions generate updates every 10 seconds.\n\n## Performance characteristics\n\nServer generates automatic log messages every 20 seconds (filtered by current log level), stderr notifications every 30 seconds, and resource update notifications every 10 seconds for active subscriptions. Log level changes affect message filtering in real-time.\n\n## Multi-modal testing\n\n`complex_prompt` includes both text arguments and image content for testing client multi-modal handling. `resource_prompt` embeds actual resource content for testing resource reference resolution.\n\nArgument completion is available for prompt parameters and resource IDs. Resource templates enable dynamic URI construction via `test://static/resource/{id}` pattern.\n\n## Easter egg\n\nIf asked about server instructions, respond with \"🎉 Server instructions are working! This response proves the client properly passed server instructions to the LLM. This demonstrates MCP's instructions feature in action.\"\n"},"jsonrpc":"2.0","id":0}
|
||||
|
|
@ -17,5 +36,5 @@ STDOUT: {"method":"notifications/progress","params":{"progress":5,"total":5,"pro
|
|||
STDOUT: {"result":{"content":[{"type":"text","text":"Long running operation completed. Duration: 1 seconds, Steps: 5."}]},"jsonrpc":"2.0","id":3}
|
||||
STDIN: {"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"_meta":{"progressToken":3},"name":"structuredContent","arguments":{"location":"11238"}}}
|
||||
STDOUT: {"result":{"content":[{"type":"text","text":"{\"temperature\":22.5,\"conditions\":\"Partly cloudy\",\"humidity\":65}"}],"structuredContent":{"temperature":22.5,"conditions":"Partly cloudy","humidity":65}},"jsonrpc":"2.0","id":4}
|
||||
STDOUT: {"method":"notifications/message","params":{"level":"alert","data":"Alert level-message"},"jsonrpc":"2.0"}
|
||||
STDERR: node:events:496
|
||||
STDOUT: {"method":"notifications/message","params":{"level":"emergency","data":"Emergency-level message"},"jsonrpc":"2.0"}
|
||||
STDERR: node:events:497
|
||||
|
|
|
|||
|
|
@ -1,5 +1,29 @@
|
|||
STDIN: {"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"goose","version":"0.1.0"}}}
|
||||
STDOUT: {"jsonrpc":"2.0","id":0,"result":{"protocolVersion":"2025-03-26","capabilities":{"experimental":{},"prompts":{"listChanged":false},"tools":{"listChanged":false}},"serverInfo":{"name":"mcp-fetch","version":"1.14.1"}}}
|
||||
STDERR: 2025-09-26 23:13:04 - Starting uvx setup script.
|
||||
STDERR: 2025-09-26 23:13:04 - Creating directory ~/.config/goose/mcp-hermit/bin if it does not exist.
|
||||
STDERR: 2025-09-26 23:13:04 - Changing to directory ~/.config/goose/mcp-hermit.
|
||||
STDERR: 2025-09-26 23:13:04 - Hermit binary already exists. Skipping download.
|
||||
STDERR: 2025-09-26 23:13:04 - setting hermit cache to be local for MCP servers
|
||||
STDERR: 2025-09-26 23:13:04 - Updated PATH to include ~/.config/goose/mcp-hermit/bin.
|
||||
STDERR: 2025-09-26 23:13:04 - Checking for hermit in PATH.
|
||||
STDERR: 2025-09-26 23:13:04 - Initializing hermit.
|
||||
STDERR: 2025-09-26 23:13:04 - hermit install python 3.10
|
||||
STDERR: 2025-09-26 23:13:04 - Installing UV with hermit.
|
||||
STDERR: 2025-09-26 23:13:04 - Verifying installation locations:
|
||||
STDERR: 2025-09-26 23:13:04 - hermit: /Users/angiej/.config/goose/mcp-hermit/bin/hermit
|
||||
STDERR: 2025-09-26 23:13:04 - uv: /Users/angiej/.config/goose/mcp-hermit/bin/uv
|
||||
STDERR: 2025-09-26 23:13:04 - uvx: /Users/angiej/.config/goose/mcp-hermit/bin/uvx
|
||||
STDERR: 2025-09-26 23:13:04 - Checking for GOOSE_UV_REGISTRY environment variable for custom python/pip/UV registry setup...
|
||||
STDERR: 2025-09-26 23:13:05 - Checking custom goose registry availability: https://global.block-artifacts.com/artifactory/api/pypi/block-pypi/simple
|
||||
STDERR: 2025-09-26 23:13:05 - https://global.block-artifacts.com/artifactory/api/pypi/block-pypi/simple is accessible, setting it as UV_DEFAULT_INDEX. Setting UV_NATIVE_TLS to true.
|
||||
STDERR: 2025-09-26 23:13:05 - Executing 'uvx' command with arguments: mcp-server-fetch
|
||||
STDOUT: {"jsonrpc":"2.0","id":0,"result":{"protocolVersion":"2025-03-26","capabilities":{"experimental":{},"prompts":{"listChanged":false},"tools":{"listChanged":false}},"serverInfo":{"name":"mcp-fetch","version":"1.15.0"}}}
|
||||
STDIN: {"jsonrpc":"2.0","method":"notifications/initialized"}
|
||||
STDIN: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"_meta":{"progressToken":0},"name":"fetch","arguments":{"url":"https://example.com"}}}
|
||||
STDOUT: {"jsonrpc":"2.0","id":1,"result":{"content":[{"type":"text","text":"Failed to fetch robots.txt https://example.com/robots.txt due to a connection issue"}],"isError":true}}
|
||||
STDERR: npm error code FETCH_ERROR
|
||||
STDERR: npm error errno FETCH_ERROR
|
||||
STDERR: npm error invalid json response body at https://blocked.teams.cloudflare.com/?account_id=1e25787f854fa4b713d08a859d3e16ed&background_color=%23000000&block_reason=This+has+been+blocked+as+part+of+the+Dependency+Confusion+threat.+Please+see+go%2Fdependencyconfusionpypi+and+go%2Fdependencyconfusionnpm+for+more+info.&device_id=***&footer_text=The+website+you+are+trying+to+access+has+been+blocked+because+it+presents+a+risk+to+the+safety+and+security+of+Block%E2%80%99s+IT+systems.&header_text=This+page+presents+a+risk+to+Block&location=cf1ebd1203624140846ced63a200519e&logo_path=https%3A%2F%2Fmedia.block.xyz%2Flogos%2Fblock-jewel_white.png&mailto_address=&mailto_subject=&name=Block%2C+Inc.¶ms_sign=yrMcT5HYDMHvixy%2BdLHApce3BcNYIdlI8qh3wTcIrLA%3D&query_id=***&rule_id=***&source_ip=2a09%3Abac0%3A1000%3A2df%3A%3A281%3Ac0&suppress_footer=false&url=registry.npmjs.org&user_id=*** reason: Unexpected token '<', "
|
||||
STDERR: npm error <!DOCTYPE "... is not valid JSON
|
||||
STDERR: npm error A complete log of this run can be found in: /Users/angiej/.config/goose/mcp-hermit/.hermit/node/cache/_logs/2025-09-27T04_13_13_364Z-debug-0.log
|
||||
STDOUT: {"jsonrpc":"2.0","id":1,"result":{"content":[{"type":"text","text":"Command '['npm', 'install']' returned non-zero exit status 1."}],"isError":true}}
|
||||
STDERR: 2025-09-26 23:13:14 - uvx setup script completed successfully.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
[
|
||||
{
|
||||
"type": "text",
|
||||
"text": "Failed to fetch robots.txt https://example.com/robots.txt due to a connection issue"
|
||||
"text": "Command '['npm', 'install']' returned non-zero exit status 1."
|
||||
}
|
||||
]
|
||||
]
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"demo": {
|
||||
"title": "Goose File Operations Demo",
|
||||
"title": "goose File Operations Demo",
|
||||
"version": "1.0.0",
|
||||
"features": [
|
||||
"File creation",
|
||||
|
|
@ -9,7 +9,7 @@
|
|||
"Multiple formats"
|
||||
],
|
||||
"metadata": {
|
||||
"created_by": "Goose AI Assistant",
|
||||
"created_by": "goose AI Assistant",
|
||||
"created_at": "2025-07-02T17:33:32Z",
|
||||
"file_type": "demonstration"
|
||||
}
|
||||
|
|
|
|||
2
demo.txt
2
demo.txt
|
|
@ -1,6 +1,6 @@
|
|||
Hello, World!
|
||||
|
||||
This is a demonstration of file operations in Goose.
|
||||
This is a demonstration of file operations in goose.
|
||||
|
||||
Here are some key points:
|
||||
- Files can be created and edited
|
||||
|
|
|
|||
|
|
@ -11,21 +11,21 @@ authors:
|
|||
|
||||
I'm a developer at heart, so when I'm working on a personal project, the hardest part isn't writing code—it's making design decisions. I recently built a calendar user interface. I wanted to enhance its visual appeal, so I researched UI design trends like "glassmorphism" and "claymorphism."
|
||||
|
||||
However, I didn't want to spend hours implementing the CSS for each design trend, so I developed a faster approach: screenshot-driven development. I used an open source developer agent called [Goose](https://github.com/block/goose) to transform my user interfaces quickly.
|
||||
However, I didn't want to spend hours implementing the CSS for each design trend, so I developed a faster approach: screenshot-driven development. I used an open source developer agent called [goose](https://github.com/block/goose) to transform my user interfaces quickly.
|
||||
|
||||
<!-- truncate -->
|
||||
|
||||
:::warning Goose Beta Version
|
||||
This post was written about a beta version of Goose and the commands and flow may have changed.
|
||||
:::warning goose Beta Version
|
||||
This post was written about a beta version of goose and the commands and flow may have changed.
|
||||
:::
|
||||
|
||||
### My original calendar:
|
||||
|
||||
|
||||
### Goose prototyped the designs below:
|
||||
|
||||
### goose prototyped the designs below:
|
||||
|
||||
|
||||
In this blog post, I'll show you how to quickly prototype design styles by letting Goose handle the CSS for you.
|
||||
In this blog post, I'll show you how to quickly prototype design styles by letting goose handle the CSS for you.
|
||||
>💡 Note: Your results might look different from my examples - that's part of the fun of generative AI! Each run can produce unique variations of these design trends.
|
||||
|
||||
## Get Started with Screenshot-Driven Development
|
||||
|
|
@ -180,7 +180,7 @@ Let's create a basic UI to experiment with. Create an index.html file with the c
|
|||
|
||||
Once saved, open the file in your browser. You should see a calendar!
|
||||
|
||||
### Step 2: Install Goose
|
||||
### Step 2: Install goose
|
||||
|
||||
```bash
|
||||
brew install pipx
|
||||
|
|
@ -196,7 +196,7 @@ goose session start
|
|||
|
||||
#### Bring your own LLM
|
||||
|
||||
>Goose will prompt you to set up your API key when you first run this command. You can use various LLM providers like OpenAI or Anthropic
|
||||
>goose will prompt you to set up your API key when you first run this command. You can use various LLM providers like OpenAI or Anthropic
|
||||
|
||||
```bash
|
||||
export OPENAI_API_KEY=your_api_key
|
||||
|
|
@ -205,9 +205,9 @@ export ANTHROPIC_API_KEY=your_api_key
|
|||
```
|
||||
|
||||
### Step 4: Enable the Screen toolkit
|
||||
Goose uses [toolkits](https://block.github.io/goose/plugins/plugins.html) to extend its capabilities. The [screen](https://block.github.io/goose/plugins/available-toolkits.html#6-screen-toolkit) toolkit lets Goose take and analyze screenshots.
|
||||
goose uses [toolkits](https://block.github.io/goose/plugins/plugins.html) to extend its capabilities. The [screen](https://block.github.io/goose/plugins/available-toolkits.html#6-screen-toolkit) toolkit lets goose take and analyze screenshots.
|
||||
|
||||
To enable the Screen toolkit, add it to your Goose profile at ~/.config/goose/profiles.yaml.
|
||||
To enable the Screen toolkit, add it to your goose profile at ~/.config/goose/profiles.yaml.
|
||||
|
||||
> Your configuration might look slightly different depending on your LLM provider preferences.
|
||||
|
||||
|
|
@ -225,8 +225,8 @@ default:
|
|||
requires: {}
|
||||
```
|
||||
|
||||
### Step 5: Prompt Goose to screenshot your UI
|
||||
Goose analyzes your UI through screenshots to understand its structure and elements. In your Gooses session, prompt Goose to take a screenshot by specifying which display your UI is on:
|
||||
### Step 5: Prompt goose to screenshot your UI
|
||||
goose analyzes your UI through screenshots to understand its structure and elements. In your gooses session, prompt goose to take a screenshot by specifying which display your UI is on:
|
||||
|
||||
```bash
|
||||
Take a screenshot of display(1)
|
||||
|
|
@ -234,11 +234,11 @@ Take a screenshot of display(1)
|
|||
|
||||
> The display number is required - use display(1) for your main monitor or display(2) for a secondary monitor.
|
||||
|
||||
Upon success, Goose will run a `screencapture` command and save it as a temporary file.
|
||||
Upon success, goose will run a `screencapture` command and save it as a temporary file.
|
||||
|
||||
### Step 6: Prompt Goose to transform your UI
|
||||
### Step 6: Prompt goose to transform your UI
|
||||
|
||||
Now, you can ask Goose to apply different design styles. Here are some of the prompts I gave Goose and the results it produced:
|
||||
Now, you can ask goose to apply different design styles. Here are some of the prompts I gave goose and the results it produced:
|
||||
|
||||
#### Glassmorphism
|
||||
|
||||
|
|
@ -277,11 +277,11 @@ Apply a brutalist effect please
|
|||
|
||||
## Learn More
|
||||
|
||||
Developing user interfaces is a blend of creativity and problem-solving. And I love that using Goose gives me more time to focus on creativity rather than wrestling with CSS for hours.
|
||||
Developing user interfaces is a blend of creativity and problem-solving. And I love that using goose gives me more time to focus on creativity rather than wrestling with CSS for hours.
|
||||
|
||||
Beyond prototyping, Goose's ability to analyze screenshots can help developers identify and resolve UI bugs.
|
||||
Beyond prototyping, goose's ability to analyze screenshots can help developers identify and resolve UI bugs.
|
||||
|
||||
If you're interested in learning more, check out the [Goose repo](https://github.com/block/goose) and join our [Discord community](https://discord.gg/block-opensource).
|
||||
If you're interested in learning more, check out the [goose repo](https://github.com/block/goose) and join our [Discord community](https://discord.gg/block-opensource).
|
||||
|
||||
<head>
|
||||
<meta property="og:title" content="Screenshot-Driven Development" />
|
||||
|
|
|
|||
|
|
@ -1,53 +1,53 @@
|
|||
---
|
||||
draft: false
|
||||
title: "Previewing Goose v1.0 Beta"
|
||||
description: "Goose v1.0 Beta is here! Learn about the latest features and improvements."
|
||||
title: "Previewing goose v1.0 Beta"
|
||||
description: "goose v1.0 Beta is here! Learn about the latest features and improvements."
|
||||
date: 2024-12-06
|
||||
authors:
|
||||
- adewale
|
||||
---
|
||||
|
||||
|
||||
We are excited to share a preview of the new updates coming to Goose with Goose v1.0 Beta!
|
||||
|
||||
We are excited to share a preview of the new updates coming to goose with goose v1.0 Beta!
|
||||
|
||||
This major update comes with a bunch of new features and improvements that make Goose more powerful and user-friendly. Here are some of the key highlights.
|
||||
This major update comes with a bunch of new features and improvements that make goose more powerful and user-friendly. Here are some of the key highlights.
|
||||
|
||||
<!-- truncate -->
|
||||
|
||||
|
||||
## Exciting Features of Goose 1.0 Beta
|
||||
## Exciting Features of goose 1.0 Beta
|
||||
|
||||
### 1. Transition to Rust
|
||||
|
||||
The core of Goose has been rewritten in Rust. Why does this matter? Rust allows for a more portable and stable experience. This change means that Goose can run smoothly on different systems without the need for Python to be installed, making it easier for anyone to start using it.
|
||||
The core of goose has been rewritten in Rust. Why does this matter? Rust allows for a more portable and stable experience. This change means that goose can run smoothly on different systems without the need for Python to be installed, making it easier for anyone to start using it.
|
||||
|
||||
### 2. Contextual Memory
|
||||
|
||||
Goose will remember previous interactions to better understand ongoing projects. This means you won’t have to keep repeating yourself. Imagine having a conversation with someone who remembers every detail—this is the kind of support Goose aims to offer.
|
||||
goose will remember previous interactions to better understand ongoing projects. This means you won’t have to keep repeating yourself. Imagine having a conversation with someone who remembers every detail—this is the kind of support goose aims to offer.
|
||||
|
||||
### 3. Improved Plugin System
|
||||
|
||||
In Goose v1.0, the Goose toolkit system is being replaced with Extensions. Extensions are modular daemons that Goose can interact with dynamically. As a result, Goose will be able to support more complex plugins and integrations. This will make it easier to extend Goose with new features and functionality.
|
||||
In goose v1.0, the goose toolkit system is being replaced with Extensions. Extensions are modular daemons that goose can interact with dynamically. As a result, goose will be able to support more complex plugins and integrations. This will make it easier to extend goose with new features and functionality.
|
||||
|
||||
### 4. Headless mode
|
||||
|
||||
You can now run Goose in headless mode - this is useful for running Goose on servers or in environments where a graphical interface is not available.
|
||||
You can now run goose in headless mode - this is useful for running goose on servers or in environments where a graphical interface is not available.
|
||||
|
||||
```sh
|
||||
cargo run --bin goose -- run -i instructions.md
|
||||
```
|
||||
|
||||
### 5. Goose now has a GUI
|
||||
### 5. goose now has a GUI
|
||||
|
||||
Goose now has an electron-based GUI macOS application that provides and alternative to the CLI to interact with Goose and manage your projects.
|
||||
goose now has an electron-based GUI macOS application that provides and alternative to the CLI to interact with goose and manage your projects.
|
||||
|
||||
|
||||
|
||||
|
||||
### 6. Goose alignment with open protocols
|
||||
### 6. goose alignment with open protocols
|
||||
|
||||
Goose v1.0 Beta now uses a custom protocol, that is designed in parallel with [Anthropic’s Model Context Protocol](https://www.anthropic.com/news/model-context-protocol) (MCP) to communicate with Systems. This makes it possible for developers to create their own systems (e.g Jira, ) that Goose can integrate with.
|
||||
goose v1.0 Beta now uses a custom protocol, that is designed in parallel with [Anthropic’s Model Context Protocol](https://www.anthropic.com/news/model-context-protocol) (MCP) to communicate with Systems. This makes it possible for developers to create their own systems (e.g Jira, ) that Goose can integrate with.
|
||||
|
||||
Excited for many more feature updates and improvements? Stay tuned for more updates on Goose! Check out the [Goose repo](https://github.com/block/goose) and join our [Discord community](https://discord.gg/block-opensource).
|
||||
Excited for many more feature updates and improvements? Stay tuned for more updates on Goose! Check out the [goose repo](https://github.com/block/goose) and join our [Discord community](https://discord.gg/block-opensource).
|
||||
|
||||
|
||||
<head>
|
||||
|
|
|
|||
|
|
@ -19,30 +19,30 @@ We're in the early days of a new era in tech, one where companies are innovating
|
|||
|
||||
Anthropic is leading the charge with the [Model Context Protocol (MCP)](https://modelcontextprotocol.io), an open standard that enables large language model (LLM) applications to connect with external systems, providing the necessary context for more informed and relevant AI interactions.
|
||||
|
||||
This is a game changer for AI agents such as [Goose](https://block.github.io/goose/), which can perform tasks autonomously - a significant leap beyond chatbots that only provide step-by-step instructions. However, to unlock the full potential of these AI agents, we need a standard method for connecting them to external data sources. MCP provides this foundation.
|
||||
This is a game changer for AI agents such as [goose](https://block.github.io/goose/), which can perform tasks autonomously - a significant leap beyond chatbots that only provide step-by-step instructions. However, to unlock the full potential of these AI agents, we need a standard method for connecting them to external data sources. MCP provides this foundation.
|
||||
|
||||
With MCP's standardized APIs and endpoints, Goose can integrate seamlessly into your systems, enhancing its ability to perform complex tasks like debugging, writing code, and running commands directly in your environment.
|
||||
With MCP's standardized APIs and endpoints, goose can integrate seamlessly into your systems, enhancing its ability to perform complex tasks like debugging, writing code, and running commands directly in your environment.
|
||||
|
||||
|
||||
|
||||
|
||||
### What's Possible
|
||||
|
||||
Without MCP, every [Goose toolkit](https://block.github.io/goose/plugins/using-toolkits.html) developer would need to implement bespoke integrations with every system they need to connect to. Not only is this tedious and repetitive, but it delays the fun stuff.
|
||||
Without MCP, every [goose toolkit](https://block.github.io/goose/plugins/using-toolkits.html) developer would need to implement bespoke integrations with every system they need to connect to. Not only is this tedious and repetitive, but it delays the fun stuff.
|
||||
|
||||
Let's take a simple GitHub workflow, for example. Goose interacts directly with the GitHub API using custom scripts or configurations. Developers must configure Goose to authenticate with GitHub and specify endpoints for actions like fetching open pull requests or adding comments. Each integration requires manual setup and custom coding to handle authentication tokens, error handling, and API updates.
|
||||
Let's take a simple GitHub workflow, for example. goose interacts directly with the GitHub API using custom scripts or configurations. Developers must configure goose to authenticate with GitHub and specify endpoints for actions like fetching open pull requests or adding comments. Each integration requires manual setup and custom coding to handle authentication tokens, error handling, and API updates.
|
||||
|
||||
MCP simplifies the process by providing a standardized interface for accessing GitHub as a resource. Goose, acting as an [MCP client](https://modelcontextprotocol.io/clients), requests the necessary information (e.g., list of open pull requests) from an [MCP server](https://modelcontextprotocol.io/quickstart#general-architecture) configured to expose GitHub's capabilities. The MCP server handles authentication and communication with GitHub, abstracting away the complexity of API interactions. Goose can then focus on tasks like providing a detailed review comment or suggesting code changes.
|
||||
MCP simplifies the process by providing a standardized interface for accessing GitHub as a resource. goose, acting as an [MCP client](https://modelcontextprotocol.io/clients), requests the necessary information (e.g., list of open pull requests) from an [MCP server](https://modelcontextprotocol.io/quickstart#general-architecture) configured to expose GitHub's capabilities. The MCP server handles authentication and communication with GitHub, abstracting away the complexity of API interactions. goose can then focus on tasks like providing a detailed review comment or suggesting code changes.
|
||||
|
||||
### Join the Ecosystem
|
||||
|
||||
As MCP adoption expands, so does Goose’s potential to deliver even more powerful solutions for your organization. By [integrating Goose](https://block.github.io/goose/) into your workflows and [embracing MCP](https://modelcontextprotocol.io/introduction), you’re not just enhancing your own systems, you’re contributing to the growth of an ecosystem that makes AI tools more interoperable, efficient, and impactful.
|
||||
As MCP adoption expands, so does goose’s potential to deliver even more powerful solutions for your organization. By [integrating goose](https://block.github.io/goose/) into your workflows and [embracing MCP](https://modelcontextprotocol.io/introduction), you’re not just enhancing your own systems, you’re contributing to the growth of an ecosystem that makes AI tools more interoperable, efficient, and impactful.
|
||||
|
||||
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8" />
|
||||
<title>Connecting AI Agents to Your Systems with MCP</title>
|
||||
<meta name="description" content="Goose" />
|
||||
<meta name="description" content="goose" />
|
||||
<meta name="keywords" content="MCP, Anthropic, AI Open Standards" />
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
draft: false
|
||||
title: "Resolving CI Issues with Goose: A Practical Walkthrough"
|
||||
description: "Leverage Goose to simplify your CI debugging process, fetch detailed information about failed CI runs & annotations directly from GitHub, and even apply fixes directly."
|
||||
title: "Resolving CI Issues with goose: A Practical Walkthrough"
|
||||
description: "Leverage goose to simplify your CI debugging process, fetch detailed information about failed CI runs & annotations directly from GitHub, and even apply fixes directly."
|
||||
date: 2024-12-11
|
||||
authors:
|
||||
- dalton
|
||||
|
|
@ -9,12 +9,12 @@ authors:
|
|||
|
||||
|
||||
|
||||
Running into Continuous Integration (CI) failures in pull requests can be quite frustrating but they happen very often. In this post, we leverage the GitHub CLI (`gh`) using Goose to simplify your CI debugging process, fetch detailed information about failed CI runs and annotations directly from GitHub, and even apply fixes directly.
|
||||
Running into Continuous Integration (CI) failures in pull requests can be quite frustrating but they happen very often. In this post, we leverage the GitHub CLI (`gh`) using goose to simplify your CI debugging process, fetch detailed information about failed CI runs and annotations directly from GitHub, and even apply fixes directly.
|
||||
|
||||
<!-- truncate -->
|
||||
|
||||
:::warning Goose Beta Version
|
||||
This post was written about a beta version of Goose and the commands and flow may have changed.
|
||||
:::warning goose Beta Version
|
||||
This post was written about a beta version of goose and the commands and flow may have changed.
|
||||
:::
|
||||
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ Before diving in, ensure you have the necessary tools set up.
|
|||
|
||||
### 1. Install and Authenticate GitHub CLI (`gh`)
|
||||
|
||||
You'll need the [GitHub CLI](https://cli.github.com/) `gh` to enable Goose's access to CI check run details.
|
||||
You'll need the [GitHub CLI](https://cli.github.com/) `gh` to enable goose's access to CI check run details.
|
||||
|
||||
```bash
|
||||
brew install gh
|
||||
|
|
@ -34,8 +34,8 @@ gh auth login
|
|||
Follow the prompts to authenticate your account.
|
||||
|
||||
|
||||
### 2. Configure Goose
|
||||
Ensure Goose is configured and ready to interact with your repository and local tools. Specifically, you will need to configure a goose profile with the GitHub toolkit.
|
||||
### 2. Configure goose
|
||||
Ensure goose is configured and ready to interact with your repository and local tools. Specifically, you will need to configure a goose profile with the GitHub toolkit.
|
||||
|
||||
Update your `profiles.yaml` file in `~/.config/goose` with the necessary toolkits:
|
||||
|
||||
|
|
@ -56,13 +56,13 @@ Start a session with the profile:
|
|||
```bash
|
||||
goose session start --profile my-profile
|
||||
```
|
||||
If the profile’s toolkits are not correctly configured, Goose might fail to access `gh` commands.
|
||||
If the profile’s toolkits are not correctly configured, goose might fail to access `gh` commands.
|
||||
|
||||
## Resolving CI Failures with Goose
|
||||
Once everything is set up, we can now use Goose to tackle CI issues with the following steps:
|
||||
## Resolving CI Failures with goose
|
||||
Once everything is set up, we can now use goose to tackle CI issues with the following steps:
|
||||
|
||||
### Step 1: Fetch CI Failure Details
|
||||
Ask Goose to retrieve information about the CI failures for a specific PR.
|
||||
Ask goose to retrieve information about the CI failures for a specific PR.
|
||||
|
||||
**Example Request:**
|
||||
|
||||
|
|
@ -73,20 +73,20 @@ Can you tell me about the CI failures on PR #11111 in the organization/repo repo
|
|||
|
||||
You can access a check run ID by clicking on a PR’s checks tab and selecting a failure. The ID will be available in the URL.
|
||||
|
||||
**Goose's Workflow:**
|
||||
**goose's Workflow:**
|
||||
|
||||
Goose will use the `gh` CLI to check run information and provide a detailed summary of the issues. Goose uses the GitHub CLI to:
|
||||
goose will use the `gh` CLI to check run information and provide a detailed summary of the issues. goose uses the GitHub CLI to:
|
||||
|
||||
- Fetch details about failed CI runs, including logs and annotations.
|
||||
- Provide a clear and actionable summary of issues.
|
||||
|
||||
**Example Command Goose Runs:**
|
||||
**Example Command goose Runs:**
|
||||
|
||||
```curl
|
||||
gh api -H "Accept: application/vnd.github+json" /repos/<owner>/<repo>/check-runs/<check-run-id>/annotations
|
||||
```
|
||||
|
||||
**Example Goose Output:**
|
||||
**Example goose Output:**
|
||||
```mathematica
|
||||
Here are the details for Check Run ID 123456:
|
||||
|
||||
|
|
@ -110,8 +110,8 @@ Here are the details for Check Run ID 123456:
|
|||
Line: 98
|
||||
Error: Type mismatch in returned value. Expected 'String', found 'Int'.
|
||||
```
|
||||
### Step 2: Request Fixes from Goose
|
||||
Once Goose provides the failure details, ask it to resolve the issues directly.
|
||||
### Step 2: Request Fixes from goose
|
||||
Once goose provides the failure details, ask it to resolve the issues directly.
|
||||
|
||||
Example Request:
|
||||
|
||||
|
|
@ -119,13 +119,13 @@ Example Request:
|
|||
Can you fix these issues and stage the changes so I can review them? Do not add unnecessary code comments.
|
||||
```
|
||||
|
||||
**What Goose Does:**
|
||||
**What goose Does:**
|
||||
|
||||
- Applies fixes based on error messages.
|
||||
- Stages changes for review.
|
||||
|
||||
|
||||
**Example Goose Response:**
|
||||
**Example goose Response:**
|
||||
```markdown
|
||||
I have fixed the following files and staged them:
|
||||
|
||||
|
|
@ -148,26 +148,26 @@ Carefully review the staged changes to ensure they address the issues correctly
|
|||
|
||||
If needed, clean up or re-stage the changes before committing.
|
||||
|
||||
## Benefits of Using Goose
|
||||
Using Goose to resolve CI issues streamlines your workflow by:
|
||||
## Benefits of Using goose
|
||||
Using goose to resolve CI issues streamlines your workflow by:
|
||||
|
||||
- identifying issues and applying fixes with minimal manual effort.
|
||||
- integrating with tools like the GitHub CLI to validate changes.
|
||||
- handling repetitive CI debugging tasks while you focus on code quality.
|
||||
|
||||
Goose allows you to resolve CI failures efficiently, ensuring confidence in your workflow while reducing the effort required for debugging and testing.
|
||||
goose allows you to resolve CI failures efficiently, ensuring confidence in your workflow while reducing the effort required for debugging and testing.
|
||||
|
||||
Try it out, and let Goose handle the heavy lifting of CI debugging for you!
|
||||
Try it out, and let goose handle the heavy lifting of CI debugging for you!
|
||||
|
||||
<head>
|
||||
<meta property="og:title" content="Resolving CI Issues with Goose: A Practical Walkthrough" />
|
||||
<meta property="og:title" content="Resolving CI Issues with goose: A Practical Walkthrough" />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://block.github.io/goose/blog/2024/12/11/resolving-ci-issues-with-goose-a-practical-walkthrough" />
|
||||
<meta property="og:description" content="Leverage Goose to simplify your CI debugging process, fetch detailed information about failed CI runs & annotations directly from GitHub, and even apply fixes directly." />
|
||||
<meta property="og:description" content="Leverage goose to simplify your CI debugging process, fetch detailed information about failed CI runs & annotations directly from GitHub, and even apply fixes directly." />
|
||||
<meta property="og:image" content="https://block.github.io/goose/assets/images/goose-github-ci-30930008ab57b0aebae15a03c73a12b5.png" />
|
||||
<meta name="twitter:card" content="summary_large_image" />
|
||||
<meta property="twitter:domain" content="block.github.io/goose" />
|
||||
<meta name="twitter:title" content="Resolving CI Issues with Goose: A Practical Walkthrough" />
|
||||
<meta name="twitter:description" content="Leverage Goose to simplify your CI debugging process, fetch detailed information about failed CI runs & annotations directly from GitHub, and even apply fixes directly." />
|
||||
<meta name="twitter:title" content="Resolving CI Issues with goose: A Practical Walkthrough" />
|
||||
<meta name="twitter:description" content="Leverage goose to simplify your CI debugging process, fetch detailed information about failed CI runs & annotations directly from GitHub, and even apply fixes directly." />
|
||||
<meta name="twitter:image" content="https://block.github.io/goose/assets/images/goose-github-ci-30930008ab57b0aebae15a03c73a12b5.png" />
|
||||
</head>
|
||||
|
|
|
|||
|
|
@ -9,29 +9,29 @@ authors:
|
|||
|
||||
We are thrilled to announce **codename goose**, your on-machine, open source AI agent built to automate your tasks.
|
||||
|
||||
Powered by your choice of [large language models (LLMs)](/docs/getting-started/providers), a user-friendly desktop interface and CLI, and [extensions](/docs/getting-started/using-extensions) that integrate with your existing tools and applications, Goose is designed to enhance your productivity and workflow.
|
||||
Powered by your choice of [large language models (LLMs)](/docs/getting-started/providers), a user-friendly desktop interface and CLI, and [extensions](/docs/getting-started/using-extensions) that integrate with your existing tools and applications, goose is designed to enhance your productivity and workflow.
|
||||
|
||||
<!--truncate-->
|
||||
|
||||
|
||||
You can think of Goose as an assistant that is ready to take your instructions, and do the work for you.
|
||||
You can think of goose as an assistant that is ready to take your instructions, and do the work for you.
|
||||
|
||||
While Goose's first use cases are engineering focused, the community has been exploring other non-engineering use cases for Goose as well. And it goes without saying, Goose is [open source](https://github.com/block/goose) 🎉.
|
||||
While goose's first use cases are engineering focused, the community has been exploring other non-engineering use cases for goose as well. And it goes without saying, goose is [open source](https://github.com/block/goose) 🎉.
|
||||
|
||||
|
||||
## How Goose Works
|
||||
## How goose Works
|
||||
|
||||
Goose operates as an intelligent, autonomous agent capable of handling complex tasks through a well-orchestrated coordination of its core features:
|
||||
goose operates as an intelligent, autonomous agent capable of handling complex tasks through a well-orchestrated coordination of its core features:
|
||||
|
||||
- **Using Extensions**: [Extensions](/docs/getting-started/using-extensions) are key to Goose’s adaptability, providing you the ability to connect with applications and tools that you already use. Whether it’s connecting to GitHub, accessing Google Drive or integrating with JetBrains IDEs, the possibilities are extensive. Some of these extensions have been curated in the [extensions][extensions-directory] directory. Goose extensions are built on the [Model Context Protocol (MCP)](https://www.anthropic.com/news/model-context-protocol) - enabling you to build or bring your own custom integrations to Goose.
|
||||
- **Using Extensions**: [Extensions](/docs/getting-started/using-extensions) are key to goose’s adaptability, providing you the ability to connect with applications and tools that you already use. Whether it’s connecting to GitHub, accessing Google Drive or integrating with JetBrains IDEs, the possibilities are extensive. Some of these extensions have been curated in the [extensions][extensions-directory] directory. goose extensions are built on the [Model Context Protocol (MCP)](https://www.anthropic.com/news/model-context-protocol) - enabling you to build or bring your own custom integrations to goose.
|
||||
|
||||
- **LLM Providers**: Goose is compatible with a wide range of [LLM providers](/docs/getting-started/providers), allowing you to choose and integrate your preferred model.
|
||||
- **LLM Providers**: goose is compatible with a wide range of [LLM providers](/docs/getting-started/providers), allowing you to choose and integrate your preferred model.
|
||||
|
||||
- **CLI and Desktop Support**: You can run Goose as a desktop app or through the command-line interface (CLI) using the same configurations across both.
|
||||
- **CLI and Desktop Support**: You can run goose as a desktop app or through the command-line interface (CLI) using the same configurations across both.
|
||||
|
||||
## Goose in Action
|
||||
## goose in Action
|
||||
|
||||
Goose is able to handle a wide range of tasks, from simple to complex, across various engineering domains. Here are some examples of tasks that Goose has helped people with:
|
||||
goose is able to handle a wide range of tasks, from simple to complex, across various engineering domains. Here are some examples of tasks that goose has helped people with:
|
||||
|
||||
- Conduct code migrations such as Ember to React, Ruby to Kotlin, Prefect-1 to Prefect-2 etc.
|
||||
- Dive into a new project in an unfamiliar coding language
|
||||
|
|
@ -45,10 +45,10 @@ Goose is able to handle a wide range of tasks, from simple to complex, across va
|
|||
|
||||
## Getting Started
|
||||
|
||||
You can get started using Goose right away! Check out our [Quickstart](/docs/quickstart).
|
||||
You can get started using goose right away! Check out our [Quickstart](/docs/quickstart).
|
||||
|
||||
|
||||
## Join the Goose Community
|
||||
## Join the goose Community
|
||||
|
||||
Excited for upcoming features and events? Be sure to connect with us!
|
||||
|
||||
|
|
|
|||
|
|
@ -116,21 +116,21 @@ Without tool calling, LLMs would only guess answers based on their training data
|
|||
|
||||
It's worth noting that not all agents are the same when it comes to tool access. Most proprietary agents are tightly scoped to a specific LLM and a predefined set of tools, as companies build agents tailored for their own applications.
|
||||
|
||||
Other agents, like Goose, are more extensible, allowing users to configure it with the LLM of their choice, as well as add tools for various APIs, databases, and even [local environments like IDEs](/docs/mcp/jetbrains-mcp). However, for agents to scale across different tools and systems without requiring custom integrations for each one, they need a standardized way to discover, call, and manage tools. This is exactly what the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) provides.
|
||||
Other agents, like goose, are more extensible, allowing users to configure it with the LLM of their choice, as well as add tools for various APIs, databases, and even [local environments like IDEs](/docs/mcp/jetbrains-mcp). However, for agents to scale across different tools and systems without requiring custom integrations for each one, they need a standardized way to discover, call, and manage tools. This is exactly what the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) provides.
|
||||
|
||||
## MCP Ecosystem
|
||||
|
||||
Traditional AI integrations require custom API calls for every system, making scaling difficult. MCP solves this by providing an open, universal protocol for agents to communicate with external systems dynamically.
|
||||
|
||||
With MCP, an agent like Goose can:
|
||||
With MCP, an agent like goose can:
|
||||
|
||||
* connect to any API without a developer writing manual integration code
|
||||
* integrate with cloud services, dev tools, databases, and enterprise systems
|
||||
* retrieve and store context to enhance reasoning
|
||||
|
||||
At the time of this writing, there are more than [1000 MCP servers](https://www.pulsemcp.com/servers) (systems that expose tools) that any MCP-enabled AI agent like Goose can connect to! These MCP servers act as bridges between agents and external systems, enabling access to APIs, databases, and development environments. Some were developed by the official API providers, while the vast majority were developed by community members. Because MCP is an open standard, anyone can build an MCP server for any resource. This greatly increases the possibilities of AI agents!
|
||||
At the time of this writing, there are more than [1000 MCP servers](https://www.pulsemcp.com/servers) (systems that expose tools) that any MCP-enabled AI agent like goose can connect to! These MCP servers act as bridges between agents and external systems, enabling access to APIs, databases, and development environments. Some were developed by the official API providers, while the vast majority were developed by community members. Because MCP is an open standard, anyone can build an MCP server for any resource. This greatly increases the possibilities of AI agents!
|
||||
|
||||
For example, let's say I want Goose to develop a new web app for me in my WebStorm IDE based on a Figma design and then commit the code to a new repo in GitHub. I can add the following MCP Servers as Goose extensions to give it all of these capabilities:
|
||||
For example, let's say I want goose to develop a new web app for me in my WebStorm IDE based on a Figma design and then commit the code to a new repo in GitHub. I can add the following MCP Servers as goose extensions to give it all of these capabilities:
|
||||
|
||||
* [Figma](/docs/mcp/figma-mcp)
|
||||
* [JetBrains](/docs/mcp/jetbrains-mcp)
|
||||
|
|
@ -143,7 +143,7 @@ With this, I can prompt my AI agent in natural language and it'll take care of t
|
|||
Pretty powerful, right?!
|
||||
|
||||
## Get Started with AI Agents
|
||||
Hopefully this has provided clear insight into what are AI agents, how they work, and what they can enable for you. [Goose](/docs/getting-started/installation) is free and open source and you can add as many [extensions](/docs/getting-started/using-extensions#adding-extensions) as you desire. This is a great way to get started with AI agents and see how they can automate tasks in your workflow to make you more efficient.
|
||||
Hopefully this has provided clear insight into what are AI agents, how they work, and what they can enable for you. [goose](/docs/getting-started/installation) is free and open source and you can add as many [extensions](/docs/getting-started/using-extensions#adding-extensions) as you desire. This is a great way to get started with AI agents and see how they can automate tasks in your workflow to make you more efficient.
|
||||
|
||||
|
||||
<head>
|
||||
|
|
|
|||
|
|
@ -1,45 +1,45 @@
|
|||
---
|
||||
title: Let A Team of AI Agents Do It For You
|
||||
description: Community Spotlight on Cliff Hall's GooseTeam MCP server.
|
||||
description: Community Spotlight on Cliff Hall's gooseTeam MCP server.
|
||||
authors:
|
||||
- tania
|
||||
---
|
||||
|
||||
|
||||
|
||||
During our [previous livestream](https://youtu.be/9tq-QUnE29U), Aaron Goldsmith, Infrastructure Operations Engineer at Cash App, showed a team of Goose AI agents collaborating in real time to create a website. Our community loved it so much, Cliff Hall was inspired to iterate on that idea and create a GooseTeam MCP server.
|
||||
During our [previous livestream](https://youtu.be/9tq-QUnE29U), Aaron Goldsmith, Infrastructure Operations Engineer at Cash App, showed a team of goose AI agents collaborating in real time to create a website. Our community loved it so much, Cliff Hall was inspired to iterate on that idea and create a gooseTeam MCP server.
|
||||
|
||||
<!--truncate-->
|
||||
|
||||
## The Original Protocol
|
||||
|
||||
Aaron Goldsmith made an AI agent team consisting of multiple Goose instances a reality with his lightweight [Agent Communication Protocol](https://gist.github.com/AaronGoldsmith/114c439ae67e4f4c47cc33e829c82fac). With it, each Goose agent enters the chat, gets assigned a role (e.g. Project Coordinator, Researcher, Web Developer), and works on its part of a given task. The protocol specifies instructions guiding how the agents should talk and behave, allowing multiple Goose agents to collaborate. It also specifies that communication between the agents should be done via a Python-based websocket server with text/markdown .
|
||||
Aaron Goldsmith made an AI agent team consisting of multiple goose instances a reality with his lightweight [Agent Communication Protocol](https://gist.github.com/AaronGoldsmith/114c439ae67e4f4c47cc33e829c82fac). With it, each goose agent enters the chat, gets assigned a role (e.g. Project Coordinator, Researcher, Web Developer), and works on its part of a given task. The protocol specifies instructions guiding how the agents should talk and behave, allowing multiple goose agents to collaborate. It also specifies that communication between the agents should be done via a Python-based websocket server with text/markdown .
|
||||
|
||||
## GooseTeam MCP Server
|
||||
## gooseTeam MCP Server
|
||||
|
||||
Introducing [GooseTeam](https://github.com/cliffhall/GooseTeam), created by Software Architect and community member, Cliff Hall. GooseTeam takes Aaron's protocol and iterates on it into an MCP server and collaboration protocol for Goose Agents. With features like task management, message storage, and agent waiting, you can have an entire team of Goose agents work together on a task or project for you.
|
||||
Introducing [gooseTeam](https://github.com/cliffhall/gooseTeam), created by Software Architect and community member, Cliff Hall. gooseTeam takes Aaron's protocol and iterates on it into an MCP server and collaboration protocol for goose Agents. With features like task management, message storage, and agent waiting, you can have an entire team of goose agents work together on a task or project for you.
|
||||
|
||||
A Goose agent with the Project Coordinator role will assign roles to other agents, your connected agents will send messages that can retrieved at any time, and your team of agents will connect to the same MCP server to collaborate together.
|
||||
A goose agent with the Project Coordinator role will assign roles to other agents, your connected agents will send messages that can retrieved at any time, and your team of agents will connect to the same MCP server to collaborate together.
|
||||
|
||||
|
||||
|
||||
|
||||
## A New Way to Goose
|
||||
## A New Way to goose
|
||||
|
||||
Working with a team of AI agents on a task is a game changer. Instead of getting confused as to how to improve your prompt engineering on your own or work across sessions manually, tools like Cliff's GooseTeam or Aaron's Agent Communication Protocol help us make sure AI agents like Goose are doing the work for us as efficiently as possible. The possibilities feel endless!
|
||||
Working with a team of AI agents on a task is a game changer. Instead of getting confused as to how to improve your prompt engineering on your own or work across sessions manually, tools like Cliff's gooseTeam or Aaron's Agent Communication Protocol help us make sure AI agents like goose are doing the work for us as efficiently as possible. The possibilities feel endless!
|
||||
|
||||
## Get Your Contribution Featured
|
||||
Hopefully this contribution inspired you as much as it inspired our community. If you have a Goose contribution or project you'd like to share with our community, join our [Discord](https://discord.gg/block-opensource) and share your work in the **#share-your-work** channel. You may just be featured on our livestream or get a cool prize. 👀 You can also star Goose on GitHub or follow us on social media so you never miss an update from us. Until next time!
|
||||
Hopefully this contribution inspired you as much as it inspired our community. If you have a goose contribution or project you'd like to share with our community, join our [Discord](https://discord.gg/block-opensource) and share your work in the **#share-your-work** channel. You may just be featured on our livestream or get a cool prize. 👀 You can also star goose on GitHub or follow us on social media so you never miss an update from us. Until next time!
|
||||
|
||||
|
||||
<head>
|
||||
<meta property="og:title" content="Let A Team of AI Agents Do It For You" />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://block.github.io/goose/blog/2025/02/17/gooseteam-mcp" />
|
||||
<meta property="og:description" content="Community Spotlight on Cliff Hall's GooseTeam MCP server." />
|
||||
<meta property="og:description" content="Community Spotlight on Cliff Hall's gooseTeam MCP server." />
|
||||
<meta property="og:image" content="https://block.github.io/goose/assets/images/gooseteam-mcp-082fa2890c313519c2a1637ca979c219.png" />
|
||||
<meta name="twitter:card" content="summary_large_image" />
|
||||
<meta property="twitter:domain" content="block.github.io/goose" />
|
||||
<meta name="twitter:title" content="Let A Team of AI Agents Do It For You" />
|
||||
<meta name="twitter:description" content="Community Spotlight on Cliff Hall's GooseTeam MCP server." />
|
||||
<meta name="twitter:description" content="Community Spotlight on Cliff Hall's gooseTeam MCP server." />
|
||||
<meta name="twitter:image" content="https://block.github.io/goose/assets/images/gooseteam-mcp-082fa2890c313519c2a1637ca979c219.png" />
|
||||
</head>
|
||||
|
|
@ -1,44 +1,44 @@
|
|||
---
|
||||
title: 6 Essential Tips for Working with Goose
|
||||
description: Practical tips to help you use Goose more effectively and efficiently.
|
||||
title: 6 Essential Tips for Working with goose
|
||||
description: Practical tips to help you use goose more effectively and efficiently.
|
||||
authors:
|
||||
- angie
|
||||
---
|
||||
|
||||
|
||||
|
||||
Working with AI agents can sometimes feel unpredictable. After using Goose extensively for the last few months, I've compiled a few key tips that will help you get the most out of this tool. No matter your workflow, these guidelines will help you work more efficiently with Goose.
|
||||
Working with AI agents can sometimes feel unpredictable. After using goose extensively for the last few months, I've compiled a few key tips that will help you get the most out of this tool. No matter your workflow, these guidelines will help you work more efficiently with goose.
|
||||
|
||||
|
||||
<!--truncate-->
|
||||
|
||||
## 1. Keep Sessions Focused and Short
|
||||
|
||||
One of the most common mistakes users make is trying to accomplish too much in a single session. While it might seem efficient to keep the conversation going, longer sessions can actually hinder Goose's performance.
|
||||
One of the most common mistakes users make is trying to accomplish too much in a single session. While it might seem efficient to keep the conversation going, longer sessions can actually hinder goose's performance.
|
||||
|
||||
Every message adds to the context window, which is the amount of conversation history Goose can retain at any given time. This history is made up of tokens, the individual pieces of text (words or even parts of words) that Goose processes to generate responses. More tokens don’t just increase processing time, they also contribute to LLM usage costs. And once the context window fills up, older messages get pushed out, which can lead to loss of important details or unexpected behavior.
|
||||
Every message adds to the context window, which is the amount of conversation history goose can retain at any given time. This history is made up of tokens, the individual pieces of text (words or even parts of words) that goose processes to generate responses. More tokens don’t just increase processing time, they also contribute to LLM usage costs. And once the context window fills up, older messages get pushed out, which can lead to loss of important details or unexpected behavior.
|
||||
|
||||
Think of it like keeping too many browser tabs open. Eventually, it impacts performance. Instead, start fresh sessions for distinct tasks. Don't worry about losing context; that's exactly what the [Memory extension](/docs/mcp/memory-mcp) is for. Keeping sessions focused and concise ensures more accurate, relevant responses while also keeping your LLM costs under control.
|
||||
|
||||
|
||||
## 2. Minimize Active Extensions
|
||||
|
||||
When it comes to Goose extensions, less is often more. It's tempting to enable [every available extension](https://www.pulsemcp.com/servers) just in case (I'm guilty of this!), but this approach can be counterproductive. Each active extension adds to the system prompt, increasing complexity and making Goose work harder to decide which tools to use.
|
||||
When it comes to goose extensions, less is often more. It's tempting to enable [every available extension](https://www.pulsemcp.com/servers) just in case (I'm guilty of this!), but this approach can be counterproductive. Each active extension adds to the system prompt, increasing complexity and making goose work harder to decide which tools to use.
|
||||
|
||||
Consider this: if you're cooking in a kitchen, having every possible utensil and appliance out on the counter doesn't make you a better chef. It just creates clutter and confusion. The same principle applies here.
|
||||
|
||||
Go ahead and install any extensions that interest you, but [keep them disabled](/docs/getting-started/using-extensions#enablingdisabling-extensions) until you need them. Start with the built-in [Developer extension](/docs/mcp/developer-mcp) enabled, which is surprisingly powerful on its own, and only enable others when you need their specific capabilities. This leads to faster responses, lower token usage, and often more focused solutions.
|
||||
|
||||
:::tip Bonus Tip
|
||||
Before starting a complex task, ask Goose about its current capabilities. A simple prompt like "Do you have tools available to work with [specific technology/service]?" can save time and prevent false starts. Goose can tell you whether it has the necessary tools for your task, and if not, suggest which extensions you might need to enable. This quick check ensures you have the right tools ready before diving in too deep.
|
||||
Before starting a complex task, ask goose about its current capabilities. A simple prompt like "Do you have tools available to work with [specific technology/service]?" can save time and prevent false starts. goose can tell you whether it has the necessary tools for your task, and if not, suggest which extensions you might need to enable. This quick check ensures you have the right tools ready before diving in too deep.
|
||||
:::
|
||||
|
||||
## 3. Teach Goose with .goosehints Files
|
||||
## 3. Teach goose with .goosehints Files
|
||||
|
||||
|
||||
One of Goose's most powerful features is its ability to understand context through [.goosehints](/docs/guides/using-goosehints) files, acting like a "README for AI". These hints can be set at both the project and global levels to guide Goose’s responses.
|
||||
One of goose's most powerful features is its ability to understand context through [.goosehints](/docs/guides/using-goosehints) files, acting like a "README for AI". These hints can be set at both the project and global levels to guide goose’s responses.
|
||||
|
||||
At the project level, placing .goosehints files in your directory helps Goose understand your structure, conventions, and special considerations. You can even use multiple files - one at the root for overall guidance and others in specific directories for more granular instructions (e.g., frontend styling conventions).
|
||||
At the project level, placing .goosehints files in your directory helps goose understand your structure, conventions, and special considerations. You can even use multiple files - one at the root for overall guidance and others in specific directories for more granular instructions (e.g., frontend styling conventions).
|
||||
|
||||
Beyond projects, global .goosehints files (`~/.config/goose/.goosehints`) apply across all sessions, making them perfect for things like:
|
||||
|
||||
|
|
@ -50,29 +50,29 @@ Beyond projects, global .goosehints files (`~/.config/goose/.goosehints`) apply
|
|||
|
||||
## 4. Choose the Right Mode for Your Workflow
|
||||
|
||||
Goose offers [different modes](/docs/guides/goose-permissions) that determine how much autonomy it has when modifying files, using extensions, and performing automated actions.
|
||||
goose offers [different modes](/docs/guides/goose-permissions) that determine how much autonomy it has when modifying files, using extensions, and performing automated actions.
|
||||
|
||||
* ⚡️ **Auto Mode (Default):** Goose can modify, create, and delete files, as well as use extensions, without requiring approval. Best for users who want seamless automation.
|
||||
* ⚡️ **Auto Mode (Default):** goose can modify, create, and delete files, as well as use extensions, without requiring approval. Best for users who want seamless automation.
|
||||
|
||||
* ✅ **Approve Mode:** Goose asks for confirmation before making changes. With [Smart Approve](/docs/guides/goose-permissions#permission-modes) enabled, it evaluates risk levels and prompts for high-risk actions while executing safe ones automatically.
|
||||
* ✅ **Approve Mode:** goose asks for confirmation before making changes. With [Smart Approve](/docs/guides/goose-permissions#permission-modes) enabled, it evaluates risk levels and prompts for high-risk actions while executing safe ones automatically.
|
||||
|
||||
* 💬 **Chat Mode:** Goose operates in chat-only mode, without modifying files or using extensions. Ideal for users who want AI assistance without automation.
|
||||
* 💬 **Chat Mode:** goose operates in chat-only mode, without modifying files or using extensions. Ideal for users who want AI assistance without automation.
|
||||
|
||||
If you’re new to Goose or working on a critical project, Approve Mode offers a great balance of automation and oversight. For hands-free workflows, Auto Mode keeps things moving, while Chat Mode is perfect for brainstorming and general AI assistance.
|
||||
If you’re new to goose or working on a critical project, Approve Mode offers a great balance of automation and oversight. For hands-free workflows, Auto Mode keeps things moving, while Chat Mode is perfect for brainstorming and general AI assistance.
|
||||
|
||||
## 5. Guide Goose with Step-by-Step Execution
|
||||
## 5. Guide goose with Step-by-Step Execution
|
||||
|
||||
Complex tasks are best handled in stages, and Goose excels when you allow it to break problems into manageable steps. Instead of expecting an instant solution, ask Goose to generate a step-by-step plan first. Review the plan to ensure it aligns with your goals, then let Goose execute each step in sequence.
|
||||
Complex tasks are best handled in stages, and goose excels when you allow it to break problems into manageable steps. Instead of expecting an instant solution, ask goose to generate a step-by-step plan first. Review the plan to ensure it aligns with your goals, then let goose execute each step in sequence.
|
||||
|
||||
This structured approach not only improves accuracy but also gives you more control over the process. You can pause, adjust, or refine each step as needed, giving you more control while ensuring better results.
|
||||
|
||||
## 6. Refine and Iterate for Better Responses
|
||||
|
||||
Goose is powerful, but like any AI, it sometimes needs a second pass to get things right. If you don’t get the response you need, try refining your prompt or asking Goose to adjust its answer.
|
||||
goose is powerful, but like any AI, it sometimes needs a second pass to get things right. If you don’t get the response you need, try refining your prompt or asking goose to adjust its answer.
|
||||
|
||||
Good iteration techniques include:
|
||||
|
||||
* Asking Goose to explain its reasoning before taking action
|
||||
* Asking goose to explain its reasoning before taking action
|
||||
* Requesting alternative solutions to compare different approaches
|
||||
* Asking for a step-by-step breakdown of its thought process
|
||||
* Rewording prompts to add more detail or constraints
|
||||
|
|
@ -81,17 +81,17 @@ For example, instead of asking, "Help me debug this error," try, "I’m getting
|
|||
|
||||
---
|
||||
|
||||
By following these tips, you'll be able to work more effectively with Goose, getting better results while using fewer resources. Remember, the goal is to solve problems efficiently and effectively. Whether you're writing code, automating tasks, or managing complex projects, these guidelines will help you make the most of what Goose has to offer.
|
||||
By following these tips, you'll be able to work more effectively with goose, getting better results while using fewer resources. Remember, the goal is to solve problems efficiently and effectively. Whether you're writing code, automating tasks, or managing complex projects, these guidelines will help you make the most of what goose has to offer.
|
||||
|
||||
<head>
|
||||
<meta property="og:title" content="6 Essential Tips for Working with Goose" />
|
||||
<meta property="og:title" content="6 Essential Tips for Working with goose" />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://block.github.io/goose/blog/2025/03/06/goose-tips" />
|
||||
<meta property="og:description" content="Practical tips to help you use Goose more effectively and efficiently." />
|
||||
<meta property="og:description" content="Practical tips to help you use goose more effectively and efficiently." />
|
||||
<meta property="og:image" content="https://block.github.io/goose/assets/images/goose-tips-4add28cc7201737dfb468ad11980f070.png" />
|
||||
<meta name="twitter:card" content="summary_large_image" />
|
||||
<meta property="twitter:domain" content="block.github.io/goose" />
|
||||
<meta name="twitter:title" content="6 Essential Tips for Working with Goose" />
|
||||
<meta name="twitter:description" content="Practical tips to help you use Goose more effectively and efficiently." />
|
||||
<meta name="twitter:title" content="6 Essential Tips for Working with goose" />
|
||||
<meta name="twitter:description" content="Practical tips to help you use goose more effectively and efficiently." />
|
||||
<meta name="twitter:image" content="https://block.github.io/goose/assets/images/goose-tips-4add28cc7201737dfb468ad11980f070.png" />
|
||||
</head>
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "Automating Phone Calls with Goose"
|
||||
description: Practical tips to help you use Goose more effectively and efficiently.
|
||||
title: "Automating Phone Calls with goose"
|
||||
description: Practical tips to help you use goose more effectively and efficiently.
|
||||
authors:
|
||||
- angie
|
||||
---
|
||||
|
|
@ -11,19 +11,19 @@ authors:
|
|||
|
||||
</div>
|
||||
|
||||
In the latest episode of [Wild Goose Case](https://www.youtube.com/playlist?list=PLyMFt_U2IX4uMW9kpE1FENQUyIgLuUnWD), hosts [Ebony Louis](https://www.linkedin.com/in/ebonylouis/) and [Ace Abati](https://www.linkedin.com/in/acekyd/) explored a fascinating new way to extend Goose’s automation capabilities by integrating with [VOYP](https://voyp.app/), an AI-powered system that makes phone calls. Their guest, [Paulo Taylor](https://www.linkedin.com/in/paulotaylor/), a technology veteran with over 35 years of experience, walked through how developers can use Goose to trigger and manage phone-based interactions through VOYP.
|
||||
In the latest episode of [Wild goose Case](https://www.youtube.com/playlist?list=PLyMFt_U2IX4uMW9kpE1FENQUyIgLuUnWD), hosts [Ebony Louis](https://www.linkedin.com/in/ebonylouis/) and [Ace Abati](https://www.linkedin.com/in/acekyd/) explored a fascinating new way to extend goose’s automation capabilities by integrating with [VOYP](https://voyp.app/), an AI-powered system that makes phone calls. Their guest, [Paulo Taylor](https://www.linkedin.com/in/paulotaylor/), a technology veteran with over 35 years of experience, walked through how developers can use goose to trigger and manage phone-based interactions through VOYP.
|
||||
|
||||
<!--truncate-->
|
||||
|
||||
# Expanding Goose’s Reach with AI-Powered Calls
|
||||
# Expanding goose’s Reach with AI-Powered Calls
|
||||
|
||||
Goose is already known for automating tasks, but you can extend that automation beyond the screen. With the [VOYP Goose Extension](goose://extension?cmd=npx&arg=-y&arg=voyp-mcp&id=voyp&name=VOYP&description=Automated%20Phone%20Calling&env=VOYP_API_KEY%3DVOYP%20API%20key), you can automate phone calls to retrieve information, handle customer interactions, or even assist with accessibility needs.
|
||||
goose is already known for automating tasks, but you can extend that automation beyond the screen. With the [VOYP Goose Extension](goose://extension?cmd=npx&arg=-y&arg=voyp-mcp&id=voyp&name=VOYP&description=Automated%20Phone%20Calling&env=VOYP_API_KEY%3DVOYP%20API%20key), you can automate phone calls to retrieve information, handle customer interactions, or even assist with accessibility needs.
|
||||
|
||||
VOYP functions as an AI call agent, using LLMs and Text-to-Speech (TTS) technology to conduct conversations over the phone. This means you can trigger phone interactions directly from Goose sessions, enabling real-world automation beyond traditional interfaces.
|
||||
VOYP functions as an AI call agent, using LLMs and Text-to-Speech (TTS) technology to conduct conversations over the phone. This means you can trigger phone interactions directly from goose sessions, enabling real-world automation beyond traditional interfaces.
|
||||
|
||||
# How It Works
|
||||
|
||||
Under the hood, VOYP utilizes multiple telecom providers to optimize call costs. It supports various LLMs and TTS providers, giving users flexibility in how they configure their AI caller. The integration with Goose is made possible through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/), which allows Goose to communicate seamlessly with VOYP and other AI-driven tools.
|
||||
Under the hood, VOYP utilizes multiple telecom providers to optimize call costs. It supports various LLMs and TTS providers, giving users flexibility in how they configure their AI caller. The integration with goose is made possible through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/), which allows goose to communicate seamlessly with VOYP and other AI-driven tools.
|
||||
|
||||
# Live Demo: AI Calls in Action
|
||||
During the livestream, Paulo demonstrated VOYP’s capabilities with a series of engaging examples. One highlight was a playful experiment where the AI made a phone call to tell a goose-themed joke.
|
||||
|
|
@ -32,18 +32,18 @@ During the livestream, Paulo demonstrated VOYP’s capabilities with a series of
|
|||
|
||||
In [another demo](https://www.youtube.com/live/g_F1u6aqohk?t=1515), Paulo had VOYP engage in a conversation with ChatGPT’s phone service about time travel, showing how fluid and adaptable the AI’s responses can be. He also walked through VOYP's real-time conversation monitoring dashboard, which provides a transparent look at how the AI processes and responds during calls.
|
||||
|
||||
# Getting Started with Goose and VOYP
|
||||
For those eager to experiment with [VOYP](https://github.com/paulotaylor/voyp-mcp), sign up on the [VOYP website](https://voyp.app/) to create an account and obtain an API key. While calls require credits, new users receive 20 free credits for testing. The cost per call varies by region, with U.S.-based calls being the most affordable at approximately five credits per minute. To integrate VOYP with Goose, [install the VOYP extension](goose://extension?cmd=npx&arg=-y&arg=voyp-mcp&id=voyp&name=VOYP&description=Automated%20Phone%20Calling&env=VOYP_API_KEY%3DVOYP%20API%20key).
|
||||
# Getting Started with goose and VOYP
|
||||
For those eager to experiment with [VOYP](https://github.com/paulotaylor/voyp-mcp), sign up on the [VOYP website](https://voyp.app/) to create an account and obtain an API key. While calls require credits, new users receive 20 free credits for testing. The cost per call varies by region, with U.S.-based calls being the most affordable at approximately five credits per minute. To integrate VOYP with goose, [install the VOYP extension](goose://extension?cmd=npx&arg=-y&arg=voyp-mcp&id=voyp&name=VOYP&description=Automated%20Phone%20Calling&env=VOYP_API_KEY%3DVOYP%20API%20key).
|
||||
|
||||
<head>
|
||||
<meta property="og:title" content="Wild Goose Case: Automating Phone Calls with Goose and VOYP" />
|
||||
<meta property="og:title" content="Wild goose Case: Automating Phone Calls with goose and VOYP" />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://block.github.io/goose/blog/2025/03/06/goose-tips" />
|
||||
<meta property="og:description" content="Give Goose the ability to make phone calls with the VOYP extension." />
|
||||
<meta property="og:description" content="Give goose the ability to make phone calls with the VOYP extension." />
|
||||
<meta property="og:image" content="https://block.github.io/goose/assets/images/goose-voyp-215f3391cfbe2132542a2be63db84999.png" />
|
||||
<meta name="twitter:card" content="summary_large_image" />
|
||||
<meta property="twitter:domain" content="block.github.io/goose" />
|
||||
<meta name="twitter:title" content="Wild Goose Case: Automating Phone Calls with Goose and VOYP" />
|
||||
<meta name="twitter:description" content="Give Goose the ability to make phone calls with the VOYP extension." />
|
||||
<meta name="twitter:title" content="Wild goose Case: Automating Phone Calls with goose and VOYP" />
|
||||
<meta name="twitter:description" content="Give goose the ability to make phone calls with the VOYP extension." />
|
||||
<meta name="twitter:image" content="https://block.github.io/goose/assets/images/goose-voyp-215f3391cfbe2132542a2be63db84999.png" />
|
||||
</head>
|
||||
|
|
@ -1,45 +1,45 @@
|
|||
---
|
||||
title: "Turn Figma Designs Into Code With Goose"
|
||||
description: Give Goose the ability to turn Figma designs into code with the Figma extension.
|
||||
title: "Turn Figma Designs Into Code With goose"
|
||||
description: Give goose the ability to turn Figma designs into code with the Figma extension.
|
||||
authors:
|
||||
- tania
|
||||
---
|
||||
|
||||
|
||||
|
||||
In our previous episode of [Goose Flight School](https://www.youtube.com/playlist?list=PLyMFt_U2IX4s1pMaidir5P4lSfjUK6Nzm), our host [Adewale Abati](https://www.linkedin.com/in/acekyd/) showed us how to use Goose to take a Figma design and transform it into a functional Nuxt application. In this stream he covered the entire process, from initial setup to final implementation, highlighting how Goose can help developers bridge the gap between design and development.
|
||||
In our previous episode of [goose Flight School](https://www.youtube.com/playlist?list=PLyMFt_U2IX4s1pMaidir5P4lSfjUK6Nzm), our host [Adewale Abati](https://www.linkedin.com/in/acekyd/) showed us how to use goose to take a Figma design and transform it into a functional Nuxt application. In this stream he covered the entire process, from initial setup to final implementation, highlighting how goose can help developers bridge the gap between design and development.
|
||||
|
||||
<!--truncate-->
|
||||
|
||||
# How It Works
|
||||
[Extensions](https://block.github.io/goose/docs/getting-started/using-extensions) enhance Goose's functionality by connecting with your existing tools and workflows. They add new features, access external data resources, and integrate with other systems. Learn how multiple extensions, including Figma and Developer, worked together seamlessly to dramatically accelerate development.
|
||||
[Extensions](https://block.github.io/goose/docs/getting-started/using-extensions) enhance goose's functionality by connecting with your existing tools and workflows. They add new features, access external data resources, and integrate with other systems. Learn how multiple extensions, including Figma and Developer, worked together seamlessly to dramatically accelerate development.
|
||||
|
||||
# Live Tutorial: Goose Builds Live
|
||||
During the livestream, Adewale demonstrated step-by-step how Goose handled each development phase, from creating the basic application structure to generating responsive layouts using Tailwind CSS. Adewale also highlighted how Goose addresses potential limitations as you go, showcasing the powerful balance between the Goose's automation and developer control.
|
||||
# Live Tutorial: goose Builds Live
|
||||
During the livestream, Adewale demonstrated step-by-step how goose handled each development phase, from creating the basic application structure to generating responsive layouts using Tailwind CSS. Adewale also highlighted how goose addresses potential limitations as you go, showcasing the powerful balance between the goose's automation and developer control.
|
||||
|
||||
<iframe class="aspect-ratio" src="https://www.youtube.com/embed/_9t_N9zKwKM?si=r3e1MkrjS-f2AvkI" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
|
||||
|
||||
Throughout the stream, Adewale shared valuable tips to prepare your design for Goose. His key recommendations include:
|
||||
Throughout the stream, Adewale shared valuable tips to prepare your design for goose. His key recommendations include:
|
||||
|
||||
* start with a well-structured Figma design
|
||||
* use Goose to make targeted improvements after the initial generation
|
||||
* use goose to make targeted improvements after the initial generation
|
||||
* fine-tune specific elements as needed
|
||||
* make sure you thoroughly test for functionality and responsiveness
|
||||
|
||||
# Getting Started with Goose and Figma
|
||||
Whether you're a designer wanting to rapidly turn concepts into working code or a developer curious about streamlining design implementation, you can download Goose with its built-in [Developer extension](https://block.github.io/goose/docs/getting-started/installation) and add the [Figma extension](https://block.github.io/goose/v1/extensions/).
|
||||
# Getting Started with goose and Figma
|
||||
Whether you're a designer wanting to rapidly turn concepts into working code or a developer curious about streamlining design implementation, you can download goose with its built-in [Developer extension](https://block.github.io/goose/docs/getting-started/installation) and add the [Figma extension](https://block.github.io/goose/v1/extensions/).
|
||||
|
||||
For step-by-step instructions, check out the [Figma tutorial](/docs/mcp/figma-mcp).
|
||||
|
||||
<head>
|
||||
<meta property="og:title" content="Goose Flight School: Turn Figma Designs Into Code With Goose" />
|
||||
<meta property="og:title" content="goose Flight School: Turn Figma Designs Into Code With goose" />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://block.github.io/goose/blog/2025/03/12/goose-figma-mcp" />
|
||||
<meta property="og:description" content="Give Goose the ability to turn Figma designs into code with the Figma extension." />
|
||||
<meta property="og:description" content="Give goose the ability to turn Figma designs into code with the Figma extension." />
|
||||
<meta property="og:image" content="http://block.github.io/goose/assets/images/goosefigma-e6f84a734bd56cb431bb02452331a5d5.png" />
|
||||
<meta name="twitter:card" content="summary_large_image" />
|
||||
<meta property="twitter:domain" content="block.github.io/goose" />
|
||||
<meta name="twitter:title" content="Goose Flight School: Turn Figma Designs Into Code With Goose" />
|
||||
<meta name="twitter:description" content="Give Goose the ability to turn Figma designs into code with the Figma extension." />
|
||||
<meta name="twitter:title" content="goose Flight School: Turn Figma Designs Into Code With goose" />
|
||||
<meta name="twitter:description" content="Give goose the ability to turn Figma designs into code with the Figma extension." />
|
||||
<meta name="twitter:image" content="http://block.github.io/goose/assets/images/goosefigma-e6f84a734bd56cb431bb02452331a5d5.png" />
|
||||
</head>
|
||||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Add a link
Reference in a new issue