omegas.dev valid

Ωmegas docs

Documentation for Continuity, Handoff, and Operator: tools for agents that do real work, with the record to prove it.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:58:02.270Z. Cached copy · Source on omegas.dev

# Ωmegas docs

> Documentation for Continuity, Handoff, and Operator: tools for agents that do real work, with the record to prove it.

## Docs

- [Overview](https://docs.omegas.dev/index.md): Start with the Omega product that matches the work your agent needs to do.
- [Continuity](https://docs.omegas.dev/continuity/overview.md): Move a Claude Code or Codex setup without moving a secret. Open source, local-first, MIT.
- [Continuity quickstart](https://docs.omegas.dev/continuity/quickstart.md): Scan, explain, export and re-apply an agent setup in five commands. Everything on this page runs locally and contacts nothing.
- [Continuity CLI reference](https://docs.omegas.dev/continuity/cli.md): Every subcommand, flag and exit code of the @omegas/continuity command line.
- [Continuity security model](https://docs.omegas.dev/continuity/security.md): How Continuity reads hostile filesystems, redacts credentials in five layers, and imports bundles as untrusted input.
- [Handoff](https://docs.omegas.dev/handoff/overview.md): Ask a person once, receive typed data, and redeem one effect with a durable receipt.
- [Handoff quickstart](https://docs.omegas.dev/handoff/quickstart.md): Probe the live service, run the reference server and its conformance suite locally, and make your first request from Python or TypeScript.
- [The Handoff protocol](https://docs.omegas.dev/handoff/protocol.md): A tour of the normative v0.1 specification: the object model, the state machines, receipts, authorizations, and the signing scheme.
- [Handoff SDKs](https://docs.omegas.dev/handoff/sdks.md): The Python and TypeScript clients, their honest installation state, and the patterns they make easy.
- [Handoff conformance](https://docs.omegas.dev/handoff/conformance.md): How to run the Handoff compatibility suite against your own deployment.
- [Operator](https://docs.omegas.dev/operator/overview.md): Cloud browser devices driven by tasks, with live view, human takeover, webhooks, and an audit trail. In closed preview; access is granted per organization.
- [Operator: authentication and scopes](https://docs.omegas.dev/operator/authentication.md): One credential, a scope table with no surprises left in it, and the credential-custody rules that keep a key out of your logs.
- [Operator: tasks and event streams](https://docs.omegas.dev/operator/tasks.md): Submitting a task, reading it back at the right route, streaming its events past the 300-second cap, and what needs_human means.
- [Operator: live view and takeover](https://docs.omegas.dev/operator/live-view.md): Watch sessions, control sessions, the takeover lease, and why read-only is genuinely read-only.
- [Operator: webhooks](https://docs.omegas.dev/operator/webhooks.md): Verifying signed deliveries, answering duplicates correctly, and keeping your endpoint out of the auto-disable path.
- [Operator: errors and conventions](https://docs.omegas.dev/operator/conventions.md): The error taxonomy and which codes are retryable, idempotency on
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=omegas.dev · GET /v1/domain/omegas.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for omegas.dev:
1. POST https://agentwebmap.com/v1/sites/omegas.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://omegas.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/omegas.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/omegas.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.