AGENTS, WITH A PLACE TO WORK

Good work.
Multiplied.

A goal, a team, a schedule, or a signal. Put agents to work, see every handoff, and keep the decisions that matter in your hands.

A panda foreman in a green hard hat and vest, holding a clipboard and directing the crewThe Locus panda reading a bookA panda teammate sitting with a laptop
ONE PLAN. A FEW GOOD PAWS.
CHOOSE HOW THE WORK HAPPENSILLUSTRATIVE WORKFLOW

In Locus 2.7, the composer keeps Work, Plan, Grill, Goal, Task Capsules, and Solo or team options in one workflow menu. Your draft stays right where you left it.

YOUR GOAL

Find the failing test.
Fix the cause.
Prove it works.

A real workspace. A reviewable result.

Give each part to the right mind.

Configure a dispatcher and named specialists. Choose the model and access ceiling for each role, with bounded work and a visible run record.

  1. Dispatcher

    Decompose the goal into a bounded job graph.

    01
  2. Researcher → writer

    Investigate first. Then propose a focused change.

    02
  3. Reviewer

    Check the evidence and review the resulting diff.

    03
TIME. EVENTS. A CHANGE WORTH NOTICING.

Give work a starting signal.

Set a rule. Change the sample. See what would run.

LOCAL SIMULATOR
01 / THE RULE

A brief, on your schedule.

Example timezone: America/Toronto. Locus runs on your awake Mac.

THEN ASK THE AGENT TO

Review the project and prepare a progress brief.

02 / TEST INPUT
What happens with this input?

Try a Saturday, or a time before the scheduled run.

Real condition checks. Sample agent output.No models called, accounts connected, or files written.

In Locus, schedules and event polling run locally. Approvals appear in Attention; run history stays in Activity.

AMBITION, WITH BOUNDARIES

Delegation should
make the work clearer.

More agents are useful when they have distinct jobs. Locus gives each role a model, an access ceiling, and a bounded part of the goal.

Different roles. Different models.

Use local Ollama for one role and a connected account for another. Authorize hosted routing before a dispatcher sends task context to that provider.

Changes you can actually inspect.

Run team work in a managed Git worktree. Review the diff before it reaches your project. Locus checks for conflicts before applying it, or you can land the result on a branch.

A ceiling on access. A budget for work.

Configure role access and limits on jobs, calls, tokens, and concurrency. Permission modes govern tool access; command guardrails block configured catastrophic patterns.

WORK THAT CARRIES THROUGH

Longer than
a single turn.

Persistent goals

Continue across turns and app restarts. Keep the goal and its progress together, with pause, resume, edit, and end controls.

Task Capsules

Keep a plan with separate planning, implementation, and review models. Revisit revisions and carry the work into the next stage.

Lasting conversations

Each scheduled agent keeps a primary conversation. Return to its run history and results, with side conversations kept separate.

PRICING / NO LOCUS SUBSCRIPTION

The workspace is free.
The model is your choice.

No agent seats. No Locus credits. Local models, hosted APIs, and your connected plan each have their own cost picture.

LOCUS$0 / software

Free and open source.
Apache-2.0.

Read the license

No provider fee.

Inference runs on your hardware. Install Ollama and choose a model that fits your Mac.

Local compute · your machine

See what the work costs.

Usage & Costs shows model calls, hosted tokens, team runs, and estimated cost. Break it down by day, workspace, model, or agent.

7 days30 days90 daysAll history

Set limits before the run.

Set team limits for jobs, rounds, concurrent calls, total calls, metered tokens, and estimated cost. Keep the amount of work deliberate.

Cost estimates use your entered rates. An estimate limit stops further routing after it is exceeded; it is not a guaranteed cap on your provider’s bill.
GIVE THEM SOMETHING WORTH DOING

Your next idea could use a team.

Get Locus Agent teams guide

Locus command palette