Shipped
Resume panel
Open a pad after hours away and Nodepad surfaces the role, last thought, open decisions, questions, and parked items that were active when you left.
Shipped in the workspace resume panel and role picker.
The real problem
Context loss isn't
task management.
Every project switch costs your entire mental stack — the role you were in, the half-decided question, the line of thinking you were holding. Building it back from scratch takes 10–15 minutes you didn't have.
What Nodepad does about it
Saves what you
were thinking.
Open a pad after hours away and the resume panel surfaces the role you were in, the last thought, the decisions still open, the questions waiting, and the items you parked. Your stack rebuilds itself.
Every Nodepad feature must pass one filter: "Does this help the user answer 'Where was I?'" If no, we defer it.
The core feature
Open a pad. The resume panel knows what was running in your head.
When you switch back to a project, Nodepad surfaces a small panel above the workspace: the role you were in, the time since you left, the open decisions, the open questions, the parked items. One click and you're back inside that role — not at the project root.
Type
DECISION: at the start of a sticky and the footer pill auto-labels. BLOCKER: IDEA: QUESTION: PARKED: OUTCOME: — no dropdowns.
- Coming back to a side project after a sprint at the day job
- Re-entering a client retainer Monday morning
- Resuming a research thread after a meeting interrupted you
- Picking up where an AI agent left off via
/context.json
Auth Service Design
DECISION:
JWT Rotation Policy
QUESTION:
Vendor: Clerk vs DIY
PARKED:
DB Migration Design
BLOCKER:
Why Nodepad is different
All features →01
Write markdown.
Get nodes.
Open the markdown panel and write in the format you already know. Headings become sections, bullets become stickies, nested bullets become children. Preview the staged diff, commit. Thirty lines become thirty nodes — no dragging.
# Architecture
## Auth Service
- DECISION: Move to separate service
→ 3 nodes staged · preview diff · commit
## Auth Service
- DECISION: Move to separate service
→ 3 nodes staged · preview diff · commit
02
Any node is
a workspace.
Click into any node and it opens as its own pad — with its own children, its own notes, its own context state. No artificial depth limit: drill as deep as the problem needs, and the resume panel tracks where you left off at every level.
pad › client-retainer › Architecture
↩ Resume: "JWT interval still open" · 18m ago
↩ Resume: "JWT interval still open" · 18m ago
03
One project,
multiple roles.
A client retainer contains Executive, Engineering, Architecture, People management, Vendor evaluation — each a role. Nodepad remembers their state independently. Resume returns you to the last role, not the project root.
Architecture
Vendor eval
Executive ← last
04
Structured memory
for AI agents.
GET /api/v1/nodepads/:short_id/context.json returns role-aware structured state — current role, last thought, open decisions, parked items. Claude Code, Cursor, and any MCP client can read it. No prose parsing.
05
Switch context
from your terminal.
In progress:
inventlist nodepad switch <ctx>/<role>
·
inventlist nodepad resume
·
inventlist nodepad capture decision.
We're wiring capture, switch, and structured summaries into your shell — install works today; polish ships iteratively.
$ inventlist nodepad resume
pad side-project
role Architecture
since 14m ago
2 decisions · 3 questions · 1 parked
pad side-project
role Architecture
since 14m ago
2 decisions · 3 questions · 1 parked
What is shipped vs coming
Each homepage claim carries a status. Nodepad Pro checkout is rolling out on production — pricing is marked Shipping until checkout is fully live everywhere.
Shipped
Write markdown. Get nodes.
Paste an outline or ask AI for a markdown plan, then stage the diff before it becomes a node tree. It stays inspectable before it changes your pad.
Markdown sticky rendering and staged apply are in production code.
Shipped
Any node is a workspace.
Pads are not flat canvases. Every node can open into its own working surface, with children, context, attachments, and handoff paths.
Nested node workspaces, pad switching, and sharing grants are live.
Shipped
Role-aware contexts
Architecture, vendor pricing, people management, and execution can each carry their own state inside one pad. Switch roles without rebuilding your mental stack.
Role switching and context-state persistence are wired in the workspace.
Coming
Structured memory for AI agents
The next agent surface is GET /api/v1/nodepads/:short_id/context.json: role-aware state, decisions, parked items, and boundaries in one machine-readable response.
Today the API exposes /api/v1/nodepads/contexts and /api/v1/nodepads/last_active; the richer per-pad endpoint is the next layer.
Shipping
Terminal workflows for Nodepad
Switch pads, resume state, capture decisions, and read structured summaries from your shell — we're rounding out how Nodepad pairs with the InventList CLI.
Homebrew install is live; pad-centric commands (switch, resume, capture, and sync flows) are shipping — follow roadmap updates as capabilities land.
The actual product
Your pads. Your roles. One workspace.
Every node is a workspace. Click into any of them — it opens as its own pad with its own children, its own notes, its own context state.
Your Nodes
From template
+ Add node
Focus
Morning design sprint — 3h
API review + test pass
No-meeting block · 2pm
People
Junior UX Guide
Closing Thought
Active Threads
Outcomes
Launch nodepad.tools public beta
50 paying users by June
CLI v2 · MCP integration
Speed Template
Projects
One dataset · eight lenses · switch with 1-8 keys
Grid
Cards by area
Kanban
Columns by area
Matrix
Impact × Effort
Mindmap
Interactive tree
Graph
Forces & links
Timeline
Newest first
Treemap
Count by area
◎ People
Andrew
Cameron
email
◎ Speed T.
context
Tree
Outline depth
CLI · in progress
Your context,
from the terminal too.
We're bringing pad switching, resume, capture, and agent-readable summaries into your shell. Install ships via Homebrew today; deeper Nodepad workflows are rolling out — the demos below show where we're headed.
brew install inventlist/tap/inventlist
~/work $ inventlist where
side-project · pad: Architecture (bound)
─ THINK ─
~/work $
side-project · pad: Architecture (bound)
─ THINK ─
DECISION Move auth to a separate service before v0.3 14m ago
PARKED DB migration design — revisit Friday 2h ago
QUESTION does Stripe webhook latency affect e2e? 3h ago
─ BUILD ─
main 2 uncommitted · 4 ahead
─ SHIP ─
#412 Auth split: phase 1 — 6h ago
~/work $
Shipping next
inventlist nodepad resumePad-only snapshot — last thought, role, open decision/question/parked counts. The "Where was I?" verb in its strictest form.
inventlist nextAI picks the next thing to touch — drawing on your roadmap, captures, parked items, and the time you have. Forward-looking sibling to
where.
Not for everyone.
Who it's for →Nodepad is shaped for people who run multiple streams of work and switch mental modes throughout the day — the operator-of-one.
Solo founder · operator-of-one
Wears 6+ hats per day — exec, eng, product, sales, support, family — and loses ~10 minutes rebuilding mental state on every switch.
Resume each role in seconds with the last thought, open decisions, and parked items already surfaced.
Indie developer · open-source
Multiple side projects, research threads, and a day job. Half-finished thoughts vanish between sessions.
Each project is a context. Open the pad → see the last thought + what's blocked + what's parked.
CTO · tech lead
Switches between strategic, architectural, code-review, mentoring, and vendor-evaluation modes throughout the day.
Roles inside one project let you save and restore each mode. Architecture and People carry their own state inside one Nodepad pad.
Consultant juggling clients
Three retainers, a day job, a startup. Every Monday morning is rebuild-the-mental-map mode.
Each client is a context. ⌘K switches in. Resume panel shows what was open at last close.
AI coding agent · MCP client
Agents need structured context to continue from. Free-form notes are unreadable.
GET /context.json returns role-aware structured state. Agents know what was decided, what's open, what to leave alone.
What Nodepad is not
A category
of one.
Nodepad is in a category of one. It's easier to define by what it isn't.
Nodepad is a context recovery and execution memory tool. Built for builders, teams, and AI agents who lose context every time they switch.
- ✕Not a notes app
- ✕Not a mind-mapping tool
- ✕Not a Milanote clone
- ✕Not a Notion alternative
- ✕Not a generic productivity dashboard
- ✕Not a full project management tool
- ✕Not a heavy task manager
- ✕Not a place where everything goes and nothing moves
Simple pricing
One tool.
One price.
Monthly
Annual
Save 40%
Free
$0
/ forever
Get started, no credit card.
- Unlimited pads
- 30 AI credits / month
- Resume panel
- CLI / terminal workflows (shipping)
- Context JSON endpoint
- 5 exports / month
- — Priority support
Pro
Shipping
Nodepad Pro
$5
$3
/ month
or $36 / year — save 40%
- Everything in Free
- 200 AI credits / month
- 50 exports / month
- Priority support
- Early access to new features
- Agent context history (90 days)
- Team sharing (coming soon)
Stands alone. Composes with the rest.
The InventList
family of tools.
Nodepad has its own domain, CLI integrations we're finishing, and an agent surface on the way. Use it without an InventList account. When you use the family, the seams disappear.
nodepad.tools
Context recovery + execution memory. Where was I?
nodepad.tools ← you are here
planpad.
Public roadmap, markdown source of truth. Ship in public.
inventlist.com/tools/roadmap
inventlist.
Home for indie makers running the full loop.
inventlist.com
localvault.
Local-first secrets vault. CLI-native, zero cloud.
inventlist.com/tools/localvault
Ready to resume?
Stop rebuilding
your mental stack.
Save the role. Save the thought. Resume in seconds.