Human-in-the-loop for Goose
Goose is Block's open-source, on-machine agent, and every Goose extension is an MCP server. That makes Orako a natural fit: add it as a stdio extension and Goose can ask the teammate who owns a decision, then continue the session with a claimed answer.
Connect Orako to Goose
- 01
Add the extension below to ~/.config/goose/config.yaml, or run
goose configure. - 02
Goose loads Orako's tools with the extension at session start.
- 03
When a decision needs a person, Goose calls
ask_specialistand resumes on the reply.
extensions:
orako:
name: orako
type: stdio
enabled: true
cmd: orako
args: ["mcp", "--server", "https://app.orako.io"]
envs:
ORAKO_TOKEN: <your token>
timeout: 300You can also add it interactively with goose configure → Add Extension → Command-line Extension. The timeout is generous on purpose: humans answer in minutes, not milliseconds.
New to MCP in Goose? See Block’s docs.
What Goose can ask
Goose extensions meet your team's actual experts.
Sessions that outlive a Slack ping
Goose runs long local sessions. A question fires through Orako, the claimed answer arrives when the auth owner is free, and the session threads it in without losing state.
Recipes with a human step
Teams share Goose recipes for repeatable jobs. A recipe that includes ask_specialist bakes "check with the owner" into the workflow itself.
On-machine agent, off-machine knowledge
Goose works locally, but the answers it collects through Orako land in a shared knowledge base the whole team searches.
Goose + Orako, answered
Does Goose support MCP natively?
Yes, structurally: Goose extensions are MCP servers. A stdio extension in config.yaml declares type, cmd, args, envs, and a timeout, and Goose loads its tools at session start. Orako is one such extension.
Why raise the extension timeout for Orako?
Because the tool call completes when a human answers. Goose's default extension timeouts assume fast machine responses; setting timeout: 300 gives a teammate a realistic window to claim and reply before Goose gives up on the call.
Do my teammates need this agent installed to answer?
No. Only the developer running the agent connects Orako. The people answering receive each question in Slack, Microsoft Teams, Discord, or the Orako dashboard, claim it there, and reply in the thread. They never touch an editor, a terminal, or an MCP config.
What happens to the answers?
Every resolved conversation is saved to your organization's knowledge base with a confidence score. Agents call search_knowledge before asking, so a question your team already answered is served from the knowledge base instead of pinging anyone again.
Put a human in the loop for Goose
Give Goose the one thing it can’t generate: the answer only your team knows.