START IN YOUR WORKSPACE

03 / GET STARTED

Start with your next task.

Bring your project, configure your agents, and define what a successful result looks like.
Linux · Python 3.11+ · Your configured Agent CLI

01

Get the source

Clone the repository into your local workspace.

git clone https://github.com/sdnlink/the_last_km.git cd the_last_km
02

Launch the local console

python3 -m console

Open http://127.0.0.1:8765.

03

Configure agents and create a task

Use the setup page to install and authenticate your agents. Enter the original requirements and acceptance criteria, select relevant behavioral checks, and start the task.

Read the full documentation

GOOD QUESTIONS. CLEAR ANSWERS.

A few things worth knowing.

How is Auto Moniter different from a coding agent?

Your coding agent writes and changes code. Auto Moniter coordinates the work around it: clarifying requirements, scheduling independent reviews, feeding back gaps, and running your acceptance checks until the requested work is verified.

Can I keep using my current agents and models?

Yes. Auto Moniter works with several native Agent CLIs and selected backends through Paseo. Support and permission modes vary between worker and reviewer roles. Install and authenticate each CLI, then consult the project documentation and local environment checks for the combination you plan to use.

What counts as done?

With independent review enabled, the worker and reviewer must agree on the delivery scope, provide valid evidence, and pass the configured checks and version checks. The watcher makes the final acceptance decision. An agent saying “done,” or a formatting check passing, is not enough.

Does my code stay on my machine?

The supervisor and console run locally. Your chosen agents may send code, prompts, and context to a model provider, depending on their configuration. Local orchestration does not, by itself, make model calls offline or keep all data on your machine.

Can I pick up where a task left off?

The supervisor saves the workspace, checkpoints, and recorded review feedback. If recovery checks pass, you can resume the same run with its accumulated time and call usage intact. If recovery is unsafe, it stops with diagnostics. Unaccepted work is never reported as delivered.