See it in action

Two short coding stories: a rule you state once, and a method your agent learns and reuses. Then look inside the dashboard.

Here are two short illustrative stories from one project. A developer builds a task-tracker API with a coding agent over several sessions. The screenshots further down are example data from a local dashboard.

Use case 1: a rule

Say a rule once

1. Session 1: state the rule

   The developer says: “All API errors must return { code, message }.” The agent builds the first endpoint and saves the rule as a memory.

2. Session 2: it just knows

   In a brand new session, the agent adds a second endpoint. Its errors already use { code, message }. Nobody repeated the rule.

3. Session 3: the rule changes

   The team moves to a standard error format. The developer says so once. The old rule is retired, and new endpoints use the new format.

You say it once, and your agent keeps it until you change it.

Use case 2: a method

Your agent learns how you work

1. Task 1: the agent works it out

   Asked to add POST /tasks, the agent figures out a good routine: define the route, validate the input, write tests, update the API docs. The tests pass and the task is finished.

2. The method is saved as a procedure

   When the agent closes the task, it saves that routine as a procedure, with its steps and a warning: “Run the migration before the tests.”

3. Task 2: Slowave offers it

   Weeks later, in a new session, the developer asks for GET /tasks/{id}. As the task starts, Slowave offers the saved procedure. The agent follows the same routine and skips the trial and error.

4. The agent rates it

   The agent reports that the procedure helped. It will be offered more readily for similar work. If it had gone wrong, Slowave would keep it as a warning instead.

Your agent doesn’t only remember facts. It remembers how to do the job.

What the saved procedure looks like

Goal: Add an API endpoint.

1. Define the route.
2. Validate the input.
3. Run the migration, then write the tests.
4. Update the API docs.

Watch out: Run the migration before the tests.

Learn how procedures work

What a procedure is, and how it improves with use.

Look inside with the dashboard

Run slowave dashboard to open it. Everything shown stays on your computer.

Overview

How much your agent recalled, and how useful it was.

Memories

Everything your agent has saved, in one searchable list.

Procedures

Methods your agent learned and can reuse.

Retrieval

What was asked, what came back, and whether it helped.

Graph

How your memories connect to each other.

Activity

A timeline of what happened and when.

The dashboard also has a System view that shows whether the database, background worker and backups are healthy.

Next: connect your agent

Pick your tool and finish setup.