# Features

Every feature in Hark, plainly: what it is and why it matters.

## Organize your ideas

Give every idea a clear place, a stage, and enough structure to keep it from disappearing.

### Workshops

**What it is:** A private space for a set of projects — yours, your team's, or one per client.

**Why it matters:** Keeps unrelated work from mixing; the boundary agents and permissions respect.

### Pipeline

**What it is:** Six stages every idea moves through: Vault → Recon → Blueprint → Fabrication → Live → Cold Storage. Shown when you turn on Advanced structure; the simple view keeps to Project, Current state, Decisions and Next action.

**Why it matters:** You can see at a glance where every idea stands, and moving one is a real decision.

### Project page

**What it is:** Each idea is a structured file: Business, Build Docs, Branding.

**Why it matters:** The full stack of an idea lives in one place instead of chats, repos, and folders.

### Completeness %

**What it is:** A completeness score from a checklist you control.

**Why it matters:** Shows what's still missing before an idea is ready to build or share.

### Sparks

**What it is:** A one-line inbox for raw ideas, promotable to a full project later.

**Why it matters:** Capturing takes seconds, so ideas stop dying in group chats.

### Import from a conversation

**What it is:** Paste a ChatGPT or Claude thread, connect a repo, or point at an existing project — Hark proposes a Current state with quotes as evidence, and says "Not found in the source" instead of guessing.

**Why it matters:** Rescues the ideas already buried in dead chats — you start with work, not a blank page.

### Try it free, no account

**What it is:** Paste a conversation or tap the sample and see a proposed Current state before signing up; it carries into your account.

**Why it matters:** You see the result in seconds before committing to anything.

### Board

**What it is:** A drag-and-drop view of the pipeline.

**Why it matters:** Moving ideas between stages takes one motion.

### Search, tags, filters

**What it is:** Find any idea across workshops.

**Why it matters:** Works at 4 ideas or 400.

### Vault gates

**What it is:** Leaving the Vault requires a next action, a kill criterion, and a review date.

**Why it matters:** Forces honesty about each idea before it consumes attention.

### Cold Storage & rotting

**What it is:** Parked ideas live in Cold Storage; stale ones get flagged during review.

**Why it matters:** Your active list stays real; nothing quietly rots.

## Track real progress

Keep the live state, evidence, decisions, and shipped work attached to the project itself.

### Current state

**What it is:** A short, always-current card: phase, what shipped, in progress, next up, blockers, open questions, non-goals.

**Why it matters:** The one screen that answers "where exactly are we?" — for you and for any agent.

### Journal

**What it is:** A dated log of ships, decisions (with rationale), milestones, and notes.

**Why it matters:** Your history survives; the why behind every choice is written down.

### Sessions & handoffs

**What it is:** Each work session ends with a note: what changed, what's next, what to watch.

**Why it matters:** The next person or agent picks up exactly where the last one left off.

### Where did this come from?

**What it is:** Every record shows its source (person, agent, repo, imported chat or doc), its evidence, whether it's accepted, and whether it's still current.

**Why it matters:** You can tell a confirmed fact from an agent's claim at a glance.

### Drafts from repo activity

**What it is:** Commits, merged PRs and releases become an "Inferred from repo activity" draft with each commit linked as evidence.

**Why it matters:** Progress gets recorded even when nobody wrote a note.

### Traction

**What it is:** Define metrics (MRR, users, signups), log values, see sparklines.

**Why it matters:** Numbers tell the story — and become the investor update.

### Links

**What it is:** Repo, live site, staging, app stores, socials, docs on every venture.

**Why it matters:** The project connects to the real thing.

### Growth tab

**What it is:** After launch: a feature pipeline (idea → shipped) and a feedback inbox.

**Why it matters:** The roadmap keeps living after the product does.

### Fork with lineage

**What it is:** Branch an idea into a pivot, spinoff, or v2 with recorded parentage.

