Goose Integration Guide

Give Goose  (Block’s open-source agent) persistent memory across sessions using Engram.

Setup

Option A: one-off session

goose session --with-streamable-http-extension "https://mcp.getengram.app/mcp"

Goose runs Engram’s OAuth sign-in on first connect.

Option B: permanent extension

Run goose configure → Add Extension → Remote Extension (Streamable HTTP) and enter:

• Name: engram
• URL: https://mcp.getengram.app/mcp

Prefer an API key instead of OAuth? Sign up at getengram.app , create a key, and add a request header when prompted: Authorization: Bearer engram_sk_live_your_key_here.

Known issue: some Goose versions re-prompt the OAuth flow each session (goose#3545 ). If that bites you, use the API-key header instead — it authenticates silently.

Verify

In a Goose session, ask it to search Engram. If it can call the search tool, you’re connected.

Using memory in Goose

• “Remember this” — stores the exchange verbatim
• “What do you remember about this repo?” — semantic search over everything stored
• One memory across tools: sessions captured from Claude Code, notes saved in ChatGPT, and context from Cursor are all recallable here.