All workflows

Workflows

ORVEN has no fixed layout. Each job gets the columns it needs. These are the boards engineers open most, with a full guide for each.

Debugging

Find out why, with the evidence on one screen.
01

Chase a bug

Open nvim, the Debugger and the dev server. Set a breakpoint, trigger the request, read the variables. The code, the paused frame and the server's output stay on screen together.

columns nvim · debugger · processes Read the guide →
02

Fix a flaky test

Keep the test runner in watch mode next to the code. Every save reruns the test; the failure and the log that explains it stay visible.

columns nvim · processes Read the guide →
03

Investigate an incident

Start from the logs, confirm in the data, and have the agent piece together what happened while you keep digging.

columns processes · agent · database Read the guide →

Understanding code

Get from "what is this" to "I can change it".
04

Read unfamiliar code

Ask the agent how a path works. It answers with a diagram drawn from the source, its boxes pointing at the code they stand for.

columns nvim · agent Read the guide →
05

Trace a request end to end

Send one real request and follow it through the code. The log shows where it went, the agent maps it, nvim shows each stop.

columns agent · nvim · processes Read the guide →

Data & schema

Change data with the table in view.
06

Change the schema

Write the migration in nvim, run it, and check the table in the next column. Ask the agent what else reads it before you merge.

columns nvim · database · agent Read the guide →
07

Backfill data

Run the backfill and watch both its output and the table it writes to. Stop it the moment the numbers look wrong.

columns nvim · database · processes Read the guide →

Frontend

See the change as you make it.
08

Build the UI

Save in nvim. The page updates beside it. The dev server log is one glance away when something breaks.

columns nvim · browser · processes Read the guide →
09

Fix a visual regression

The page looks wrong since the last merge. Put it beside an agent that finds the change, and review its fix before you commit it.

columns browser · agent · review Read the guide →

Working with agents

Hand off a task. Stay in control of what lands.
10

Hand off a task

Give the agent a scoped task and keep its changes and the test run open next to it. It asks before it writes.

columns agent · review · processes Read the guide →
11

Review agent changes

Read what the agent wrote the way you read a teammate's PR. Comment on the lines, hand the comments back, and watch it revise.

columns agent · review · nvim Read the guide →
12

Run agents side by side

Give two agents two tasks in one repository, each in a worktree of its own, each with its changes in view.

columns agent · review Read the guide →
13

Juggle several tasks

A task on every board, agents working on all of them, and one key to whatever needs you next.

columns agent · nvim · processes Read the guide →

Shipping

Get it reviewed, merged and verified.
14

Ship it

Last look at the changes, a full test run, and the deploy log, on one board until it is live.

columns agent · review · processes Read the guide →

Close the other windows.

Get ORVEN