Every client project, always resumable.
Your team runs Claude Code, Codex, and Cursor across twenty client builds. Hark keeps every one of them ready for the next person or agent — the decisions, the state, the handoff — so delivery hours go to delivery, not reconstruction.
The work you're paying for today
Someone on your team spends hours every week figuring out what was decided, where a build stands, and re-explaining it to the next agent or teammate. That's coordination labor billed against margin. Hark does it — and keeps the record straight across agents.

One workshop per client
Give each client an isolated workshop, then invite unlimited guests into the client room without giving them access to another account. Agent sessions are locked to one project, so context never leaks between clients — an explicit answer to the agency fear that one client's private decisions could appear in another client's build.

Handoffs that write themselves
When a session goes quiet, Hark drafts the handoff from what actually happened. Decisions proposed by agents wait for your review. The next agent reads a compact brief before it starts, and .hark/HANDOFF.md plus .hark/DECISIONS.md are committed to the client's repository so the record ships with the code.

Show the client the build, not a status deck
Give the client a room that shows the current build, decisions, and proof. The ship log becomes the status report; the progress-update generator turns it into send-ready copy; and white-label pages carry your agency's brand instead of another weekly deck.

Hand it off clean
Deliver every decision, document, and asset in one client handoff bundle. The repository carries HANDOFF.md and DECISIONS.md alongside the work, so a client's next builder can resume without a final reconstruction call.

What it replaces
- The weekly status deck.
- The “where were we?” call.
- The re-onboarding when a builder rotates off.

Agency — $100/month
Unlimited client workshops, 8 seats with additional seats at $10 per month, unlimited guests, white-label pages, a cross-client overview, and handoff export.
Common questions
- Can clients see other clients' work?
- Never. Each client workshop is isolated at the database level. Guests see only the client project and sections you share with them.
- Do our agents' notes leak between projects?
- No. Every agent session is locked to one project. Moving to another project requires an explicit switch, and blocked cross-project attempts are logged.
- Can we keep our own branding?
- Yes. White-label client pages are included on Agency, so the client-facing record carries your studio's brand.
- What if Hark is down?
- The handoff lives in the client's repository too. With repo export on, Hark commits .hark/HANDOFF.md, .hark/DECISIONS.md, and a marked AGENTS.md block.
- Who owns the data?
- Your agency does. Export it or delete it at any time.
Start one client workshop today. Keep every build resumable from the first handoff.