Platform extensions sketch #4868

DOsinga · 2025-09-28T16:52:09Z

Platform Extensions

This introduces a new type of extension, platform extensions. these are extensions that are tied tightly to the platform and can (currently) read and write to the current session.

It also makes description a required field on the extensions for consistency

DOsinga · 2025-09-28T16:58:59Z

crates/goose/src/agents/todo_extension.rs

+                version: "1.0.0".to_string(),
+            },
+            instructions: Some(
+                "Manage TODO lists - read and write task planning content.".to_string(),


we should expand this of course

so this replaces the prompt for existing todos? (or it is still in system prompt?). Existing todos seem to think they are a file which always looks odd, so probably good to play around with this

yes, will be. currently todo read & write are tools without an extension, which means there is no extension prompt which means we include it in the system prompt which means that if you switch off todo, it still knows about it. so that's one of the things we're trying to fix here

angelahning · 2025-09-29T17:39:14Z

crates/goose/src/agents/agent.rs

                "Frontend tool execution required".to_string(),
                None,
            )))
-        } else if tool_call.name == TODO_READ_TOOL_NAME {


yeah this is the best bit!

crates/goose/src/agents/extension.rs

angelahning · 2025-09-29T19:04:03Z

crates/goose/src/agents/todo_tools.rs

-    Tool::new(
-        TODO_READ_TOOL_NAME.to_string(),
-        indoc! {r#"
-            Read the entire TODO file content.


Have these tool instructions been ported somewhere else?

they have now

angelahning · 2025-09-29T19:13:04Z

crates/goose/src/config/extensions.rs

-            .unwrap_or_else(|_| HashMap::new()))
+            .unwrap_or_else(|_| HashMap::new());
+
+        if !extensions_map.is_empty() {


Why do we only enable the platform extensions if the user has existing extensions?

good question; I saw this happening where it would get here and not have any extensions yet and then if we insert it here, something else is not going to set their defaults. obviously would be better to solve the issue in that something else, but that feels like it is inside some hairy client code. we should get a good opinion though on where in general the default extensions are set. I'm not sure !

angelahning · 2025-09-29T19:43:13Z

crates/goose-server/src/routes/extension.rs

-
    // If this is a Stdio extension that uses npx, check for Node.js installation
    #[cfg(target_os = "windows")]
    if let ExtensionConfigRequest::Stdio { cmd, .. } = &extension_request {


does this compile? here's referring to ExtensionConfigRequest::stdio which has been deleted

ooh, good catch. probably no longer compiles on windows. it does beg the question what this windows specific code is doing here and why it is installing a specific version of node, but still.

angelahning · 2025-09-29T20:04:35Z

crates/goose/src/agents/todo_extension.rs

+        vec![
+            Tool {
+                name: "todo_read".into(),
+                description: Some("Read the current TODO list content".into()),


description needs to be expanded. Same for the write tool below.

this is a sketch - the idea is to look at the architecture

michaelneale · 2025-09-30T02:38:15Z

crates/goose-cli/src/commands/configure.rs

-            } else {
-                None
-            };
+            let description = cliclack::input("Enter a description for this extension:")


so descriptions are required now - but not often used, how come mandatory now effectively?

well, we were using them all over the place, just for when we didn't have them we would try to put something together ourselves. this is just an effort to make it all look a bit more like each other.

that is ok - just wanted to make sure deliberate and won't cause problems loading older configurations

michaelneale · 2025-09-30T02:39:26Z

crates/goose/src/agents/extension.rs

+        let mut map = HashMap::new();
+
+        map.insert(
+            todo_extension::EXTENSION_NAME,


much nicer looking

michaelneale · 2025-09-30T23:46:44Z

LGTM - when ready/builds any thing to manually test and watch out for @DOsinga ?

alexhancock · 2025-10-01T01:45:39Z

crates/goose/src/agents/todo_extension.rs

+        }
+
+        vec![
+            Tool {


Can do Tool::new for a bit nicer syntax if we want

alexhancock · 2025-10-01T01:46:57Z

crates/goose/src/agents/todo_extension.rs

+impl TodoClient {
+    pub fn new(context: PlatformExtensionContext) -> Result<Self> {
+        let info = InitializeResult {
+            protocol_version: ProtocolVersion::V_2025_03_26,


if there is a constant for the june version we can start using it. i was going to take a pass and make that the default in rmcp. we more closely resemble the june version than march.

sounds good. of course this is internal only so for now I doubt we'll check it, bit still

jamadeo

Nice. I think passing the context to a per-session client is great, and opens these up to be really quite powerful.

I'm fine with description being non-optional in general, but I don't think users should have to create a description when adding an MCP server. (e.g. I go find the github mcp, add it, I should not have to also type "github" in a description field.)

jamadeo · 2025-10-01T12:40:59Z

crates/goose/src/agents/todo_extension.rs

+
+#[async_trait]
+impl McpClientTrait for TodoClient {
+    async fn list_resources(


if these are going to act like mcp servers, it would be really nice to be able to define them using rmcp's server sdk, e.g.

impl Todo { #[tool(name = "todo_add")] pub async fn todo_add(...) }

they could still be built with the platform extension context and have all the same access, but they'd be easier to write and easily port-able to out-of-process MCP servers

michaelneale · 2025-10-01T23:28:14Z

but my config is:

GOOSE_MODEL: claude-sonnet-4-5-20250929
ANTHROPIC_HOST: https://api.anthropic.com
GOOSE_PROVIDER: anthropic
OTEL_EXPORTER_OTLP_ENDPOINT: https://goose-otlp-proxy.sqprod.co
GOOSE_RECIPE_GITHUB_REPO: squareup/goose-recipes
extensions:
  developer:
    enabled: true
    type: builtin
    name: developer
    display_name: Developer Tools
    description: null
    timeout: 300
    bundled: true
    available_tools: []

so something is broken with the extension loading (it won't load or even recognise a built in) specifically with this branch

michaelneale

isn't picking up built in extensions or configured extensions (see comment)

DOsinga · 2025-10-02T02:20:56Z

isn't picking up built in extensions or configured extensions (see comment)

I couldn't reproduce this, but it did asked me if I wanted to fix the install of the todo extension. that should be fixed now. it might be the same thing. this is what I am seeing:

michaelneale · 2025-10-03T01:04:31Z

@DOsinga still the same - not showing any extensions or finding them, and have pulled latest

no idea why - but any other branch is fine, it is just this one

michaelneale · 2025-10-03T01:12:14Z

ok testing with production build cargo build -r is where I am seeing it not work for some reason...

…into platform-extensions

michaelneale

ok think have hammered on this enough - cli does work now - so I am happy (weird how it loaded different - I guess longer term that code path will be replaced with goosed so all good).

I also note that todo now shows up an extension you can turn off, but it is not in the config.yaml - which means you can't "add it" later on - is this an issue? (maybe it will always just show up in any list which is fine and ideal). Again - cli only.

(openapi schema isn't happy though - but when build is ok I think this makes sense)

DOsinga · 2025-10-03T12:50:17Z

ok think have hammered on this enough - cli does work now - so I am happy (weird how it loaded different - I guess longer term that code path will be replaced with goosed so all good).

I also note that todo now shows up an extension you can turn off, but it is not in the config.yaml - which means you can't "add it" later on - is this an issue? (maybe it will always just show up in any list which is fine and ideal). Again - cli only.

(openapi schema isn't happy though - but when build is ok I think this makes sense)

yeah, good analysis. todo always shows up, as it is a platform tool, so all you can do is switch it off. if you delete it from the config, we add it again. I think this is how all bundled tools should work? not sure. also not sure on how it works now and when they are re-added (i.e. like with developer tool, the desktop will adde them if deleted?). might need to do a follow up to clean this up

* main: Removed unused libs (block#4932) Platform extensions sketch (block#4868) Add reply to the routes (block#4963) feat(cli): add GOOSE_DEBUG environment variable support (block#4825)

* main: (22 commits) fix: Issue #4540: `goose configure` -> Cursor Agent succeeds (#4942) feat: Add advanced data analysis pipeline recipe (#4990) (#5005) Create / edit recipe form unification and improvements (#4693) feat: add Code Review Mentor recipe with Developer and Memory extensions (#4992) (#5014) feat: set custom models for lead/worker (#4598) feat: add grok-code-fast-1 support for xAI provider (#4472) Persist dynamic extension config so we can resume recipe sessions w/ extensions (#4331) fix: show PowerShell PATH instructions for Windows users (#4989) feat: add Smart Task Organizer recipe for Hacktoberfest (#4936) Fix extension headers (#5000) feat: add advanced software project generator initializer recipe (#4767) (#4949) Removed unused libs (#4932) Platform extensions sketch (#4868) Add reply to the routes (#4963) feat(cli): add GOOSE_DEBUG environment variable support (#4825) docs: Change community page sections (#4984) docs: remove temporary Hacktoberfest issue templates (#4982) Create multi-channel researcher prompt (#4947) docs: Add Community Content section to Community Page (#4964) Allow empty API Key when registering custom provider (#4977) ...

Co-authored-by: Douwe Osinga <[email protected]> Co-authored-by: Michael Neale <[email protected]> Signed-off-by: Itz-Agasta <[email protected]>

The todo extension added in block#4868 causes errors with bedrock because bedrock expects an input schema. Without this fix, bedrock tool calls fail with Error: Server error: Failed to call Bedrock: ValidationException(ValidationException { message: Some("The value at toolConfig.tools.3.toolSpec.inputSchema.json.type must be one of the following: object."), meta: ErrorMetadata { code: Some("ValidationException"), message: Some("The value at toolConfig.tools.3.toolSpec.inputSchema.json.type must be one of the following: object."), extras: Some({"aws_request_id": "9813e4c5-607f-47fc-8a6a-4387ef28acb7"}) } })

The todo extension added in block#4868 causes errors with bedrock because bedrock expects an input schema. Without this fix, bedrock tool calls fail with Error: Server error: Failed to call Bedrock: ValidationException(ValidationException { message: Some("The value at toolConfig.tools.3.toolSpec.inputSchema.json.type must be one of the following: object."), meta: ErrorMetadata { code: Some("ValidationException"), message: Some("The value at toolConfig.tools.3.toolSpec.inputSchema.json.type must be one of the following: object."), extras: Some({"aws_request_id": "9813e4c5-607f-47fc-8a6a-4387ef28acb7"}) } }) Signed-off-by: alexyao2015 <[email protected]>

Platform extensions sketch

a237a15

DOsinga commented Sep 28, 2025

View reviewed changes

DOsinga mentioned this pull request Sep 29, 2025

Add MOIM (Minus One Info Message) for automatic context injection (TODO list and current time) #4833

Closed

Merge branch 'main' into platform-extensions

7a5b224

angelahning reviewed Sep 29, 2025

View reviewed changes

michaelneale reviewed Sep 30, 2025

View reviewed changes

Douwe Osinga added 4 commits September 30, 2025 16:07

Merge branch 'main' into platform-extensions

014362a

Port the prompt

58ad6f6

This windows thing

890321b

Some testing

0cf10d1

Remove

1657ead

alexhancock reviewed Oct 1, 2025

View reviewed changes

jamadeo reviewed Oct 1, 2025

View reviewed changes

Douwe Osinga added 8 commits October 1, 2025 09:40

Merge branch 'main' into platform-extensions

0d9b694

Merge branch 'main' into platform-extensions

e631ecc

Update extension definition

9d68885

Merge branch 'main' into platform-extensions

dbfbf44

more desc

80cf29d

Merge branch 'main' into platform-extensions

f3d90c5

unused

9777934

ugh

cd0ee96

michaelneale requested changes Oct 1, 2025

View reviewed changes

What Mic said

465cd66

michaelneale and others added 3 commits October 3, 2025 11:13

Add logs/ directory to .gitignore

78556e9

More defensive

9c06027

Merge branch 'platform-extensions' of https://github.com/block/goose …

7989104

…into platform-extensions

michaelneale approved these changes Oct 3, 2025

View reviewed changes

Back to required

abe7256

DOsinga merged commit 96ded37 into main Oct 3, 2025
11 checks passed

DOsinga deleted the platform-extensions branch October 3, 2025 17:45

lifeizhou-ap mentioned this pull request Oct 6, 2025

fix: backwards compatible parsing recipe file #5020

Merged

9 tasks

Itz-Agasta pushed a commit to Itz-Agasta/goose that referenced this pull request Oct 7, 2025

Platform extensions sketch (block#4868)

3e19722

Co-authored-by: Douwe Osinga <[email protected]> Co-authored-by: Michael Neale <[email protected]> Signed-off-by: Itz-Agasta <[email protected]>

alexhancock mentioned this pull request Oct 8, 2025

chore(release): release version 1.10.0 #5060

Closed

alexyao2015 mentioned this pull request Oct 8, 2025

Fix bedrock tool input schema #5064

Merged

9 tasks

alexhancock mentioned this pull request Oct 9, 2025

release/1.10.0 #5101

Closed

+                      }
+                      vec![
+                          Tool {

Platform extensions sketch #4868

Platform extensions sketch #4868

Uh oh!

Conversation

DOsinga commented Sep 28, 2025