Prepared Work

Ask ChatGPT Ask Claude

Prepared Work is Vaner's main user-facing surface. It's a small feed of evidence-backed cards Vaner prepared during idle time, ready to inspect when you ask. Each card answers four questions:

What did Vaner prepare?
Why did Vaner prepare it now?
What evidence supports it?
What safe action can I take?

Vaner intentionally shows few, strong items. Candidate, hidden, stale, and superseded artefacts stay out of the feed.

What can appear

Review notes
Bug hypotheses
Docs drift notes
Virtual diffs
Research briefs
Ready prediction-backed drafts

Actions

Each card carries server-authoritative actions. Clients render only what Vaner returns:

Inspect. Full rationale, evidence, warnings, preview.
Export. Vaner-owned content (markdown, patch payload).
Adopt. Use a ready prediction as your current intent.
Dismiss. Hide from the feed.
Feedback. Record useful / partial / irrelevant / wrong.

Export and adopt are explicit. Vaner never silently applies patches or edits project files.

Virtual diffs

Patch-shaped Prepared Work. Stored, not auto-applied. They include the target files, source snapshot, rationale, evidence, and export payload.

A virtual diff goes stale when its target files no longer match the recorded snapshot. Stale diffs block export until regenerated.

Inspecting Prepared Work

The cockpit is Vaner's local control surface. Start it with:

vaner up --path .

Default URL: http://127.0.0.1:8473. Same Prepared Work feed as the desktop app and any MCP client; UI-safe by default with a diagnostic toggle.

Useful endpoints for scripted checks:

GET /prepared-work
GET /work-products
GET /work-products/{id}/inspect
POST /work-products/{id}/export

Watch the live event stream:

vaner watch --cockpit-url http://127.0.0.1:8473

Long-horizon mode

vaner deep-run start opens a longer session biased toward "what will matter tomorrow?" instead of the daytime "what's likely next?" loop. Pairs with the Deep Research bundle.

Deep-Run prepares; it does not act. Drafts queue for human adopt / discard. Nothing ships, sends, or commits without an explicit confirmation.

vaner deep-run start
vaner deep-run start --preset aggressive --duration 480 --cost-cap 5
vaner deep-run status
vaner deep-run stop

Bundle defaults pre-fill the session. See Configuration for the per-session knobs and Policy bundles for each bundle's deep_run_profile.

A goal is a long-horizon intent in your workspace ("ship the new auth middleware"). Goals persist across daemon restarts and survive individual prompts. Each carries a status (active / paused / abandoned / achieved), related files, and a reconciliation state.

Declare and inspect goals from any MCP-aware client:

vaner.goals.list
vaner.goals.declare
vaner.goals.update_status
vaner.goals.delete

Or browse them in the cockpit's Goals view.

When the repo changes, Vaner reconciles each goal's linked artefacts against the new state. A goal whose evidence has gone stale gets demoted; one that gains confirming evidence gets promoted.

HTTP and MCP

HTTP:

GET /prepared-work
GET /work-products
GET /work-products/{id}/inspect
POST /work-products/{id}/export
POST /work-products/{id}/dismiss
POST /work-products/{id}/feedback

MCP:

vaner.prepared_work.dashboard
vaner.work_products.list
vaner.work_products.inspect
vaner.work_products.export
vaner.work_products.dismiss
vaner.work_products.feedback

The default dashboard hides internal lifecycle and ranking fields. Diagnostic clients can opt in.