Other Agents

Last updated 2026-08-21

Ocul-PM isn't Claude Code only. Any agent that reads AGENTS.md can leave entries, and for agents that don't, a thin delegating stub is placed in their own rules file.

Why AGENTS.md is the center

Adding a project creates AGENTS.md at the root. The entire body of the journaling rules lives there — when to record, where files go and what they're named, what the frontmatter needs.

Claude Code, Codex CLI, Gemini CLI and many others read this file natively. That's how the rules arrive with no extra install.

Note

Originally the rules only lived in .oculpm/agents/_template.md, and dogfooding showed external LLMs don't go read that file on their own. So the root AGENTS.md became the primary surface, and other adapters were reduced to stubs pointing at @AGENTS.md.

Supported rules files

Toggle these in Settings → ocul-pm → Agents. Turning one on creates the file at that path and keeps it updated as rules change.

AgentRules file
Shared (Claude Code, Codex CLI, …)AGENTS.md
Claude Code.claude/CLAUDE.md
Cursor.cursor/rules/ocul-pm.mdc
Gemini CLIGEMINI.md
GitHub Copilot.github/copilot-instructions.md
Windsurf.windsurf/rules/ocul-pm.md
Cline.clinerules/ocul-pm.md
Zed.rules
aiderCONVENTIONS.md
Antigravity.agent/rules/ocul-pm.md

Your own content is preserved

Some of these are files you write in tooAGENTS.md, .claude/CLAUDE.md, GEMINI.md, .github/copilot-instructions.md, CONVENTIONS.md, .rules.

In those, the app owns only the marked block:

<!-- oculpm:begin v1 -->
… app-managed rules …
<!-- oculpm:end -->

Anything outside the block survives a rules refresh. Your coding conventions and the app's journaling rules can share one file.

Warning

By contrast .cursor/rules/ocul-pm.mdc, .windsurf/rules/ocul-pm.md, .clinerules/ocul-pm.md, and .agent/rules/ocul-pm.md are app-owned files and are overwritten wholesale. Don't put personal rules at those paths.

Editing the rules themselves

To change the wording, edit .oculpm/agents/_template.md. That's the master; saving propagates to every adapter you've enabled — fix it once and Cursor and Claude Code both get the new rules.

To give one agent different wording, put a file for it under .oculpm/agents/per-agent/.

When the rules go stale

App updates can raise the rules spec. Resend rules in Settings → ocul-pm → Agents reinstalls the current spec. The detect button narrows the list to agents that appear to be in use in this project.

Degrees of automatic recording

"Leaves entries" comes in different strengths:

ApproachConfidence
In-app Claude CodeHigh — recording tools (MCP) attached directly to the session
Terminal Claude Code + pluginHigh — a session-end hook fires structurally
Any other agent (rules file only)Medium — as much as the model remembers the rules

On that third tier, check the honesty audit on Today now and then. Anything missed shows up there.

Tip

If you use Claude Code, installing the plugin makes the biggest difference — two lines, in Claude Code.

Mixing several agents

No problem. Each entry's frontmatter records agent.id and the model name, so you can tell later who did what. The retro's Agent contributions card shows the distribution.

Skills & Rules hub

The Skills & Rules screen in the sidebar is where you work all of the above from inside the app. It has five tabs.

Skills

One SKILL.md file is one skill. Agents invoke skills on their own based on the description in the frontmatter — which is why writing a good description matters.

  • Project / Global — keep it to this project (.claude/skills/) or make it available everywhere (~/.claude/skills/). You can copy between them
  • Disable — moves it to .claude/skills/.disabled/ so it isn't loaded. The file is not deleted
  • Edit — change it in the app and save with ⌘S
  • New skill — start from an empty one

Shop

Install curated skills that build verification habits with one click — things like self-audit, which makes agents check their own work.

Rules

Toggle the per-adapter rules files covered above, and edit the master.

Hooks

Claude Code hook integration. With hooks on, session start and end are recorded from real signals instead of heuristics — rather than the app guessing "files went quiet, must be done," the agent says so.

Note

The auto journal draft at session end (which costs money) and MCP tool registration are managed in Settings → ocul-pm → Integration, not this tab.

Plugin

Shows what the plugin installs — the list of commands, tools, and skills.

Next steps