Developer
Bugs, feature requests, open tasks, quick captures from docs, and a clean context packet when you want help on the exact slice of work you are in.
- Inbox
- Bugs
- Feature requests
- Ideas
Chrome extension beta
A private-by-default scratchpad and workspace for working text. Use Quick Capture and Inbox for fast intake, pull out tasks from plain text, reuse snippets, and copy only the context you actually want to share.
Why root
root is not trying to be a giant note archive. It is a lighter work surface for rough notes, pasted research, links, tasks, project rules, quick captures, and the reusable text you keep reaching for while work is still moving.
If you just want a fast local notepad, root is good at that too. It just gives working text a little more structure without turning into a heavy system.
Use Inbox when you do not know where something belongs yet. Quick Capture gives that same intake flow a tiny extension surface, and you can drag one or more .md or .txt files straight onto the workspace when the text already exists somewhere else.
Task lines, Clean View, tags, and snippets help rough text become useful working context without forcing a database or project manager onto it.
Copy Context opens Context Handoff so you can preview exactly what leaves root before you copy it, save it, or use it with browser AI workflows.
Workflow
Use the Copy Context action to open Context Handoff, then choose the current item, selected items, the current project, pinned context, or open tasks. Preview the bundle first, keep or remove metadata, and switch to links only when the references are the real payload. In some browser setups, the visible packet itself can be enough to work from without a separate paste step.
root keeps the organization shallow on purpose. Use Quick Capture and Inbox for intake, tags as lightweight projects, Open Tasks as the live checklist rollup, and Snippets for reusable text that should not clutter the main list. Quick Capture is the part that lets you save something while you are still on the page you were already using.
That means the capture step is not theoretical. It is a small real tool that drops text into the same workspace where you sort it later. If you prefer root on demand instead of on every new tab, turn on redirect mode in Quick Capture and use one stable workspace tab.
Examples
root makes the most sense when you can picture the actual items sitting in the sidebar. The structure stays light, but the shape changes depending on what kind of work you do.
Bugs, feature requests, open tasks, quick captures from docs, and a clean context packet when you want help on the exact slice of work you are in.
Keep hooks, script fragments, sponsor notes, links, and posting checklists together without turning the whole thing into a giant content system.
Catch quick requests, prep notes, travel details, and follow-ups in one local workspace, then use Open Tasks and Copy Context to keep people aligned.
Use root for lecture dump notes, assignment checklists, research links, study prompts, and all the rough text that shows up before things feel organized.
Principles
root should make sense even if you never paste into an assistant. root keeps your workspace local and is explicit about what it sends. Browser-level AI features still follow the browser's own sharing rules, so the same features that help you manage working text locally also make sharing calmer and more intentional when you do want to send something somewhere else.
Explore more
If you want the details behind the workflow, these are the best next stops.