Published by Anvil Coder · Halvic Labs GmbH
Updated
Getting started with AI coding agents
Prepare Anvil Coder with access, a repository, project rules and a small first ticket. Understand usage costs, verification and the final review.
What do you need for a first run?
You need access to Anvil Coder, a repository with appropriate permissions and a clearly bounded task. Registration currently uses a waitlist. Subscription prices are not final; platform consumption and external BYOK model costs are separate. Check pricing and usage costs before starting.
Choose a non-critical repository or a small bug fix first. A migration with unresolved requirements is not a useful first test of whether the workflow fits your team.
How do you prepare the project?
- Connect the repository and configure the internal issue board or a supported tracker.
- Describe the language, framework and verification commands in the stack profile. The verification environment needs the corresponding tools; a profile does not automatically install them.
- Configure project rules and guardrails, including allowed dependencies and the handling of sensitive data.
- Review the cost limits and approval settings before triggering a story.
What makes a suitable first ticket?
For example: “Reject an empty email address when saving.” Add observable acceptance criteria: no record is created, the interface displays a clear message, and a regression test covers the failure. Identify the affected area and explicitly exclude unrelated changes.
This is an illustrative task, not a documented customer result. For larger projects, see the path from specification to pull request.
What should you check in the result?
Read the diff, run report and actual test results together. A generated test file is not a passed test. The hosted service produces a pull request draft; a human decides whether to merge. Complete any missing verification before acceptance.
The documentation covers configuration in detail.
