Installation guide

Install Penny for OpenCode

Use Penny’s operating skill and OAuth tools in OpenCode, with explicit opt-in for each private conversation.

Instructions checked October 11, 2026

Add the plugin and MCP configuration

Merge this into your OpenCode configuration, preserving existing providers, plugins and permissions:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@mypenny/opencode@0.1.0"],
  "mcp": {
    "penny": {
      "type": "remote",
      "url": "https://app.mypenny.ai/mcp",
      "headers": { "X-MyPenny-Require-Auth": "true" }
    }
  },
  "permission": { "penny_*": "ask" }
}

OpenCode installs the npm plugin on startup. Keep the auth-challenge header: OpenCode authenticates before plugin hooks run. It contains no token. The ask rule keeps normal tool approvals.

Connect your Penny account

opencode mcp auth penny

Complete OpenCode’s OAuth flow in your browser, signing in to Penny and approving the displayed access.

Enable this private conversation

Start a fresh, unshared conversation and say:

Enable Penny private memory for this conversation. Load my Penny context before we start.

Approve penny_enable and the requested Penny tools. Every new conversation starts disabled. Child sessions and sessions with a share URL cannot enable memory. Say “Disable Penny for this conversation” to clear the grant. A server restart clears it too.

Verify and review what is shared

Search Penny for the exact phrase "Penny connection check 7c98e2". An empty result is fine. Do not save or change anything.

Approve the native penny_penny_read call. An empty tool result is enough to verify the read connection. Approved calls send their arguments to Penny; returned memory may be sent to your configured model provider and appears in the conversation. Keep conversations containing private memory unshared.

Hooks supply public reminders, not automatic reads or transcript uploads. Recall and saves depend on the agent following instructions; saving before compaction is best effort. Explicit opt-in and native approvals matter because the host cannot attest every scheduled context.

Disconnect or remove

opencode mcp logout penny

Remove only @mypenny/opencode@0.1.0 from the plugin list and the penny MCP configuration, then restart OpenCode. Preserve other plugins and permission rules. Use Penny’s account controls to revoke access as well. Plugin removal alone does not log out or erase memory already returned to a conversation.

Having trouble?

If authentication fails, check the exact Penny URL and required header, then rerun auth. If tools are denied, enable the current unshared conversation and check your explicit permission rules. Do not replace them with an always-allow wildcard.

Release instructions and limitations. For help, use Settings → Support or email support@mypenny.ai. Keep tokens, private memories and unredacted logs out of support messages.

Keep these instructions handy

Open this guide in your Penny dashboard · Read as Markdown

Need help with your connection? Email support@mypenny.ai. Keep passwords, tokens and private notes out of support messages.