← Vesper

VESPER · WORK

Put it to work.

LANCER WORK turns the conversation into a session inside a folder. Vesper reads the code, makes a plan, edits files, and runs commands and tests in a sandbox until they pass. Every change can be undone, and anything that would leave the sandbox waits for you.

SEE IT WORK

From one sentence to a passing test suite.

A small ledger app, one request, and every step on screen. Click a step to jump to it.

HOW IT WORKS

An engineer that works where you can see it.

Five things that make long tasks safe to hand over.

A session in a folderPick a folder; the chat becomes the project
A sandboxWrites only the workspace, no network by default
Undo anythingCheckpoints before every edit
A shared terminalYou and it on one screen
Teacher, peers, helpersExplain, review, work in parallel

01

Pick a folder, and the conversation works in it.

Choose a workspace beside the input box, or start a new one, and the conversation becomes that project’s session. Its words stream in, each tool call and each diff appears in the conversation, and every file it touches has an Open button: Word, Markdown, PowerPoint and LaTeX open in LANCER WORD, LANCERPOINT and LANCER TEX.

A status line shows steps, context, cost, model and reasoning, with buttons for changes, undo, files, terminal, and the teacher and peers. Every session in the folder is kept, old and new, and you can switch between them.

02

A sandbox, and rules you write.

Commands run in a sandbox: they can change only the workspace, cannot reach the network unless you allow it, and cannot read your keys. Version-control folders and hook settings are read-only inside it. If a command needs to leave the sandbox, it asks.

Choose how approvals work: ask every time, automatic with a reviewer checking routine steps, or hands-off. Some things always ask: sending in your name, spending money, deleting, irreversible actions and commands on servers. Write your own rules too: “git push, ask me”, “.env, never read”.

03

Every change can be taken back.

Before each edit the original is recorded. Undo the whole task, or go back to before step five. In a git repository, a hidden snapshot is taken before each step, so files that commands created, changed or deleted come back too, without touching your branches or staging area.

You can also rewind the conversation: pick something you said, and roll back the code, the conversation, or both, then edit what you said and send it again.

04

A real terminal you share.

Open the terminal and you both use the same screen, inside the same sandbox. You can type and press Ctrl-C; it can read the screen, type a line, press keys and wait for text to appear. REPLs, installers that ask questions, editors and long-running servers all work.

Long commands move to the background instead of being killed, and it is told when they finish. Things with an interface are opened in a built-in browser and played until they work.

05

A teacher, peers and helpers.

The teacher shares the task’s context and only explains: ask what a step is doing and why, for a beginner or an expert. Up to four peers, such as a reviewer, a tester or a security engineer, read along and speak when they have something to add; what they say reaches the next step.

It can send helpers to work in parallel, each with its own model if you like. A coding task can also be handed to the official Codex command line on your computer, inside Vesper’s sandbox, with every step shown in the task.

Anything that leaves the sandbox waits for you.LANCER WORK

A WORKED EXAMPLE

Fixing a bug before lunch, without watching the whole time.

You describe the problem, approve one command, and come back to a passing suite.

You say
Exports break when a category has a comma in it. Fix it, add a test, and keep the old output format.
What happens
  1. Reproduces it

    Writes a failing test with “Food, drinks” first.

  2. Fixes the writer

    Switches to the csv module with quoting for text fields.

  3. Asks once

    A package needs the network; you allow it for this task.

  4. Runs until green

    Twelve tests pass; the old output is byte-for-byte the same.

  5. Hands it back

    A card with the changed files, an undo button and the cost.

What you get
DIFF

Three files changed

export.py, cli.py and a new test, each with its diff.

TEST

12 passed

Including the case that used to break.

UNDO

A way back

Undo the round, or any single step, at any time.

WHAT IT DOES

What a careful engineer would want.

Work until it passes

Give it a check command and it keeps fixing until the check passes.

Code review

Issues with severity, file and line; tick the ones to fix and it fixes them.

Your conventions

AGENTS.md and rule files are read, including ones scoped to a folder.

Skills and commands

Type / for built-in commands, your own commands and every skill you have enabled.

Cost in view

Cache hit rate and estimated cost on the status line, all the time.

Steady under load

Rate limits switch to a backup model, wait and retry, and pause rather than fail.

WHAT YOU KEEP

Changes you can read, and a way back.

Everything happens in your folder, as ordinary files and commits you control.

DIFF
Diffs for every step

Coloured, line by line, on the timeline.

CKPT
Checkpoints

Undo the task, a round or a single step.

MD
AGENTS.md

Conventions it learns from you, written where your tools can read them.

LOG
A full record

Every step kept and searchable, even after the context is compressed.

The sandbox is the default, not an option.

  • Commands can only change the workspace and cannot read your keys.
  • No network unless the workspace allows it; leaving the sandbox always asks.
  • Sending in your name, spending money and deleting always ask, whatever the approval mode.

Pick a folder. Ask for one fix.

LANCER WORK is part of Vesper, a personal AI in development for Mac, Windows and the web.