Roll out to your team

Each developer can install the plugin themselves (Claude Code, Codex & Cursor). For a team, an admin can put it on every machine and switch it on through each tool's managed settings. Each developer still signs in once, so their agent reads the workspace as them: the first session after rollout says how.

1. Put the plugin on every machine

Unzip the plugin from Downloads to the same place on every machine, for example /opt/jackdaw-agent-plugin (macOS and Linux). Your device-management tool (Jamf, Kandji, Intune, a setup script) can do this. Python 3 must be installed; the helper uses nothing else.

2. Switch it on

Claude Code

Add this to Claude Code's managed settings: the managed-settings.json file (/Library/Application Support/ClaudeCode/managed-settings.json on macOS, /etc/claude-code/managed-settings.json on Linux, C:\Program Files\ClaudeCode\managed-settings.json on Windows), or the Claude Code settings in your Claude admin console on Team and Enterprise plans.

{
  "extraKnownMarketplaces": {
    "jackdaw": { "source": { "source": "directory", "path": "/opt/jackdaw-agent-plugin" } }
  },
  "enabledPlugins": { "jackdaw@jackdaw": true }
}

extraKnownMarketplaces makes the plugin folder known to Claude Code; enabledPlugins set to true turns the plugin on for everyone, and developers can't turn it off. We checked the marketplace entry and the install with Claude Code 2.1.281; that a managed enabledPlugins installs the plugin on each machine's next session follows Anthropic's managed-settings documentation.

Codex

Codex can't switch a plugin on for everyone, but its managed requirements.toml (/etc/codex/requirements.toml) can run the plugin's hooks for every user, as OpenAI's managed configuration describes. Point each hook at the helper with --client codex:

SessionStart, UserPromptSubmit, SubagentStart: python3 /opt/jackdaw-agent-plugin/plugins/jackdaw/scripts/jackdaw-cli context --client codex --event <the event>
Stop: python3 /opt/jackdaw-agent-plugin/plugins/jackdaw/scripts/jackdaw-cli capture --client codex

The plugin's own hooks/hooks.json has the same entries with their timeouts. We haven't tested this route yet.

Cursor

Cursor runs hooks from a hooks.json your device management places at /Library/Application Support/Cursor/hooks.json (macOS), /etc/cursor/hooks.json (Linux) or C:\ProgramData\Cursor\hooks.json (Windows); developers can't turn those off (Cursor's hooks documentation). Use the plugin's hooks/cursor-hooks.json with the plugin folder written out in full, since admin hooks don't get the plugin's path:

{
  "version": 1,
  "hooks": {
    "sessionStart": [{ "command": "python3 /opt/jackdaw-agent-plugin/plugins/jackdaw/scripts/jackdaw-cli context --client cursor --event SessionStart --format cursor" }],
    "beforeSubmitPrompt": [{ "command": "python3 /opt/jackdaw-agent-plugin/plugins/jackdaw/scripts/jackdaw-cli capture --client cursor", "timeout": 10 }],
    "afterAgentResponse": [{ "command": "python3 /opt/jackdaw-agent-plugin/plugins/jackdaw/scripts/jackdaw-cli capture --client cursor", "timeout": 15 }]
  }
}

Keep the plugin in a folder without spaces: Cursor fails a hook command whose path has one. We haven't tested this route yet.

3. Session memory for the whole company

Session memory (each finished turn kept as dated work memory, visible only to the developer) is on by default. To turn it off for everyone, set JACKDAW_SESSION_MEMORY=off in the tools' environment; for Claude Code, add it to the managed settings:

{ "env": { "JACKDAW_SESSION_MEMORY": "off" } }

With it off, developers can't turn it back on. on only makes it the default: a developer who turns session memory off keeps it off.

4. Each developer signs in once

On their first session, the agent shows a one-line notice with the setup command to run from their repository. It opens Jackdaw's sign-in, where they choose your workspace, then offers to import the repository's existing Claude Code memory notes and to turn Claude Code's own memory off.