The visual task manager for you and your agent See how ›

Your to-do list is hiding the project.

Flat lists bury how the work fits together. LatticeRun grows your plan as a living tree — every branch a task, every ring filling as you ship — and lets you work it as a Mind map, List, Table, Kanban board or Gantt Timeline.

Point your coding agent at the same tree and it plans the work there: a roadmap it follows, and a progress chart you can read at a glance. You stop asking what it has done — you can see it.

No account needed to start · free plans stay in your browser · export anytime

The LatticeRun mind map in dark mode: a living task tree with progress rings
Why LatticeRun

A task manager you can actually see

Lists hide the shape of your work. LatticeRun shows it — the same tree, from every view.

🫧Progress bubbles

Every task is a bubble with a live progress ring that fills as sub-tasks complete — and drains if plans change.

🔄One tree, six views

Mind map, List, Table, Kanban board, Gantt Timeline and Sprint board are lenses on the same tree. Edit anywhere, drag anywhere — there is nothing to sync, because it is one structure.

🌿Linked projects

Spin any task into its own full project with two-way sync. Perfect for delegating a branch without sharing the whole tree.

🚀Sprints

Give a fortnight a name and a goal, then pull work into it from anywhere in the tree. Columns are derived from your ticks, so there is nothing to keep in sync by hand.

🔒Local-first, then yours to sync

Free plans never leave your browser — no account, nothing on our servers. Turn on a paid plan and your trees sync across your devices and your team, protected row by row so people only read what they are on. Either way, export any project as JSON or the chart as SVG whenever you like, and take it with you.

🤖Agent-ready · MCP

A first-party MCP connector lets Claude Code, Kimi, Hermes and other MCP agents work your trees with a token you can revoke — and holds them to a protocol: claim the branch, plan it, report on it. Most task managers still don't have a connector at all.

↩️Fearless editing

Full undo/redo history, drag-and-drop everywhere, inline rename on any surface. Experiment freely.

🌙Themes & dark mode

GitHub and Vercel-inspired backgrounds, color schemes for day and night, per-task colors, and a focus mode for deep work.

One tree, six lenses

Work the way your brain works today

Switch views mid-thought. Plan visually, execute from a list, review on a board, audit in a table, schedule on a timeline.

🌳

Mind map

The living bubble tree. Drag branches, zoom, focus on one limb, watch rings fill.

List

A fast nested checklist with inline editing, drag-to-reorder and deadline sorting.

📊

Table

A grid for audits — horizontal or vertical layout, rearrange rows and columns freely.

📌

Kanban board

Main tasks as columns, sub-tasks as stickies. Reorder columns and cards by drag.

📅

Gantt Timeline

Every branch on a dated timeline with a live today-line. Day, week and month scales.

🚀

Sprint

A named fortnight with a goal. Pull work in from any branch — the tasks stay where they live.

Who it is for

One tree, three ways of working

The same branching plan, whether it is only you, a team handing work around, or an agent doing the work while you watch.

🧍On your own

Anything big enough to lose track of is really a tree, and writing it as a flat list is what loses it. Break it down once, work from whichever view suits the hour, and see how far in you actually are.

  • A dissertation, chapter by chapter
  • A house move, from offer to boxes
  • A side project you only touch on Sundays

👥With a team

Hand over a branch rather than the whole plan. Spin a task into its own linked project and a collaborator sees just that limb — while progress still flows back into the parent tree.

  • A launch split across design, build and marketing
  • A client workstream kept apart from everything else
  • A fortnight named, given a goal, pulled from any branch

How delegation works →

🤖With an AI agent

Your agent works the tree you already have. It claims a branch before touching it, plans it where you can see the plan, and reports what it built — so a run leaves an account of itself instead of a diff to reverse-engineer.

  • A backlog an agent picks up between your sessions
  • Bugs filed as tasks and closed with a note on the fix
  • A one-line goal broken into a subtree you approve first

How agents connect →

See it in action

Current product screens

Every frame below is from the current LatticeRun app. Open it and explore the same surfaces.

LatticeRun dashboard with progress rings, tags donut and upcoming deadlines
LatticeRun mind map view with progress bubbles
LatticeRun list view checklist
LatticeRun Kanban board view with tags and assignee avatars
LatticeRun table grid view with status pills and totals
LatticeRun Gantt timeline view
LatticeRun files view with attachment thumbnails
LatticeRun per-project chat
LatticeRun dark mode

Dashboard — your day, week, tags and deadlines at a glance

From shape to shipped work

A project workflow that starts before setup

No databases to design, no onboarding weekend. Open the app and give the project a shape.

1️⃣Open the app

Start in the local app without creating an account.

2️⃣Name the branches

Add the workstreams that make the project real — product, design, launch, ops.

3️⃣Break them into tasks

Add subtasks, dates, tags, notes and owners as the plan gets clearer.

4️⃣Pick the view

Plan in the Mind map. Execute from the List. Review on the Kanban board. Audit in the Table. Schedule in the Gantt Timeline.

5️⃣Check the whole tree

