In development

Your last agent IDE.

Omega brings your project, agents, code, review, and evidence into one fast, native workspace.

IDENTITY ONBOARDING

Runningproduct direction · interactive preview

Prepare identity-first onboarding for Omega. Keep the editor, project, and agent setup intact. Split implementation from verification, then show me the exact changes and evidence.

I’ll inspect the project and current onboarding flow first, then split the interface and verification work into independent lanes. You can review or steer the work while they run.

Plan2 of 5 done

Inspect the current identity and onboarding flowDone
Map the change onto native project and editor stateDone
Implement the identity-first onboarding sliceIn progress
Run accessibility and journey verificationPending
Review the evidence and accept the resultPending

Reasoning summaryThe editor already owns project, buffer, task, terminal, and Git truth. The onboarding change should add identity without creating a second project graph or copying an external agent’s configuration.Done

The editor already owns project, buffer, task, terminal, and Git truth. The onboarding change should add identity without creating a second project graph or copying an external agent’s configuration.

Commandrg -n "Identity|Agent Setup|onboarding" crates/onboarding crates/agent_uiDone

CWD/work/omegaSOURCE—

crates/onboarding/src/identity.rs       identity-first step
crates/onboarding/src/agent_setup.rs    external-agent setup
crates/agent_ui/src/agent_panel.rs      native agent thread
3 product seams matched

skills/listLoaded repository and interface guidancedynamicToolCallDone

impeccable · active
repository AGENTS.md · active
openagents.com constraints · active

spawnAgent · implementation swarm2 done · 1 running

protocol-scoutExplorerTrace identity, project, and agent ownership boundariesDone

spawnAgentTrace the current onboarding flow and report each authority boundary.

UpdateMapped identity, project, agent setup, and application-state owners.

ResultIdentity can enter the existing flow without replacing editor or agent state.

timeline-builderFrontendBuild the native identity-first onboarding stepRunning

spawnAgentOwn the onboarding interface and preserve the native application structure.

FileChangeAdded identity creation and recovery states before theme and agent setup.

ResultThe first-run journey now keeps identity, project, and agent setup distinct.

a11y-oracleNested reviewerVerify disclosure semantics, keyboard targets, and status namesDone

spawned by timeline-builder

spawnAgentNested child spawned by timeline-builder for an independent accessibility pass.

ReviewDetails use native disclosures, status is exposed as text, and controls retain accessible names.

ResultNo icon-only ambiguity or inaccessible status color dependency found.

waitAgentCollected 3 delegated resultscollabAgentToolCallDone

protocol-scout       completed · 38s
timeline-builder      completed · 1m 14s
└─ a11y-oracle        completed · 24s

Also make sure the child work is inspectable, and keep the composer usable while the agents are still running.

sendMessageSteered timeline-buildercollabAgentToolCallDone

Delivered: “Expose the nested child transcript and preserve mid-turn steering in the composer.”

Queued follow-up (#1)Measure the route bundle after the visual pass.Runs when this turn completes

File changesPatch updatedPATCH: COMPLETED · 4 FILESDone

[MOD]crates/onboarding/src/identity.rs+96−8
No unified diff recorded.
[MOD]crates/onboarding/src/onboarding.rs+42−12
No unified diff recorded.
[MOD]crates/omega_deltas/src/omega_deltas.rs+18−2
No unified diff recorded.
[MOD]crates/onboarding/src/onboarding_tests.rs+74−4
No unified diff recorded.

Commandcargo test -p onboarding -p omega_deltasDone

CWD/work/omegaSOURCE—

test onboarding::identity_first ... ok
test onboarding::recovery_path ... ok
test omega_deltas::identity_boundary ... ok

3 focused tests passed

Command approval

Run the bounded native build to verify the onboarding journey.

cargo build -p omega

Approved

Commandcargo build -p omegaDone

CWD/work/omegaSOURCE—

Compiling onboarding
Compiling omega
Finished release profile
✓ native build passed

browser · inspectChecked the onboarding journeymcpToolCallDone

Identity appears before theme and agent setup
Recovery remains explicit
Keyboard traversal completes
Horizontal overflow: none

Web searchReviewed identity and recovery guidancewebSearchDone

2 primary references inspected. Recovery language matches the product contract.

Image viewCompared default and large-text layoutsimageViewDone

Default: 1512 × 982
Compact: 360 × 780
Large text: 24 px
No clipped controls.

[INFO]Context compactedPreserved the objective, plan, child work, approval, changed files, and verification receipts.

Measure the route bundle after the visual pass.

Command./script/clippy && cargo test -p omega_deltasDone

CWD/work/omegaSOURCE—

✓ clippy passed
✓ divergence checks passed
✓ onboarding journey passed

Agent lifecycle · settled3 done

protocol-scoutExplorerIdentity and agent ownership boundaries verifiedDone

timeline-builderFrontendIdentity-first onboarding journey completeDone

a11y-oracleNested reviewerKeyboard and status semantics verifiedDone

Plan updated5 of 5 done

Inspect the current identity and onboarding flowDone
Map the change onto native project and editor stateDone
Implement the identity-first onboarding sliceDone
Run accessibility and journey verificationDone
Review the evidence and accept the resultDone

Working

Questions and answers

What Omega is—and where it’s going.

Read the full documentation

What is Omega?

Omega is the Zed-based OpenAgents IDE now in active development. It brings projects, editing, terminals, agents, review, and work records into one native application.

Which agents will Omega work with?

Omega is designed to work with native and external agents, including agents you already use. Each external agent keeps its own account, credentials, configuration, and runtime.

What makes the work verifiable?

Omega is being built to connect an objective to the agents, changes, tests, approvals, and receipts behind the result. You can inspect the evidence instead of trusting a confident summary.

What stays local?

The native editor, project, and direct agent paths are designed to keep working without an OpenAgents cloud connection. Hosted routing, community workrooms, and cross-device features need services and must stop clearly when those services are unavailable.

Is Omega available yet?

Not yet. Omega is in active development, and the latest candidate has not passed every release-readiness gate. The current Electron-based OpenAgents Desktop remains the supported application until Omega earns the cutover.