The official Codex plugin for Poly. It gives Codex 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 Codex 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 Codex.
The hook is a dependency-free Bash script. It does not require Node.js, Python, or jq.
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, Codex still starts normally. The plugin shows a visible notice and tells Codex not to interpret the missing context as an empty memory. Start Poly and begin a new task to retry the hook.
codex plugin marketplace add withpoly/polycodex
codex plugin add poly@polyOn the next Codex session, open /hooks, review the Poly SessionStart hook, and trust it. Start another task after trusting it so the hook can load your memory context.
The MCP server authenticates with your Poly account through OAuth the first time Codex uses it.
At session startup, resume, clear, and context compaction:
- Codex runs
hooks/session-start.shfrom the installed plugin. - The hook requests
poly memory summaryfrom the locally running Poly app. - It wraps the result in
<poly-memory-context>and returns it as SessionStartadditionalContext. - Codex displays
Poly · memory context loaded.
The skill does not request the summary again. It loads only when Codex 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 + Codex guide for more.