**Why it matters:** Ideas become a family tree; pivots keep their history instead of losing it.

### GitHub App

**What it is:** Connect private repos; releases and merged PRs land in the ship log automatically.

**Why it matters:** Proof of progress comes from the code, not from memory.

### Project preview

**What it is:** A live-site preview card and the repo README on the venture.

**Why it matters:** Every idea gets a face without extra work.

## Work with any agent

Make Hark the shared memory layer for whichever AI client is best for the next job.

### Agent hub (MCP)

**What it is:** Claude Code, Codex, Cursor, ChatGPT, Grok, VS Code, Windsurf, Gemini, or your own agents connect to Hark.

**Why it matters:** One shared memory across every tool — models change, Hark persists.

### Agent brief

**What it is:** One call gives an agent everything it needs: state, decisions, blockers, non-goals. Short by default, full on request.

**Why it matters:** Any agent is fully onboarded in one read, without skimming a bloated file.

### Session flow

**What it is:** Start a session, work with tools, end with a handoff.

**Why it matters:** Turns agent work into something the next agent can continue.

### Auto-draft handoff

**What it is:** If a session goes quiet, Hark drafts the handoff from what actually happened.

**Why it matters:** Nothing ends without a note, even when nobody wrote one.

### Venture-locked sessions

**What it is:** A session is bound to one project; touching another requires an explicit switch, and attempts are logged.

**Why it matters:** Context never leaks between your projects.

### Candidate memory

**What it is:** Decisions and state changes proposed by agents wait for your accept or reject, reviewed as a diff with Supersede or Keep both.

**Why it matters:** Agents can propose; only you make something true.

### Trust levels & Autopilot

**What it is:** Per project: Standard reviews everything; Relaxed also auto-accepts list items like Next up and repo drafts; Autopilot (one agent tool, 24 hours, with a banner) accepts everything except decisions, non-goals and phase. Auto-accepted items carry an Auto-approved badge everywhere, including handoffs.

**Why it matters:** Less clicking on routine updates, while decisions — and anything that conflicts with one — always wait for you.

### Accept all from this session

**What it is:** One click accepts every quoted or observed item from a session; decisions, non-goals and phase changes stay as a short list to decide individually. Also linked from the daily digest.

**Why it matters:** Reviewing a whole session takes seconds, not a scroll.

### Supersession

**What it is:** Accepting a new decision can retire a contradicting old one, with history kept.

**Why it matters:** The brief reflects what you believe now, not everything you ever said.

### Attribution

**What it is:** Every agent write shows which agent did it: "via Claude Code", "via Codex".

**Why it matters:** You always know who changed what.

### Personal access tokens

**What it is:** Long-lived tokens for scripts, workflows, and custom agents. Read-only tokens can read the brief and project context but can never write.

**Why it matters:** Headless automation gets in without a browser.

### Connect docs

**What it is:** Step-by-step setup for every supported client, including Grok, copyable as Markdown.

**Why it matters:** Any builder — or their agent — connects in two minutes.

### Installer & hooks

**What it is:** hark init writes hooks and rules into the repo so agents read Hark automatically; in Claude Code and Cursor, stopping a session drafts the handoff.

**Why it matters:** Consulting Hark becomes automatic, not remembered.

### One-click install

**What it is:** Install buttons for Cursor and VS Code, with a web-link fallback.

**Why it matters:** Connecting an editor takes one click instead of a config file.

### CLAUDE.md sync with history

**What it is:** Optionally use the repo's CLAUDE.md as the source. Hark compares both copies before syncing, warns when the repo copy is empty or much shorter, and keeps a version history you can restore.

**Why it matters:** Turning sync on can never silently wipe the context you wrote.

### Repo export (.hark/)

**What it is:** Hark commits HANDOFF.md, DECISIONS.md, and an AGENTS.md block into your repo.

**Why it matters:** The brief lives in git too — it survives even if Hark is unreachable.

### Usage meter