The dashboard shows progress, tags and upcoming dates across every project.

6️⃣Put an agent on it

Hand your coding agent a token and it works the same tree — claiming a branch before it starts, laying out the sub-tasks where you can see them, and accounting for each one as it finishes.

Teams & delegation

Hand off a branch, not the whole tree

Assign any task or sub-task in isolation: LatticeRun spins it off into its own linked project, so a collaborator works on just that branch — not the parent plan — and progress flows back into the parent tree. On any mind-map task, focus mode hides every other branch while you work.

AI agents · MCP connector

Your agent has to show its working

Long sessions drift. LatticeRun makes the plan a place instead of a message: an agent claims a branch before it may touch it, breaks the work down before it starts, and says what it built when it finishes — while you watch it happen.

🔒

Claim before you touch

An agent takes a branch and says how it means to tackle it. While it holds that claim, the branch is its to change — and nothing else is. On a strict project, work outside it is refused.

🗺️

The plan, before the code

It breaks the task into sub-tasks first, so they land on your board while you can still steer. You stop finding out what it decided after it has built it.

🟢

Live on the board

A pulsing pill shows which branch an agent is holding right now and its own sentence about what it is doing. Anything it gave up on is flagged blocked, with the reason.

🧠

Memory that survives the session

Every project carries an agent.md brief and a decision log. Both are handed to the next agent before it plans anything — and finishing work without updating the brief builds a debt you can see.

Keeping an agent on the plan Connector docs Why we built it
Pricing

Priced for builders, not budgets

Start free forever. Upgrade when you want sync, AI and teamwork — for the price of a coffee.

Free

$0

Forever · account optional

  • Unlimited projects, saved in this browser
  • All six views + dashboard
  • Themes & dark mode
  • Undo/redo, focus mode
  • JSON & SVG export — your backup

No copy is kept on our servers, so clearing your browser data — or switching browser or device — loses it. Export regularly, or upgrade for cloud backup.

Open the app

Prefer an account? Create one free — it keeps your profile and plan with you. Sync arrives when you upgrade.

Founder Lifetime

$99

One-time · first 200 founders only

  • Everything in Solo Pro
  • Forever — no subscription
  • Founder badge on your profile
  • Vote on the roadmap
  • Our eternal gratitude 🌱

Team Block

$25/mo

Up to 5 seats · $59/mo up to 15

  • Everything in Solo Pro
  • Collaboration & project chat
  • Share a project — or spin off a branch and share just that
  • Task assignment & ownership
  • Team MCP tokens

All paid plans come with a 30-day no-questions refund. Cancel anytime in account settings.

FAQ

Honest answers

Is my data private if there's no account?

Completely. On the Free plan your projects are written to this browser's local storage and never sent to us — we have no copy and no way to read them. You can export any project as JSON (a full backup) or the chart as SVG at any time. Cloud sync is opt-in and only on paid plans.

Can I lose my Free-plan projects?

Yes, and it's worth being blunt about it. Free projects live in one browser's local storage, so they go away if you clear cookies and site data, use "private"/incognito windows, uninstall the browser, or let the browser evict storage when disk space runs low. They also don't follow you to another browser, device or profile. Because we never receive a copy, we cannot restore them for you. Two ways to be safe: export to JSON periodically, or move to a paid plan and let cloud sync keep a server-side copy.

How is this different from Notion, ClickUp or Taskade?

Those are workspaces; LatticeRun is one thing done exceptionally: a task tree with live progress bubbles, seen through six views, that stays out of your way. No databases to design, no setup weekend. Open it, grow your tree, ship.

What is a "linked project"?

Any task can be spun off into its own standalone project that stays in two-way sync with the parent tree. On Team plans you can invite a collaborator to just that spin-off — they never see the rest of your tree.

Can my AI agent use LatticeRun?

Yes — Pro and Team plans include a first-party MCP connector. Point Claude Code, Kimi, Hermes or any MCP-compatible agent at it and it can work your trees directly. Start with Keeping an agent on the plan; the tool-by-tool reference is in the connector docs.

How do you stop an agent going off-plan?

By checking, rather than asking. An agent must claim a branch before it may change anything inside it, and while it holds that claim nothing outside is available to it. Claiming hands it the project brief and the decisions already taken, so it starts from the plan rather than a blank slate; finishing means saying what was actually built. How hard that is imposed is yours to set per project — guided corrects an agent that works out of order, strict refuses it. Agents can read the setting but no tool changes it.

Do I still need Obsidian or a memory tool alongside it?

That's the intent of keeping three kinds of memory in the project itself: agent.md is the standing brief, the decision log holds why things are the way they are, and the Activity feed is what happened. All three are handed to an agent before it plans anything, and finishing work without updating the brief builds a visible debt — so the notes stay current instead of rotting in a second tool.

Who is LatticeRun for?

Solo founders, indie hackers, freelancers and small teams who think in trees but ship from lists. If you've ever drawn a project as branches on paper, this is for you.

Plant your first tree in 10 seconds

No signup. No setup. Just open the app and start growing.

Open LatticeRun →