Your house rules, too. It follows the AGENTS.md or CLAUDE.md in your project.
Code
Ship what
you meant.
Dvina writes code in your project, on your computer, with the notes, the threads and the reasons in view.



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.

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
Ship it
from the chat.
Each task’s answer comes back with its changes. Review them, commit, and open the pull request right there.



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.



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.

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.




















