Handwriting still matters for slow thinking, reflection, and the kind of notes you want to sit with. But quick things need a different kind of surface: a task before it disappears, a link with just enough context, a pasted quote, a follow-up, a reusable line, or a half-formed idea that is not ready to become a document.

The first goal was simple: replace the scramble for paper or another throwaway note when something small needed to land fast. Quick Capture, Inbox, checklist lines, snippets, and rough Markdown-friendly items came from that need.

As the work changed, root started becoming something more useful too: a context tool for AI and human handoffs. It gives working notes, tasks, source links, reusable prompts, and project memory a place to live before you decide what to send to another person, a doc, ChatGPT, Gemini, Claude, or any other tool.

What root believes

Capture before organization. The first job is to get the thought down.
Rough material is real work. Messy text still deserves a place to live.
Tasks belong near context. The note that explains the task should stay close.
Handoff should be deliberate. Copy, share, or export only when the work is ready.

What root is for

root is for quick capture, rough notes, links with context, checklist lines, reusable snippets, prompt fragments, open tasks, project context, and Context Handoff. It helps collect and shape active text before that text becomes a finished document, calendar event, shared task, long-term note, or clean packet for another person or tool.

If you are using AI tools, root's role is still modest: keep the working files and repeat instructions close, then choose the packet you actually want to share. A practical starting point is Start with about-me.md.

Get it down before it gets away.

Some things become docs, calendar events, shared tasks, polished notes, or messages. Some things only needed a calm place to live while you worked through them.

Local by default

root does not require a root account or a root server. Your workspace starts on your device. You choose when to copy, export, share, or connect another service.

What root is not

root is not trying to replace every tool. Calendars, documents, shared project systems, archives, and polished publishing tools still matter. root is the private working layer before those tools, and sometimes the quiet place where the work can stay.

What to expect during beta

Feedback is most useful when it keeps this shape in mind: fast capture, simple sorting, visible tasks, reusable snippets, private local storage, manual export, and controlled handoff. If a feature makes root feel heavier than the work requires, that matters too.

Questions or thoughtful feedback? Email [email protected].

Start with the Chrome beta. No account required. Your workspace opens right in the browser.
Add to Chrome