Skip to content

metedata/remarc

v0.13.2MIT

Read, address, and resolve Remarc comments from supported coding agents.

GitHubOpen Website

remarc

The core plugin for connecting supported coding agents to the Remarc macOS app.

It contains:

  • the Remarc MCP server for reading sessions, fetching captured context, and updating comment status;
  • the remarc skill for read-only, addressing, and status-only workflows;
  • harness-specific manifests for Claude Code and Codex, plus the portable Agent Plugins 1.0 plugin.json and mcp.json consumed by Codex Desktop and OMP.

Requirements

  • Remarc installed on macOS and launched at least once.
  • Node.js available as node.
  • Claude Code, Codex, or OMP with plugin support.

Install for Claude Code

claude plugin marketplace add metedata/remarc-agent-plugins
claude plugin install remarc@remarc

After installation in an active session, run /reload-plugins.

Update or remove it with Claude Code's plugin manager:

claude plugin marketplace update remarc
claude plugin update remarc@remarc
claude plugin uninstall remarc@remarc

Install for Codex

codex plugin marketplace add metedata/remarc-agent-plugins
codex plugin marketplace upgrade remarc
codex plugin add remarc@remarc

Remove it with:

codex plugin remove remarc@remarc

Install for OMP

omp plugin marketplace add metedata/remarc-agent-plugins
omp plugin install remarc@remarc

In an active OMP session, run:

/reload-plugins
/mcp list
/mcp test remarc:remarc
/skill:remarc

OMP can read and update existing sessions and create sessions with native origin: "omp". OMP supplies omp-coding-agent in the MCP initialization handshake, and the legacy Claude/Codex session-id field is not required.

The OMP catalog installs this directory as the package root. OMP 17.3.4 reads the root plugin.json, loads the root mcp.json, expands ${PLUGIN_ROOT} to the cached installation, and starts the bundled MCP server. The launcher is harness-neutral because Codex Desktop can consume the same portable manifest; the server distinguishes omp-coding-agent from Codex's codex-mcp-client during initialization. In the TUI, /mcp list shows that server as remarc:remarc under Agent Plugins.

See the OMP integration guide for scoped installation, updates, removal, and troubleshooting.

Verify

Ask the agent to call remarc_list_sessions. A returned session list proves that the packaged MCP server can read the current Remarc data.

The server exposes:

  • remarc_list_sessions
  • remarc_list_comments
  • remarc_get_comment
  • remarc_set_status
  • remarc_bulk_set_status
  • remarc_rename_session
  • remarc_create_session

See the MCP tools reference for inputs and workflow guidance.

Those are the protocol-level MCP names. OMP's agent-facing bridge includes the sanitized namespaced server name, so remarc_list_sessions, for example, appears to the model as mcp__remarc_remarc_remarc_list_sessions. Users can still ask for the semantic operation by name; they do not need to type the generated identifier.

Optional Claude Code lifecycle integration

Install remarc-hooks when you explicitly want Claude Code conversations paired with Remarc sessions and eligible for instant delivery:

claude plugin install remarc-hooks@remarc

The core MCP plugin works without hooks.

Current limits

  • Correctly labelled session creation supports Claude Code, Codex, and OMP. OMP creation relies on its transport-level MCP client identity, leaves the legacy claudeCodeSessionId empty, and pairs separately through remarc-wake.
  • OMP instant delivery is optional and requires the separately installed remarc-wake extension plus a Remarc build that understands its v1 lease.
  • Screenshot paths are local to the Mac running Remarc and may be unavailable to a remote agent.
  • The plugin reads and writes local Remarc data; tool results are processed by the configured agent provider.

The cross-repository data, lock, marker, and status contracts are documented in plugins/shared/contracts.md.

Directory review and privacy

Anthropic reviewers can use the deterministic fixture and prompts in DIRECTORY_REVIEW.md. The plugin's data access, provider-processing boundary, storage, and contact details are documented in the repository privacy policy.