See and revoke access
See every browser, app and key that can reach your data, give one less access, or cut it off.
Three kinds of thing can reach your instance, and each is a sign-in:
- A browser you signed in to as the owner.
- An app you approved, such as Claude, ChatGPT or the
marfaCLI on one of your computers. - A key you made for an agent, a script or a connector, or that an app made for one.
Any computer where the CLI is signed in with Full access can see and end all of them.
See what can reach your data
marfa sign-ins list01a1f120-71d6-76b0-8531-0ba34e91280a browser Chrome on macOS last used 2026-11-19T00:06:37.782Z
01a1f121-2e94-70d2-aefd-0f0b75bebe08 app marfa on sams-mac last used 2026-11-19T00:35:49.756Z
01a1f130-37fc-7184-b4a2-3fba803cf8be key Reading digest last used 2026-11-19T00:24:01.373ZEnd a sign-in you don't recognize or nobody uses. To see what each can do:
- A key:
marfa keys listshows the types it reads or edits, when it ends, and the app that made it, if one did. - An app:
marfa apps listshows each app's ID, name and approval date, and--jsonadds the scopes you approved.
marfa sign-ins rename <id> <name> gives an app or a key a name you recognize. To see what one did, search the audit log.
Cut one off
marfa sign-ins end ends any sign-in at once. Its next request is refused, and an app can't renew its access:
marfa sign-ins end 01a1f130-37fc-7184-b4a2-3fba803cf8beended sign-in 01a1f130-37fc-7184-b4a2-3fba803cf8be- Ending a key revokes it. Whoever holds it can't use it again.
- Ending an app disconnects it. The keys it made keep working unless you add
--revoke-keys, which revokes them too, and every key those keys made, except an owner's key. - Ending a browser signs it out.
What it wrote stays. Find the items it created with marfa items list --source <source>, and move any you don't want to the bin. That doesn't undo its edits to items that already existed: marfa items versions <id> shows an item's earlier versions. A key's source is in marfa keys list; marfa items stats --by source lists every source, and an app's begins oauth:.
To end many at once, such as after losing a laptop, run marfa sign-ins end-all. It ends only browsers unless you name the kinds, so to end everything, repeat --kind:
marfa sign-ins end-all --kind browser --kind app --kind keyName each sign-in to leave alone, such as the CLI you're using, with --keep <id>.
Give less access instead
- An app:
marfa apps narrow <app-id> --scope <scope>, repeating--scopefor each scope it keeps, such as--scope core.note:read, or--clearto remove them all. Its access tokens and any key it made that hold more end at once, and the app signs in again with what is left. You can only give an app less: a list with more than the app holds is refused. - A key:
marfa keys update <key-id>, as Manage keys shows.
marfa apps revoke <app-id>, with the ID from marfa apps list, also disconnects an app, and takes --revoke-keys too. The app's next sign-in shows the approval page again.
Give an app's types to another app
An app's own types, under app.<vendor>, belong to the app that registered the first of them. An app that registers again gets a new client ID and loses them, so give its vendor to the new ID, from marfa apps list:
marfa apps vendors move app.readinglist <client-id>marfa apps vendors list shows who holds each. Only you, or a key you made with grants.manage, can move one.
When access ends by itself
- An unused app: its approval ends after
grant_inactivity_daysunused,365by default. The keys it made keep working. - An app nobody approved: it is removed after
unapproved_app_retention_hours,1by default, counted from when it registered or when its approval page was last offered. - A moved address: moving the instance's sign-in address signs every app out. Each signs in again at the new address with the access it held.
Change an instance's settings explains both settings.