Quickstart

Esta página aún no está disponible en tu idioma.

This is the end-to-end loop: describe a task, let an agent do it in an isolated session, review the result, and open a pull request. You can do all of it from the dashboard; the equivalent commands are shown for those who prefer the terminal. If you haven’t installed Chronos yet, start with Installation.

Connect your repository. In the dashboard header, enter the repository path (or .) and click Open.
Terminal window
```
chronos .
```
Create a session with a prompt. Type what you want in the composer and press Enter — for example: Add a /health endpoint that returns the service status.

Chronos creates a new session on its own branch and an agent starts working. Your main branch is untouched.
Terminal window
```
chronos session new "add a /health endpoint that returns the service status"
```
Watch it work. The center pane streams the agent’s progress live — what it’s reading, the changes it’s making, and a summary when it finishes. You can keep working elsewhere and come back; the session remembers its history.
Terminal window
```
chronos session attach <id>
```
Review the changes. In the right pane:
- Changes shows every file the agent touched, with added/removed line counts.
- Open the diff to read exactly what changed.
- Checks runs your verification steps (tests, linting) so you know it’s sound.
Terminal window
```
chronos session diff <id>
chronos session check <id>
```
Open a pull request. When you’re happy, open a pull request straight from the session. It goes through your normal review and approval process, and merges only when your policy allows.
Terminal window
```
chronos session pr <id>
```
Work in parallel. You don’t have to wait. Start another session for another task — each one is isolated, so several can run at the same time without interfering.

What just happened

Your work ran in an isolated session on its own branch — your main branch was never touched.
The agent only used approved tools, and any credentials stayed out of its hands.
Every step was recorded in a complete audit trail.

That’s the core loop. The rest of this documentation goes deeper into each part — the dashboard, reviewing changes, and pull requests, approvals and merge.