Follow the project’s conventions
Ask Codvian to read existing patterns before editing, and to use your own scripts for tests, linting and builds.
For developers
Fits around your tools.
Works on your project.
Keep your editor, your repository and your commands. These habits get the best results from the agent.
How a task moves
From your request
to a change you review.
Codvian sits between you and your own tools. It reads the project, uses the terminal, Git and browser within the access you set, and hands back a diff.
- Your request
- Tool actions
- Result for review
A good first task
Small, specific,
easy to check.
Say where to look, what should change and how to verify it. You can copy this example.
Example request
Inspect the input validation in this project. Explain the current behavior, propose a small fix for empty input, add a regression test, and run the relevant checks. Ask before installing dependencies.
Review through Git
Start from a clean state, then review the diff. Checkpoints add a recovery point but do not replace version control.
Grant only what the task needs
Use Ask for approval on unfamiliar repositories. Move to Approve for me once you trust the workflow.
Match the model to the job
Strong tool-calling models handle multi-file work best. Use a higher effort level for hard problems.