Set up from your repo

Let the agent read your project and file the first project for you.

Already deep in a project? Don't fill anything in by hand. Point your connected agent at the code and let it hand Hark the first project — then keep the one thing it can't know.

Paste this to your agent

Setup prompt

Read this project, then call propose_venture_from_project with a proposed project (title, one-liner, problem, solution, target market) and the build_state as it actually stands (current phase, summary, in progress, next up, blockers, open questions), plus every decision you can see with its rationale.

Then ask me for one constraint or decision that only Hark should know — something not visible in the code — and record it with add_journal_entry as a decision.

One tool call creates the project, its business fields, its Current state and its decisions, and returns the new V-### code.

Prove the handoff

Open a different client — or just start a fresh session in the same one.
Ask: "Call get_agent_brief for V-### and tell me the constraint I recorded."
If it comes back with your constraint, the handoff is real: your decisions survived the switch.

The getting-started card ticks this step off by itself as soon as a brief read arrives from a second client or a fresh session.

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.

What Hark keeps clear

Evidence on every line

Every record shows Agreed / Observed / Proposed and a source you can open: where did this come from? Agreed means accepted, not independently verified. Observed is reserved for system evidence such as a merged pull request. An agent's claim is never shown as verified simply because it was accepted.

Learn more

Repo-native rules

Once linked and selected as the source, the repo's CLAUDE.md or AGENTS.md is authoritative. Hark mirrors it on pushes and retains history rather than authoring competing edits. Optional .hark/ export carries accepted handoff state and decisions into the repo. Repo activity suggests drafts with commit evidence. Agent briefs include mirrored instruction documents and linked repo metadata. Arbitrary repo-document browsing is not exposed by the current tools: Hark never serves source code. Automatic session hooks and compaction protection in the Hark mod are Claude Code-only; other tools follow their connection guide and explicit session tools.

Learn more

Scoped, expiring agent access

New agent keys default Propose: suggest changes, never approve them. An eight-character pairing code expires after 15 minutes and works once; no key is pasted into a setup chat. One-link agent approval asks you to sign in, choose permissions, projects and expiry, then approve. The agent still completes pairing. Keys normally expire after 90 days and can be revoked or rotated. The separate show-once Copy key path is for private storage, not chat.

Learn more