A walk through the workspace

The whole job.
In view.

The brief. The agents. The fixes. The proof.
See how the pieces of Lispa work together.

Three Lispa egg agents bring their work to a shared project table.
Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models

Actual Lispa interface. Fictional demo projects and amounts.

01 / Projects & releases

Give the whole job a home.

A release has a brief, a pile of fixes, and evidence to collect. Keep them in one project. See what changed, what is still running, and where Lispa needs your decision.

Try it: coordinate a release, prepare the fixes, and bring back the test evidence.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa project overview with a fictional storefront launch, remaining work and results.
Actual Lispa interface · Fictional demo dataView full size
02 / Chats & agent teams

Several conversations. One shared goal.

Give a focused piece of work to each agent. Follow the coordinator, the build, and the checks from the project. Open a work session when you want to give more direction.

Chats can share a cloud machine. The terminal, files, changes, artifacts, and browser stay close to the work.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa work-session list with a coordinator and fictional build, test and review teams.
Actual Lispa interface · Fictional demo dataView full size
03 / Tasks & bug fixes

Turn the backlog into work you can follow.

Break a broad request into focused tasks. Keep dependencies, active work, and results in view while agents investigate bugs or work through failing checks.

Try it: reproduce a failure, prepare a focused fix, and add a regression check.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa task list grouped by progress, review and completion with fictional tasks.
Actual Lispa interface · Fictional demo dataView full size
04 / Pull requests & follow-up

Stay with the change through review.

Inspect the change, the latest agent review, and the CI checks together. Ask Lispa to follow up on new commits, address feedback, and keep checking the result.

Your instructions set the scope, including when approval or merging is allowed.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa pull-request workspace with fictional changes, checks and a review result.
Actual Lispa interface · Fictional demo dataView full size
05 / Browser testing & evidence

Ask for a result you can inspect.

A finished task should bring back more than a message. Ask for the relevant tests, a browser check, and screenshots of what changed. Keep the evidence beside the delivery.

Check the real flow, including the phone layout, before deciding what is ready.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa delivery-review interface showing a fictional payment fix, verification evidence and review controls.
Actual Lispa interface · Fictional demo dataView full size
06 / Scheduled & event-driven work

Give the repeat work a routine.

Review new changes or run a maintenance pass on a schedule. Each automation keeps its instructions, trigger, runs, and project together. Pause the routine when you need to.

Try it: look for updated pull requests, review the new commits, and keep a record of each run.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa automation interface with fictional pull-request review and scheduled maintenance routines.
Actual Lispa interface · Fictional demo dataView full size
07 / Agent rules

Explain your way of working once.

Set the conventions you would otherwise repeat in every chat: how to review code, which checks matter, and what needs your approval. Keep rules personal or share them with the team.

Use global rules for your defaults and repository rules for the details of a particular codebase.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa agent rules with fictional shared review and checkout conventions.
Actual Lispa interface · Fictional demo dataView full size
08 / The shared brain

Leave useful knowledge for the next task.

Keep repository facts, lessons, and reusable commands connected. Let the next piece of work start with what the team has already learned.

Explore the stored knowledge and its relationships, from a testing convention to a reusable verification command.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa brain view with fictional repository facts, lessons, operators and their relationships.
Actual Lispa interface · Fictional demo dataView full size
09 / Models & routing

Keep your models. Choose how they work.

Use supported connected plans or API keys, or Lispa’s models with credits. Let automatic routing choose model power and reasoning effort for a turn, or keep the model you picked.

Set a default and adjust individual sessions. Provider limits and Lispa service charges still apply.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa routing settings showing the automatic model-routing control.
Actual Lispa interface · Fictional demo dataView full size
10 / Usage & savings estimates

See the cost alongside the work.

Follow usage over time, session counts, and estimated routing savings. Open the account view to understand where credits went and how the work adds up.

The amounts shown here are fictional. Routing savings compare API-price estimates; they are not bills or promised savings.

Works with
  • Claude
  • Codex
  • Grok
  • Gemini
  • Open models
Actual Lispa usage view with fictional daily credits, sessions and routing estimates.
Actual Lispa interface · Fictional demo dataView full size
Built in Lispa, used in Lispa

The product works on itself, too.

This dashboard was built in Lispa. The screenshot renders the delivered component with fictional counts. It is one example of the work an agent can bring back for you to inspect.

See the feature development workflow →
Lispa dashboard built in Lispa, displayed with fictional demo counts.
Start with one real piece of work

What would you like
off your plate?

Connect a repository. Give Lispa a clear goal.
Come back to work you can review.

Start with Lispa →

From $20/month with $20 in usage credits.
Paid plan required to run tasks.