Hark
HOW IT WORKSCONNECT YOUR TOOLS
Connect

Connect your tools to Hark

Pick the AI tool you use below and follow the steps — usually a button or one line. Once connected, every tool reads the same current state and leaves a note when it's done, so the next one picks up where the last left off.

MCP endpoint
https://harkstudio.io/mcp

Sign in to Hark to connect a client. Personal tokens and per-account details live inside the app.

The Hark mod for Claude Code (Early access)

A Claude Code plugin: starts every session briefed, keeps the plan through compaction, guards agreed decisions, and ends with a handoff.

Early access. The Claude plugin directory listing is pending; the install from the repo below works today.

What it does

1. Brief on start. When a session starts, the mod fetches the project's compact brief and adds it to your first message, so Claude already knows the plan, the agreed decisions and the next action.

2. Survives compaction. When Claude Code compacts the conversation, the agreed decisions, non-goals, blockers and next action come back right after, so the plan isn't lost halfway through a long session.

3. Decision guard. Before Claude edits a file covered by an agreed decision or non-goal, you see the decision and why, and choose Allow or Stop. The check runs on your machine; nothing about the edit is sent.

4. Stop = handoff. When the session ends, Hark gets a short summary — files touched, commits, test results and Claude's closing notes — and drafts the handoff for you to review. Sessions with no changes write no handoff.

5. Status line and /hark. The status line shows the project, its handoff state and how many items need you. /hark brief, /hark handoff, /hark needs and /hark open do the obvious things.

Install

From the Claude plugin directory (works once the listing is live):

/plugin install hark@claude-plugins-official

Works now — from the repo, in a Claude Code session:

/plugin marketplace add Hark-Studio/hark-mod
/plugin install hark@hark

Or from a shell:

claude plugin marketplace add Hark-Studio/hark-mod
claude plugin install hark@hark

Confirm it works: start Claude Code in the project and run /hark brief.

Requirements

  • Claude Code 2.1.287 or newer.
  • A Hark access key — open Connections in Hark and choose "Create key for Claude Code".
  • The project linked in the repo: run hark init (writes .hark/project), or Hark's installer (writes a .hark file). Without one, the mod stays idle and sends nothing.
Create key for Claude Code →

Configuration

  • Access key: the HARK_TOKEN environment variable, then HARK_PAT, then a keychain item named hark (macOS: security add-generic-password -s hark -a "$USER" -w; Linux: secret-tool store --label=Hark service hark). On Windows, set HARK_TOKEN.
  • Project: the mod reads .hark/project, or a .hark file holding venture=V-012. It looks in the folder Claude Code starts in, then each parent folder, so monorepo packages work.
  • Turn off single behaviors (the decision guard, the re-inject after compaction, the status line) in the plugin's settings in Claude Code's /plugin menu.

Privacy and trust

  • Sent: session events and metadata only — the project code, brief requests, and at the end the handoff summary (file paths, commit subjects, test pass/fail, Claude's closing notes with code and secrets redacted).
  • Never sent: file contents, the text of your edits, transcripts, or secrets. The decision guard runs locally.
  • Every request is one HTTPS call to harkstudio.io/mcp with your access key; each is abandoned after 3 seconds, and nothing ever blocks a prompt, an edit or an exit.
  • Claude Code plugins run unsandboxed on your machine, so this one is kept to a single small, dependency-free file you can read before installing.
Read the source: github.com/Hark-Studio/hark-mod

Other tools

The mod is Claude Code only. Cursor and Codex keep using their install buttons and Hark's hooks, and work alongside it.

Troubleshooting

  • Brief not added: check the access key is set, the repo has .hark/project or .hark, and claude --version is 2.1.287 or newer.
  • Guard asks too often: give decisions a scope (an area like billing, or a path like src/db/**) so they only cover the files they're about.
  • No handoff drafted: usually the network at exit. Hark drafts one from repo activity after 45 minutes idle, so nothing is lost.
  • Uninstall: /plugin uninstall hark@hark (and /plugin marketplace remove hark).

Verify it works

Ask your client: "List my Hark workspaces." Expected: your workspace names.

Then: "Create a project called Connection test in <workspace>." Expected: a new V-### appears in the app and the activity log shows the source ("via Claude Code", "via Codex", etc.). Delete the test venture afterward.

Troubleshooting

  • "Unauthorized request origin" — the client origin isn't allowlisted; retry from the latest app version, or email hello@harkstudio.io.
  • Consent screen loops / stale token — remove the connector in the client, sign out of Hark, sign back in, re-add the connector.
  • Tools list is empty — the connector isn't enabled for this chat (Claude and ChatGPT require enabling it per conversation).
  • Plan cap error — you've hit the monthly agent-call cap for this workspace; see billing.
  • Old endpoint — anything pointing at a lovable.app URL must be updated to harkstudio.io/mcp.
SIGN IN TO CONNECT