Connect an app built with Cursor

Create a login for the walker

Sign up on your deployed app with a fresh email you control and give FixWalk that email and password on the connections screen. The walker uses this account and no other.

Link your repo

You own the repository, so pick it directly on FixWalk's connections screen. FixWalk only reads it.

Give the walker a read-only database key

Read-only, always. We store it encrypted, use it only during a walk, and delete it the moment you disconnect. The walker writes only under its own account, never yours.

For Postgres (Supabase, Neon, or your own), create a read-only role:

create role fixwalk_reader login password 'CHOOSE-A-LONG-PASSWORD' noinherit;
grant usage on schema public to fixwalk_reader;
grant select on all tables in schema public to fixwalk_reader;
alter default privileges in schema public grant select on tables to fixwalk_reader;

and paste a connection string for that role. For MongoDB, create a database user with the read role on your database and paste its connection string.

If that Postgres is Supabase, one more line lets the walker see the tables protected by row-level security, which return no rows at all to a plain reader:

grant authenticated to fixwalk_reader;

It reads them as its own signed-in account, never yours, and only inside a transaction that is rolled back. Leave it out and the walk reads those tables through your app's own screens and exports instead. Neon and a plain Postgres have no authenticated role, so skip it there.

Because your app has a repository you can run, FixWalk can also hand you each trip as a pull request with a failing test instead of a prompt. Ask for that on the project page.