What shipped

Trust levels, Autopilot and one-click session approval

Each project picks how much agents approve on their own (Standard, Relaxed, or a 24-hour Autopilot per agent tool), marked Auto-approved everywhere. Decisions are never auto-approved, and anything that clashes with one waits for you. "Accept all from this session" clears the rest in one click.

CLAUDE.md sync can't overwrite your work

Before syncing, Hark shows both copies side by side and keeps a version history you can restore from. Repeated Current state items now merge into one.

Stop = handoff, drafted from repo activity

When a Claude Code or Cursor session stops, Hark drafts the handoff from commits, PRs and releases. Recipients can mint a read-only tool key, and owners get one daily digest when suggestions pile up.

Plain language everywhere and a clearer project page

One vocabulary across the site, spaced-out desktop menu, project page reordered: documents, Current state, repos, links, activity. GitHub sign-in removed; sign in with Google or email.

Sign-in is Google or email

GitHub sign-in is gone because the sign-in service doesn't support it. Linking repos, repo activity and the .hark/ export work exactly as before.

Try Hark without an account

Paste a conversation, or tap the sample, and see a proposed Current state before signing up; it carries into your account. Anonymous AI use sits under a daily spend cap.

Connect your tools, bring in your work

Add to Cursor and VS Code, one-step repo linking with export on by default, and a simple view showing just Current state, Decisions and Hand off. Paste to Current state now takes about 19 seconds.

Handoff recipients can continue without a seat

Someone who signs in from a handoff gets access to that one project and can add proposals you review. No workshop membership, no seat used, revocable anytime.

Read-only tokens can read the brief

Read-only personal access tokens can now fetch the brief and list projects. Their sessions can never write, and any write is refused naming the token's scope.

Nothing is agreed until you agree it

One onboarding path, no "Agreed" label without an approval, and "Accept all quoted" takes only items tied to an exact passage or commit. Checklist labels now say exactly what was verified.

Stage One: one complete handoff

Every record now carries its source, acceptance, applicability and scope; recover a project from a conversation, repo or existing project and review it as a diff. Handoffs are recipient-first, with a gap check and a questions loop.

Your handoff, committed to your repo

Turn export on for a linked repository and Hark writes the brief into the code itself, so it survives even if Hark is unreachable.

• .hark/HANDOFF.md and .hark/DECISIONS.md are committed from your accepted Current state and decisions
• An AGENTS.md block between markers — anything you wrote around it is preserved
• Fires on a clean end_session and when you accept a Current state change, debounced so it never spams commits
• Export now, a branch choice, last-export time, and a downloadable .hark bundle in the repository panel

The handoff is no longer optional

Four changes that stop context leaking between projects and stop agent memory entering your project page unreviewed.

• Venture-locked sessions: an agent on V-004 can't touch V-009 without switch_venture, and blocked attempts are counted
• Auto-drafted handoffs: a session that goes quiet gets a handoff drafted from what actually happened
• Candidate review: decisions and state changes proposed by agents wait for your accept, edit-and-accept, or reject
• The brief is compact by default — phase, next action, last decisions, blockers, non-goals — with depth=full on request
• Kill criteria and non-goals on Current state, plus stage gates before an idea leaves the Vault
• Context leaks blocked this month, shown in workspace settings

Usage graph and cap warnings

See agent calls per day against your plan allowance, and hear about it before you hit the ceiling.

• Daily agent-call graph in workspace settings, billing and connections
• One email to workspace owners at 80% and one at 100% of the monthly allowance
• Nothing is deleted at the cap

GitHub App, connect docs, and personal access tokens

Link a repository to a project and let scripts and headless agents in without a browser sign-in.

• Install the Hark GitHub App and link repositories per project; pushes, pull requests and releases show as activity
• Personal access tokens for scripts, cron jobs and workflow tools, with per-token attribution
• Setup guides for Claude Code, Claude, ChatGPT, Codex, Cursor, VS Code, Windsurf, Gemini CLI and headless clients

Current state, agent sessions, and the agent brief

The living half of a project: where the build actually stands, and one call that hands it to any agent.

• Current state: current phase, summary, in progress, next up, blockers, open questions
• Agent sessions with attribution — which client read the brief, which client saved the handoff, and when
• get_agent_brief composes the project page and living state into one ordered read
• Session-without-handoff flagging with a reminder to copy

Open Studio, following, and build badges

Publish a project, gather followers, and show the build off wherever your code lives.

• Public project pages at /v/<slug>, listed in Open Studio
• Follow a build and get notified when its owner logs a ship
• An SVG badge and generated social preview for READMEs and site footers
• Comped accounts for partners and early supporters

Search and agent discovery foundations

Hark is now readable by search engines, answer engines and agent directories: server-rendered content pages, structured data on every public route, an llms.txt surface, Markdown mirrors of the docs and published MCP metadata.

• New audience pages for AI builders, indie hackers, agencies and founders
• Honest comparisons against Notion and Linear, plus an MCP context hub explainer
• /llms.txt and /llms-full.txt, and a .md mirror of every docs page
• /.well-known/mcp/server.json describing the hosted Hark MCP server
• Public changelog with RSS, and IndexNow pings when a public project page changes

One-command installer and the resumed-work metric

Setting up the session flow in a repo is now a single command, and Hark measures whether a different agent actually picked the work back up.

• curl -fsSL https://harkstudio.io/install.sh | sh writes a Claude Code SessionStart hook, a stop reminder, a Cursor rule, an AGENTS.md block and a .hark file
• Current state cards show the last brief read and last handoff, with the client and time
• Sessions that never closed with a handoff are flagged after six hours
• Resumed-handoff counts and a weekly one-question survey for beta workshops

Slack, Discord, Telegram and email capture

Ideas and progress can now reach Hark, and leave Hark, without opening the app.

• Slack and Discord webhooks with event filters and a test button
• Up to five signed outbound webhooks per workshop, with retries and a delivery log
• A Telegram bot that turns any message into a spark, with /w and /v commands
• A per-workshop inbound email address that turns mail into sparks
• Per-user notification preferences for mentions, reviews, trial reminders and digests

Weekly owner review and progress updates

A two-minute weekly pass over every active project, and a quick way to tell people what changed.

• Pick a weekly review day and time per workshop; email and in-app reminder
• One screen per active project: confirm or replace the next action, resolve or defer the open question
• Answers write back to Current state and add a milestone journal entry
• Projects untouched for 14 days show as going cold, with one-tap Cold Storage
• Copy a progress update in plain text, Markdown or an X thread, plus an investor update preset

14-day trial, no card

Every new workshop now starts with a free 14-day trial and no payment details. Solo builders start on Builder, teams on Studio.

• No checkout at signup
• At day 10 and day 13 you see your own proof — projects created, handoffs completed, agents connected
• At trial end without payment the workshop becomes read-only; nothing is ever deleted
• Builder includes one comment-only client guest, scoped to a single project

Start from work you already have

Two ways into Hark that both end in a verified handoff, instead of an empty workshop.

• Import from a conversation: paste a ChatGPT or Claude thread and review a drafted project, decisions and Current state
• Set up from your repo: an agent reads the project and proposes the whole project page in one tool call
• A Prove the handoff step that completes when a second client reads the brief correctly