HomeRunHistoryBillingSettings
Sign in

Workspace governance

Review current scope, private packet transport, and held receiver posture.

Use Settings to inspect account limits, repo setup, policy memory, private packet JSON, export, webhook scope, and held future receivers while every surface remains scoped context with separate human judgment.

Signed-in onlyOne repo at a timeNo authority transfer

Current plan

Plan setup missing

Plan setup is missing for this session.

Connected repo

0 connected · 0 available to connect

Saved setup only builds up inside the current connected repo. No blocked repo boundaries are hidden here.

Saved repo notes

0 saved · 0 eligible

Eligible repo boundaries can save notes; saved note records support later context without authorizing future decisions.

Capability posture

0 current · 0 needs setup

Capability posture stays plain: current, private, intended, held, or not available here.

Current account view

Read current account state, missing setup, and packet-facing scope before use.

Codaegis settings are scoped to signed-in use. Broader self-serve exposure remains a separate deliberate move, not a silent toggle here. Sign in with GitHub before changing live settings.

Current means the capability path is in scope now. Private means read-only signed-in transport. Intended and held rows are future posture, not shipped state or authority grant.

Governed packet JSON

Private transport scope

0

Counted paths have private packet JSON or webhook route scope; repo-level state stays separate.

Signed-in account

No session

Settings stay on the signed-in path even when features need setup or are not available here.

Private packet JSON

Read the same governed packet only when the private path is in scope.

The private packet JSON surface is a signed-in retrieval path. It carries the same governed packet for downstream inspection without adding a second verdict, extra evidence, writes, runs, disposition writes, or public API status.

0 packet available

Private packet JSON

0 paths · 0 keys

Signed-in retrieval paths and private account keys for governed packet detail.

Public API: Held

Private read only

Private read scope does not create public access, writes, runs, or disposition writes.

Packet transport

See private transport scope, recent records, and replay boundaries.

The webhook route carries the same governed packet to the saved destination when plan and repo setup allow it. Failed or held transport records stay visible here, but replay does not approve, mutate, or expand the packet.

Same governed packetReceiver scopedPacket available
0 webhook scoped

Recent transport records

0

Latest packet transport records visible to the signed-in account.

Outcomes

0 packet available · 0 needs attention

0 recent packet transport records are not routed here.

Future receiver config

Show receiver posture as Current, Private, Intended, or Held.

Receiver rows describe how the same governed packet may be inspected. They stay as passive scope labels, bounded inputs, and redaction notes.

ReceiverStatusInput shapeReceiver limits

Receiver

Human: Current

Status

Current

Input shape

Packet summary and visible evidence

Receiver limits

Human decision remains separate

Receiver

Private API: Private

Status

Private

Input shape

API key: packet_detail:read

Receiver limits

No writes / No runs / No disposition writes

Receiver

Codex: Intended

Status

Intended

Input shape

Input: summary only

Receiver limits

No raw logs / No credentials

Receiver

CI: Intended

Status

Intended

Input shape

Input: summary only

Receiver limits

No authority transfer

Receiver

Internal Tool: Intended

Status

Intended

Input shape

Input: summary only

Receiver limits

No authority transfer

Receiver

Cursor: Held

Status

Held

Input shape

Held family

Receiver limits

No public launch

Receiver

CLI: Held

Status

Held

Input shape

Held family

Receiver limits

No public launch

Receiver

VM-agent: Held

Status

Held

Input shape

Held family

Receiver limits

No authority transfer

Input: summary onlyNo raw logsNo credentialsNo public launchNo authority transfer

Held authority rail: no public API launch, no final schema, no SDK, no billing, no self-serve, no compliance approval, no GitHub writeback, no merge/deploy authority, no warranty, and no autonomous-agent authority.

Private API keys

Let bounded tools read private packet detail JSON without sharing a signed-in browser.

These keys only read private packet detail JSON for this account. The full key is shown once when it is created, and stored records only keep a hash.

Agent tools should call GET /api/packets/{packetId} with Authorization: Bearer {key} or x-codaegis-api-key. The key does not create export access, runs, webhooks, disposition writes, or public access.

API key: packet_detail:readNo writesNo runsNo disposition writes
0 current read · 0 revoked

No packet API keys exist yet. Create one when a trusted tool needs private packet-detail reads.

Current account status

Signed-in scoped use

Codaegis settings are scoped to signed-in use. Broader self-serve exposure remains a separate deliberate move, not a silent toggle here.

Sign in with GitHub before changing live settings.

Trusted analysis is configured for new governed-packet checks.

Webhook and export controls only govern signed-in use; they do not widen live edge disclosure by themselves.

Account limits and features

Current plan
Plan setup missing
Capability posture
0 current · 0 needs setup · 5 not available here
Governed packet sharing
0 governed packet JSON in scope · 0 webhook scoped
Export
0 export capability paths in scope
Retention window
No history retention window recorded
Retention limit
Saved packet history supports decision continuity. Minimal operational, audit, or operational receipts may follow separate service-safety retention rules.
Usage window
Usage window missing
Included now
Governed packet export needs plan setup. Webhook route needs plan setup. Neither path changes, expands, or authorizes use beyond the packet.
Saved repo notes
Saved repo notes are disabled on the current plan.

Current scope

0 current capability paths in scope

These capability paths are in scope for the current signed-in account. Use them as shown; they do not add decision, billing, or capacity authority.

Held and setup-gated scope

5 capability paths need setup or remain held

Held and setup-gated paths keep their reason visible, so they do not look shipped, silently available, or broader than their stated scope.

Identity path

Not available here

Sign in with GitHub before managing live settings.

Settings stay read-only until an signed-in session exists.

governed packet JSON

Not available here

Sign in and recorded a governed-packet check before governed packet JSON is available.

governed packet JSON stays signed-in and only exposes governed packets.

Repo policy memory

Not available here

Sign in and connect one repo before saving shared saved setup.

No saved setup settings can be written without an signed-in session.

Webhook route

Not available here

Sign in before webhook packet transport scope can be managed.

Webhook settings stay inactive without an signed-in session and a connected repo.

Governed governed packet export

Not available here

Sign in and recorded a governed-packet check before governed governed packet export becomes relevant.

Export remains signed-in and tied to one governed packet.

Policy memory

Manage repo-scoped notes, webhook route destinations, and the default repo note without widening the product surface. Every packet-producing answer records the policy snapshot it used, so this stays one governed memory capsule instead of hidden instruction machinery.

Repo-scoped continuityUsed for this packet onlyNo hidden authorityHuman decision remains separate

Connected repo

0

Saved setup only builds up on the current connected repo.

Saved notes / private JSON

0 saved · 0 JSON

0 repo boundaries are eligible to save notes before any edit.

Webhook status

0 scoped

Webhook route destinations stay limited to signed-in same-packet transport.

Export

0 in scope

Governed packet export stays literal and plan-bound per repo.

Sign in before managing repo setup.

Repo overview

Review every visible repo scope, its latest governed packet, and its current packet transport scope without leaving Settings.

Connected

0

The current connected repo that can keep building saved setup now.

Notes / private JSON

0 saved · 0 JSON

Eligible repo boundaries and governed packet JSON access stay separate but visible together.

Webhook / export

0 · 0

Webhook route and export scope remain literal per repo.

No repo scopes are visible here yet.

Connect one repo first so saved notes and packet transport history can render truthfully here.

Recent transport history

No packet transport record exists yet.

Packet transport history will appear here once a governed packet is routed to a saved destination.