Account
No session
Sign-in is needed first. Codaegis stops before repo setup so the repo is tied to a real account.
Connect
Step 2 of 3: sign in with GitHub and connect one repo.
This is the setup step between Home and Run. It shows the account sign-in state and whether repo access is available to connect, needs setup, or is waiting, then keeps the first governed packet inside one explicit read-only repo scope. If setup is blocked, this page should tell you what is missing and the next bounded step.
Repo boundaries
0 connected · 0 available to connect
No hidden repo boundary setup holds are present in the current snapshot.
Connected repo
0 connected
Codaegis v1 keeps one connected repo usable at a time, even when other repo boundaries are visible. Switching now requires an explicit action that holds the previous repo.
Entry loop step 2 of 3
Connect one repo before the first governed-packet check.
Connect is where sign-in, repo access, and the one-repo v1 rule stop being implied. Once one repo is connected, Run becomes the next step; needs setup means Codaegis is waiting instead of pretending setup is in scope.
Sign-in is needed first. Sign in so this step can honestly move forward.
Connect step status
Identity first0 connected0 available to connect0 need setup
Connected means usable now, available to connect means you can make that repo boundary current next, and needs setup means Codaegis is waiting instead of pretending setup is in scope.
After one repo is connected, Run becomes the narrow governed-packet check step for the first governed packet. Until then, the next bounded step stays here.
Account
Sign in to Codaegis
GitHub is the sign-in path on this deployment.
GitHub sign-in configuredRepo access configured: 0 visible repo boundariesAnalysis configured
Identity path
GitHub sign-in configured
Codaegis stays explicit about whether you are on the GitHub product path, a limited local rehearsal path, or a setup-missing state.
Usage window
Usage window missing
The current session keeps monthly usage visible before any repo is connected.
Repo access
0 visible repo boundaries
Repo access is shown directly instead of being implied by the UI.
Development-only sign-in is disabled on this deployment.
Local rehearsal sign-in is disabled on this deployment. Use GitHub sign-in to continue.
Before you connect
Recommended path: sign in with GitHub before you connect a repo.
Repo access is configured, but no visible repo boundary is attached to this account yet.
Repo connection state
0 connected · 0 available to connect
No additional repo setup holds are hidden here.
Connected repo rule
0 connected
Codaegis v1 keeps one connected repo usable at a time. Switching is explicit and holds the previous repo instead of widening the boundary.
Repo access
0 visible
Repo access stays explicit so you can tell whether repo access is available, waiting on setup, or not available here.
- 01
Sign in with GitHub for the real product path; if sign-in is unavailable, Connect should say that first.
- 02
Install repo access on one repo and keep the scope read-only; if access is missing, Run stays paused.
- 03
Connect the repo you want to use first. Local rehearsal catalogs help practice the flow but never stand in for a real customer run.
- 04
If Codaegis needs more access, it asks and explains the missing evidence before the next action.
Repo boundary states
Sign-in is needed first. Sign in above before connecting a repo so Codaegis can bind setup to one account.
Connected repo
No repo is connected yet.
Record one connected repo on the left so Run can stay scoped to that repo from the first governed-packet check onward.