This walkthrough takes you through your first VibeSpace task. Before starting, make sure you have installed the app and configured at least one model provider.
1. Create a task and authorize a workspace
- Open New Task in the sidebar;
- The first time, pick a folder to authorize as the workspace (practice on a test project first);
- Use the toolbar under the input box to adjust:
- Permission mode: keep the default "Auto approval", or the more conservative "Request approval";
- Model / backend: pick a configured API model or an installed CLI backend;
- Experts & skills: optional. For example, enable the built-in
review-codeskill so the agent follows a review checklist.
2. Describe your goal
Write what you want in plain language, adding constraints and acceptance criteria when useful. The input box supports:
- Enter to send;
- Shift+Enter for a new line;
- ↑ / ↓ to browse previously sent drafts;
- File and image attachments (images need a vision-capable model).
A well-structured task description:
Goal: add workdaysBetween(start, end) to utils/dates.ts that returns
the number of weekdays between the two dates (excluding weekends).
Constraints: follow existing code style; no new dependencies.
Acceptance: add unit tests, make them pass, and summarize the pnpm test output.3. Watch the run
Once the task starts, the timeline shows every step:
- Tool cards: browse, search, read, edit, write, and command calls with parameters and results;
- Output stream: the model's reasoning and replies, as they stream;
- Context panel: token usage and compaction status for the session.
4. Handle approvals
When the agent requests a protected operation (writing a file, running a command), an approval card appears:
- Approve to let that step proceed;
- Reject — the agent receives the rejection and adjusts its plan.
In "Auto approval" mode, low-risk operations run without asking; high-risk ones always ask. Your decisions within a run are remembered — after an app restart and recovery, previously approved steps are not asked again.
5. Review changes and accept
When the task finishes, open its change view:
- See the task-level change summary and per-file diffs;
- Restore anything you dislike (preflight first, then confirm) to revert files to their pre-task state;
- Keep what you like directly in the workspace. VibeSpace never runs git commit / push — committing stays in your hands.
6. Intervene at any time
- Cancel a running task; changes made so far remain in the ChangeSet;
- Quit and come back: run state and checkpoints persist, so the app can resume from where it stopped (see Recovery & context).
Next steps
- Learn the details of permissions & approvals;
- Capture your team's workflows as skills;
- Try summoning experts & expert groups for bigger jobs.