flowcy.dev runs as an official GitHub App. Installing it gives flowcy.dev scoped, revocable permission to read and act on the repositories you choose — no personal access tokens, no service accounts.
- A GitHub account (personal or organization).
- Admin access to the repositories or organization you want to install on. GitHub requires owner permission to install third-party apps.
- A modern browser. Sign-in uses GitHub OAuth, and the Secrets feature uses WebAuthn passkeys, which need a current Chrome, Safari, Firefox, or Edge.
- Open the flowcy.dev dashboard and click Sign in with GitHub.
- You'll be redirected to GitHub's OAuth consent screen. Approve the basic profile + email scopes — these are only used to identify your account inside flowcy.dev.
- After approval you land on the empty dashboard with a banner prompting you to install the GitHub App.
From the dashboard, click Install GitHub App. This opens GitHub's installation page in a new tab, where you'll choose:
- Account — select the personal account or organization you want to install on. If you're an org admin, you'll see the org listed; if not, ask an admin to install it for you.
- Repository access — pick All repositories to let flowcy.dev manage every current and future repo, or Only select repositories to scope it to a handful. You can change this any time from GitHub's Settings → Applications → Installed GitHub Apps page.
- Permissions — review and accept. flowcy.dev requests:
- Read & write on Issues, Pull requests, Projects, and Contents (so it can label, comment, and update files).
- Read & write on Actions secrets (so it can install the
DOCS_UPLOAD_TOKEN CI secret for the docs feature on your behalf).
- Read on Metadata, Checks, and Workflows (so it can react to CI events).
- Webhook subscriptions for issue, PR, push, check, and project events.
Click Install. GitHub redirects you back to flowcy.dev, where the installation appears as a card on the Dashboard.
On the dashboard you should now see a card for your installation listing the repositories flowcy.dev can see. To smoke-test it:
- Open one of those repositories on GitHub.
- Create a new issue with a short title and description.
- Within a few seconds flowcy.dev's agent will react — usually by adding labels and linking the issue to your project board (if you have one). The activity also shows up under Sessions.
If nothing happens, jump to Settings → Automation and confirm the relevant toggles are on. Issue labeling, PR validation, and project linking are all enabled by default but can be turned off per account.
The dashboard cards link out to GitHub's installation settings. From there you can:
- Add or remove repositories from the installation.
- Suspend the app temporarily (flowcy.dev will stop receiving webhooks).
- Uninstall completely. Uninstalling revokes flowcy.dev's GitHub access immediately; your local data in flowcy.dev (sessions, settings, encrypted secrets) is retained until you delete your account.
You can install flowcy.dev on as many accounts and organizations as you have admin rights to. Each installation appears as its own card on the dashboard. Settings, prompts, automations, and secrets are scoped per user account in flowcy.dev, not per installation, so you don't need to reconfigure everything when you add a new org.