The official Claude Code plugin for Poly. It gives Claude access to your Poly files and automatically loads your Poly memory context at the start of every session.
- Automatic memory context — a
SessionStarthook runspoly memory summary, so Claude starts with your profile and recent Poly memories already in context. - The Poly agent skill — guidance for searching, reading, creating, updating, and organizing files with the local Poly CLI or hosted MCP server.
- Poly MCP — a hosted MCP connection for working with Poly files from Claude Code.
The hook is a dependency-free Bash script. It does not require Node.js, Python, or jq. It also sets POLY_DISALLOW_FORCE=1 for the session, preventing Claude from permanently deleting files through the CLI.
The memory hook requires the Poly desktop app to be installed, open, and signed in. Install the CLI from Poly → Downloads → Install CLI before installing the plugin.
If Poly is unavailable, Claude Code still starts normally. The plugin shows a visible notice and tells Claude not to interpret the missing context as an empty memory. Start Poly and run /clear to retry the hook.
claude plugin marketplace add withpoly/polycc
claude plugin install poly@polyThe MCP server authenticates with your Poly account through OAuth the first time Claude uses it.
At session startup, resume, and after /clear or context compaction:
- Claude Code runs
plugin/hooks/session-start.sh. - The hook requests
poly memory summaryfrom the locally running Poly app. - It wraps the result in
<poly-memory-context>and returns it as SessionStartadditionalContext. - Claude Code displays
Poly · memory context loaded.
The skill does not request the summary again. It loads only when Claude needs to work with Poly files or search memory in more detail.
Ask naturally:
What was I focused on last week?
Find the product brief in Poly and summarize the open questions.
Move every approved launch asset into the shared Marketing drive.
See the Poly + Claude Code guide for more.