Coding Agent quickstart

Create a project

Sign in at pre.dev and describe what you want to build, or import a GitHub repository.

Build an issue tracker for a small design team.
Include projects, assignees, due dates, and a status board.
Start with a working board using sample data.

Let the agent choose the approach

The agent chooses the next step itself: it can build a small change directly or plan a larger one first. To work on the requirements and architecture first, ask for a plan in your message.

For an existing app, include the expected behavior, the current problem, and any files or constraints you already know.

Connect what the project needs

Open /integrations for Project setup. Choose the relevant connection account, enable skills or MCP servers, and fill required values under API Keys. AI, payments, and sign-in are already built in. Use environment variables for other secrets and configuration.

Build a concrete change

Ask the agent to implement the first useful piece. For a dedicated sprint, use:

/sprint add filtering by assignee and status, with an empty state

A useful result lets you combine both filters, shows only matching issues, and explains when no issues match. Include these criteria in your request so you can check them in the preview.

Follow the active session and its progress. Additional web sessions may require a connected GitHub repository.

Review and ship

Inspect the code changes, the verification result, and the preview. Test your acceptance criteria, then request any corrections. When the app is ready, choose Publish in the header to put it at its permanent address.

For code in GitHub, the session’s Merge into Main action can create a pull request and merge it automatically when clean. Use a review-first request if you want a PR left open.