Repository changes

Understand an existing repository, make the change, and verify it

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.

MobileNavigation.tsx+12 −5
useEffect(() => {
+ const releaseScrollLock = () => {
+  document.body.style.overflow = ''
+ }
  if (open) lockScroll()
- return unlockOnUnmount
+ return releaseScrollLock
}, [open])
Verification
18 tests passed
Build completed
Mobile checked

Work inside the real project context

Add only what helps the agent understand the target and verify the result.
1

Code repository

Connect GitHub or GitLab, or upload project files.

2

Goal or failure

Provide expected behavior, reproduction steps, logs, or screenshots.

3

Project constraints

State the stack, compatibility requirements, and boundaries.

Deliverables

Keep the edits, verification, and explanation together

Scoped code changes

Follow existing structure and dependencies while avoiding unrelated rewrites.

Test and build results

Record commands, passes, failures, and environment limitations.

Change summary

Explain the cause, affected files, behavior change, and remaining risk.

Continuable workspace

Files and execution events remain available for the next request.

Process

Understand the project before changing and verifying it

01

Read conventions

Inspect structure, dependencies, instructions, and current tests.

02

Locate the cause

Follow the call path and observed behavior to bound the fix.

03

Implement the change

Edit the files and add tests proportional to the risk.

04

Run verification

Execute tests, builds, or browser checks and report the result.

Example workflow

Fix a mobile regression in an existing React project

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.

Repository change questions

Can it work with private repositories?

Yes, after an administrator enables a provider and the user authorizes repository access.

Will the agent rewrite large parts of the project?

It should default to scoped changes around the request. You can explicitly restrict directories, APIs, or dependency changes.

Can it run a development server and check the browser?

Yes. Workspace runtimes can host persistent services, and browser tools can inspect pages, console output, and screenshots.

Can I return to the state before the change?

Execution events and file versions support regeneration or restoration from the relevant checkpoint.

Give the agent a real repository problem

Connect the repository and describe the goal, reproduction steps, and constraints.

Start changing