Code repository
Connect GitHub or GitLab, or upload project files.
Connect or upload a repository and describe the goal or failure. Flowmint reads project conventions and relevant code, makes scoped edits, runs tests, builds, or browser checks, and preserves the complete workspace.
Connect GitHub or GitLab, or upload project files.
Provide expected behavior, reproduction steps, logs, or screenshots.
State the stack, compatibility requirements, and boundaries.
Follow existing structure and dependencies while avoiding unrelated rewrites.
Record commands, passes, failures, and environment limitations.
Explain the cause, affected files, behavior change, and remaining risk.
Files and execution events remain available for the next request.
Inspect structure, dependencies, instructions, and current tests.
Follow the call path and observed behavior to bound the fix.
Edit the files and add tests proportional to the risk.
Execute tests, builds, or browser checks and report the result.
See how the agent isolates the cause, edits existing files, adds a test, and preserves verification results.
View the full example“Fix the mobile regression that prevents scrolling after the navigation closes. Keep the existing components and public API, add a regression test, and run the frontend build.”
Yes, after an administrator enables a provider and the user authorizes repository access.
It should default to scoped changes around the request. You can explicitly restrict directories, APIs, or dependency changes.
Yes. Workspace runtimes can host persistent services, and browser tools can inspect pages, console output, and screenshots.
Execution events and file versions support regeneration or restoration from the relevant checkpoint.
Connect the repository and describe the goal, reproduction steps, and constraints.