Code

Ship what
you meant.

Dvina writes code in your project, on your computer, with the notes, the threads and the reasons in view.

Late in the evening at her desk at home, a senior engineer in a cobalt sweater reads her display, tea in hand, the city lights behind her.
Dvina’s answer on payments-core: a retried refund reuses its idempotency key, so it posts to the ledger once; 38 tests pass. 7 files changed on refund-idempotency, +212 −48, ready to review, with Changes and Commit.Dvina’s answer on payments-core: a retried refund reuses its idempotency key, so it posts to the ledger once; 38 tests pass. 7 files changed on refund-idempotency, +212 −48, ready to review, with Changes and Commit.

We built Dvina
with Dvina.

The app on your phone, the desktop app and this website: written, reviewed and committed in Dvina, one turn at a time.

From a weekend app to the payments core.

In full context

It read
the notes first.

The director’s notes say teens can’t take loading-dock shifts. Dvina read them before it wrote the sign-up rule, so the app does what she asked.

After closing, a volunteer developer laughs over his shoulder as he carries the last crate of apples through the pantry’s back room, his laptop shut on the table beside the director’s notes.

Your house rules, too. It follows the AGENTS.md or CLAUDE.md in your project.

Last month counts. It searches your past chats and files, so the reasons come along.

Tasks, together

They work
it out.

Three tasks on one repo decide who commits first and who rebases after. You never have to referee.

One Chat on a Mac: three tasks on pantry-shifts, the notes they sent each other (I’m on the schema, rebase after me; you commit first, I’ll run lint after you; lint is clean and I’ve committed) and Dvina’s line: All three committed. No conflicts.One Chat on a Mac: three tasks on pantry-shifts, the notes they sent each other (I’m on the schema, rebase after me; you commit first, I’ll run lint after you; lint is clean and I’ve committed) and Dvina’s line: All three committed. No conflicts.

One Chat

Ship it
from the chat.

Each task’s answer comes back with its changes. Review them, commit, and open the pull request right there.

Two tasks’ answers in the main chat with their code cards: 3 files changed on volunteer-age with Changes and Commit; 2 files changed on csv-export-dates, committed, with Review commit and Push and create PR.Two tasks’ answers in the main chat with their code cards: 3 files changed on volunteer-age with Changes and Commit; 2 files changed on csv-export-dates, committed, with Review commit and Push and create PR.
Sheets of tracing paper stacked on a pale oak table by a window, the top sheet lifted at one corner, a pencil line showing through the layers.

Review

Change
your mind.

Every turn shows the files it changed. Take one back, and the work you did since stays.

Yours to approve.

Guardrails

Careful where
it counts.

Migrations, deploys, pushes and secrets wait for your OK. Your admin can set how much always asks.

At dawn on the bank’s operations floor, the payments lead reads his laptop, a hand at his chin.
Run this command? npx prisma migrate deploy. Changes a database. Reject or Allow.Run this command? npx prisma migrate deploy. Changes a database. Reject or Allow.

From anywhere

Ask from
the stands.

Between periods, you ask for the CSV export fix. Dvina works on it in the project on your computer at home, and the changes wait for your review.Your computer needs to be on, with Dvina open.

At an evening hockey game, a woman in a cobalt puffer jacket types on her phone in the bleachers, the rink glowing behind her.

Nothing is pushed
until you say so.

Your project is a folder on your computer, and with Git every edit Dvina makes can be undone. Approvals are on by default, and you choose how much asks.

Bring Dvina to your repo.

Code needs Dvina on at least one computer. Every other device can start the work and follow it.

Keep exploring.

Computer Use

It doesn’t just answer. It does.

Questions? Answers.

Is this an IDE?
No. It’s Dvina. You describe, review and ship in the same app you use for everything else. Your editor stays your editor; Dvina does the understanding.
Do I need to install something separate?
No. Code is part of the Dvina desktop app, the same one that holds your documents, your chats and your memory.
Does it work with my existing projects?
Yes. Open a folder on your computer as a project, and Dvina reads it alongside the docs and decisions around it.
How does the pull request reach GitHub or GitLab?
Through your own Git sign-in. Dvina pushes your branch and opens the pull request on GitHub or GitLab; any other host opens its own new pull request page.
What runs without asking?
Builds and tests just run. Deleting files, pushing, database changes, deploys and anything touching secrets wait for your OK, and you choose how much asks.
Can non-developers use it?
For working apps and pages, they don’t need to: that’s Create. Code is for when you’re working on real software and want the whole story behind you.