Open
Done
Needs Changes
Abandoned
Copied to clipboard
TasksApp — VibePad
Saved
How to use
CORE WORKFLOW
INSTRUCTIONS
SYNC & SHARING
EDITOR REFERENCE
How VibePad Works
VibePad follows one loop: Capture → Send → Prompt Pool → Validate → Repeat. You plan the work, your coding agent builds it, and you validate the result before it counts as done.
Capture
↓
Send
↓
Prompt Pool
↓
Validate
↓
Repeat
Capture
Add and organise tasks inside your projects as ideas and requirements come up — a task doesn't need to be fully specified before you create it. VibePad's Web and PWA versions are especially useful for capturing and organising work from any device, ready to hand off later.
Send
Context and tasks are separate. On Desktop: Send Context puts your VibePad/Global/Project Instructions into the terminal (you press Enter when ready), then Copy to Pool moves the tasks themselves into the Prompt Pool and copies them to paste in. On Web/PWA, Copy to Pool alone covers both — paste the result wherever your agent runs.
Prompt Pool
The Prompt Pool is not just a queue of tasks waiting to be sent. Tasks sent for implementation move to the Prompt Pool and stay there until you validate the result.
VibePad remembers each task's original section, however it reached the Prompt Pool. Marking it Done returns it automatically to that original section, marked complete.
Human Validation
The coding agent finishing its work does not mean the task is complete — you validate the result. Test or review the implementation, then choose Done or Needs Changes.
Done
Means you've validated the implementation. VibePad returns the task to its remembered original section, marked complete.
Needs Changes
Means the implementation didn't fully pass validation and needs more work. VibePad adds a follow-up note underneath the task — describe what still needs to change there. The task stays part of the Prompt Pool/follow-up workflow until you send the correction back to your coding agent. Previously called "For Review" — same behaviour, clearer name.
Follow-up Numbering
A Needs Changes follow-up gets a decimal number based on the original task.
Original task13
First follow-up / correction13.1
Second follow-up / correction13.2
13.1 is not an unrelated new task — it means task 13 was previously implemented but still needed a correction after validation. The same applies to each further decimal.
Instructions
VibePad Instructions — automatic, built-in instructions that explain VibePad-specific conventions (like follow-up numbering) to your coding agent. Nothing to configure.
Global Instructions — optional, apply across all your projects. Good for general working preferences and conventions you want followed everywhere.
Project Instructions — optional, apply only to that project. Good for that project's architecture, context, or constraints.
When you send tasks, VibePad composes them together:
VibePad Instructions
+
Global Instructions
+
Project Instructions
+
Current Tasks
TERMINAL
PLATFORMS
Send Context
Pastes only your coding-agent context — VibePad Instructions, plus Global and Project Instructions if you've set them — into the active project's terminal. It never includes pending tasks, never moves anything to the Prompt Pool, and never presses Enter for you. Use it whenever the agent's context needs (re)establishing: a new session, after /clear, switching agents, or any time you want to resend it — VibePad doesn't try to guess when that is, you decide.
Terminal & Auto-start Agent
Each project can use its own terminal Working Directory. The terminal is a real local shell — run coding-agent CLIs like Codex or Claude directly, or anything else you'd normally run there.
Auto-start Agent can optionally launch a configured command automatically whenever a new terminal session opens for a project. VibePad only launches it — it does not manage or monitor the agent afterward. Send Context always stays a deliberate action you take.
Web/PWA vs Desktop
Plan anywhere. Build on desktop.
Web and PWA are best for capturing ideas, organising tasks, editing Instructions, and accessing your synced projects — no install required.
Desktop adds a local project Working Directory, an integrated terminal, optional Auto-start Agent, and the direct Send Context workflow.
Sync
Sign in with Google to keep your VibePad projects available across devices.
Advanced/self-hosted users can instead connect their own Worker and sync token — this remains fully supported. Find both options in Settings → Sync.
Sharing
Share a project with a collaborator from the share icon in the header. A shared project syncs live between everyone invited, the same way your own synced projects do.
Structure
Type # then a space to make a line a section title. Tab at the start of a task indents it into a note; Shift+Tab promotes it back.
Status
Click the circle to cycle open → done → needs changes → abandoned. Marking something as needing changes adds a follow-up note underneath.
Open
Done
Needs Changes
Abandoned
Reordering
Drag the grip on the left of a line. Dragging a title moves its whole section with it.
Copy to Pool
Copies everything not done or abandoned, grouped by section, and moves it to the Prompt Pool — ready to paste anywhere, including into a coding agent running outside VibePad. The caret menu splits every copy into two independent choices: Copy (clipboard only, nothing moves) vs Copy to Pool (also moves the tasks), and within each, Tasks only vs With Context (adds VibePad/Global/Project Instructions before the tasks — the same composition Send Context uses). On Desktop, Send Context is also available (Instructions only, no tasks, pasted directly into VibePad's own terminal).
Shortcuts
Undo / redoCtrl+Z / Ctrl+Y
New title# + space
Indent to noteTab
Promote to taskShift+Tab
Line optionsRight click
Saving
The disk icon saves to the remembered file, Save As always prompts, and the folder icon opens a file into a new project. Autosave writes to the remembered file on a timer once one exists.