Skip to main content

Product UI guide

Visual tour of the Codesteward Review web app: dual-mode reviews (Gate for PRs, Stewardship for branches), durable findings, org tenancy, and install-wide platform controls.

Screenshots from a self-hosted install with Keycloak identity and a GitHub App connector. Your org name and data will differ.


Map of the product​

Overview Dashboard · Analytics
Review Gate · Steward · Findings · Reports · PRs · Cross-Repo
Trust Learnings
Tenant Connectors · Members · Models · Prompts · Policy · Organization
You & install Account · Platform · Platform ops · Settings hub
ConcernWhere in the UI
Start a PR merge checkGate
Audit a long-lived branchSteward
Live progress, report, auditSession blade (from Gate/Steward table)
Issue backlog + SARIFFindings
Human-readable historyReports
SCM browse / open PRsPRs
Multi-repo fan-outCross-Repo
👍/👎 memoriesLearnings
GitHub App, Graph, toolsConnectors
Org roles & IdP provisionMembers
Models, policy, SCIMModels · Policy · Organization
Install health & licensePlatform (platform operator)

1. Onboarding​

New users without an org (or after first IdP login) land on a three-step path: create org → install GitHub App → first review.

Onboarding — create organization

Self-host installs often already have a Local org; choose Continue with this org or create a new tenant.


2. Dashboard​

Control plane home: KPIs, recent sessions, and a live activity stream of sessions and new findings.

Dashboard

Shortcuts:

  • Gate a PR / Steward a branch jump into the start forms.
  • Open a session row to open the session blade (pipeline, report, audit).

3. Analytics​

Org-scoped quality metrics (address rate, severity mix, session outcomes). Charts are pure CSS — no external chart SDK.

Analytics

Use this for leadership-friendly trends; use Platform ops for SRE latency and token cost across all orgs.


4. Running reviews (Gate & Steward)​

Start form​

Gate is PR-only (base/head from the PR via SCM). Steward is branch/path audit (no PR field by design).

Start gate form and session list

Typical fields:

FieldNotes
RepositoryFrom connected SCM, or type owner/repo
Modegate vs stewardship
Risk tierSpecialist set (e.g. full = correctness, security, rules, testing)
PathsScope inside the repo (. = whole tree for stewardship)
PR numberRequired for gate

Live session blade​

While a job runs (or after it completes), the right-hand blade shows stage pipeline, units, evidence, and report.

In progress — pipeline steps fill as they finish; cross-repo fan-out shows multiple units:

Running session with cross-repo units

Completed — stage timings and narrative report:

Session stage pipeline and review report

Review audit (code provenance + specialist ledger) — export lives here:

Session review audit

Evidence — findings with specialist reasoning:

Session evidence findings

Token usage — list-price estimate by model (not an invoice):

Session token usage

Deep dive on audit fields: Session audit. Pipeline stages: Review pipeline.


5. Findings​

Durable issues across gate and stewardship. Filter by severity, status, and repo; export SARIF for CI.

Findings list

Each row shows confidence, category, suggested fix when policy allows, and reasoning/tool badges. React 👍/👎 on findings to train Learnings.


6. Reports​

Catalog of human-readable session reports. Open a row for executive summary, compare re-runs on the same repo, download .md or audit JSON.

Reports catalog


7. Pull requests​

Browse connected SCM repositories and open PRs — jump to diff review or start a gate from context.

Pull requests browser


8. Cross-repo topology​

Declare edges between repos (depends_on_api, deploys_with, …). Stewardship/gate fan-out can expand along links under depth and token budgets.

Cross-repo topology


9. Learnings​

Org memories from reactions and explicit feedback. Scoped org-wide, repo, or PR. Injected into specialist prompts and post-judge noise suppression.

Learnings


10. Connectors​

Enterprise Git connectors prefer GitHub App / OAuth installs, not long-lived personal tokens. Also Graph MCP, issue trackers, Confluence, etc.

Connectors

After GitHub App is connected, setup steps collapse; use Test installation token or Reconfigure when rotating credentials.


11. Members & roles​

Org membership is separate from platform operator. With Keycloak, this page provisions directory users and links them to the org.

Members

RoleCapabilities
ViewerRead-only sessions, findings, dashboards
ReviewerStart reviews, react, export (default)
AdminMembers, connectors, models, policy, SCIM, org settings
OwnerAdmin + org ownership

Platform-wide install settings require platform operator (first bootstrap / first OIDC user, STEW_PLATFORM_ADMIN_EMAILS, or platform_admin flag) — not org admin alone.


12. Models​

Per-org provider keys (encrypted) and stage routing. Host env is fallback for single-tenant dogfood only.

Provider API keys

Org defaults and per-stage matrix

Org Langfuse project

Optional Langfuse dual-writes with a platform project when both are set.


13. Prompts​

Edit specialist persona and grounding per org. JSON output format, learning injection, and runtime context stay system-locked so the pipeline cannot be broken.

Specialist prompts


14. Policy (STEWARD.md)​

Severity floor, nit cap, skip globs, verification bar, focus areas. Stored in the org policy API; repo STEWARD.md on the base branch still applies for PR authors (they cannot relax gates).

Policy editor


15. Organization​

Tenant identity (name/slug), plan notes, feature toggles (suggested code fixes, SARIF publish), SCIM, and admin audit log.

Organization settings

SCIM directory provisioning

Admin audit log

Admin audit is IAM/config trail (login, SCIM, connectors). Review audit on a session is code provenance — different exports.


16. Account​

Profile, password (Keycloak directory when in IdP mode), theme, and browser-only prefs (mock graph, DeepAgents, etc.). Does not change API/worker runtime.

Account


17. Platform (operators)​

Install-wide health, identity status, graph rebuild, optional platform GitHub App enforce, license and runtime knobs. Tenant org admins cannot open these writes.

Platform settings

Platform ops​

Cross-org SRE view: session latency by stage, specialist error rates, worker queue, token cost estimates, slowest sessions.

Platform ops

Settings hub​

Map of scopes: You · Tenant · Install.

Settings hub


Suggested reading order​

  1. This guide (orientation + screenshots)
  2. Review pipeline (what the worker does)
  3. Session audit (compliance export)
  4. Root repository README (install, CLI, Helm)

Screenshot index​

FileScreen
onboarding.pngFirst-run org creation
dashboard-home.pngDashboard
analytics-overview.pngAnalytics
sessions-start-gate.pngGate start form + table
session-blade-*.pngSession detail blade (pipeline, audit, evidence, tokens, running)
findings-list.pngFindings
reports-catalog.pngReports
pull-requests.pngPRs
cross-repo-topology.pngCross-repo
learnings.pngLearnings
connectors.pngConnectors
members.pngMembers
models-*.pngModels / Langfuse
prompts-specialists.pngPrompts
policy-steward-md.pngPolicy
organization-*.pngOrg settings, SCIM, admin audit
account-settings.pngAccount
platform-settings.pngPlatform
platform-ops.pngPlatform ops
settings-hub.pngSettings hub