**What it is:** A graph of agent calls by client, with your plan's cap and warnings at 80% and 100%.

**Why it matters:** No surprise limits; you see what counts and when.

## Share and prove

Turn the private working record into controlled proof for clients, investors, communities, and future users.

### Public project page

**What it is:** Publish any project as a read-only page: private, unlisted link, or public.

**Why it matters:** A beautiful, shareable record of the build — investors and communities see it.

### Investor & client rooms

**What it is:** Unlisted projects with a "Investor view" of overview, links, traction, decisions.

**Why it matters:** Show the process, not just the pitch.

### Section control

**What it is:** Choose exactly which sections appear; hidden sections are never sent.

**Why it matters:** Share confidently — private stays private.

### Open Studio

**What it is:** A public gallery of builds happening in the open.

**Why it matters:** Discovery for builders; proof for visitors; distribution for you.

### Follow & digest

**What it is:** Anyone can follow a build; followers get a weekly "what shipped."

**Why it matters:** Builders get an audience; you get a reason to come back.

### Badge

**What it is:** A live SVG badge for READMEs and sites showing stage and progress.

**Why it matters:** Every badge is a backlink and a signal.

### Story

**What it is:** Optional long-form prose on a public project page.

**Why it matters:** Tell the build's story in your own words.

### Progress update

**What it is:** Turn recent journal entries into a ready-to-post update (plain, Markdown, X thread).

**Why it matters:** Build in public without the weekly update chore.

### White-label

**What it is:** Agency plan removes the Hark mark from public project pages.

**Why it matters:** Client-facing pages carry your brand.

### Export

**What it is:** Download a project or workshop as Markdown and files.

**Why it matters:** Your work is yours; leave anytime.

## Work as a team

Give collaborators, reviewers, and clients the right level of access without turning Hark into a task tracker.

### Recipient-first handoff

**What it is:** Hand off to a developer, client or agent: a gap check flags what's missing, the recipient can ask questions, and each handoff is versioned. Recipients can add proposals without a seat or workshop access.

**Why it matters:** The next person continues the work without rebuilding context.

### Roles

**What it is:** Owner, admin, member, and venture-scoped guests.

**Why it matters:** The right people see the right things.

### Guests

**What it is:** Read-and-comment access to specific ventures for clients, advisors, reviewers.

**Why it matters:** Feedback without handing out edit rights or seats.

### Comments

**What it is:** Discussion on any project, live.

**Why it matters:** Decisions get made where the work is.

### Activity log

**What it is:** Everything that happened, by whom or which agent.

**Why it matters:** Full visibility for the team.

### Weekly review

**What it is:** A two-minute screen: confirm next actions, resolve questions, accept agent proposals, park stale ideas.

**Why it matters:** The habit that keeps every idea honest.

### Notifications

**What it is:** Slack, Discord, Telegram, and email on ships, stage moves, decisions.

**Why it matters:** Hark shows up where your team already lives.

### Telegram groups

**What it is:** Link a group chat to a workshop with /link; @mentions and /spark become sparks, /v adds a journal note, and chosen updates post back to the group.

**Why it matters:** Team chat feeds the project without anyone copying things over.

### Capture anywhere

**What it is:** Message the Telegram bot or email your workshop address — it becomes a spark.

**Why it matters:** Ideas get captured the moment they happen.

### Getting started

**What it is:** A checklist that completes itself as you use the product.

**Why it matters:** New users learn by doing, not by reading.

## Trust

Protect early ideas, keep ownership simple, and use standard sign-in instead of another password.

### Private by design

**What it is:** Every workshop is isolated at the database level.

**Why it matters:** Your ideas are never visible to other customers.

### Your data is yours

**What it is:** Hark never trains on your content; export or delete anytime.

**Why it matters:** You can trust it with unlaunched ideas.

### Sign in with Google or email

**What it is:** Standard, secure sign-in; email accounts confirm their address first.

**Why it matters:** No new passwords to manage.