Skip to main content
Build a small issue board, add a useful filter, and inspect the result. You can follow the same workflow in a new project or an existing repository.

​
Before you start

You need a pre.dev account and available credits. To work on existing code, have access to the GitHub repository you want to import.

​
Build your first change

1

Create a project

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

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.
3

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.
4

Build a concrete change

Ask the agent to implement the first useful piece. For a dedicated sprint, use:
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.
5

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.

​
Check the result

Select an assignee and a status, then clear each filter. Try a combination with no matching issues. Compare that behavior with the code changes and the agent’s verification report.