OmicClaw Gateway Overview

OmicClaw is now documented as a unified gateway product rather than an older “message bot only” launcher.

The current entry points are:

  • omicclaw: branded OmicClaw launcher. It starts gateway mode and forces the web login flow.

  • omicverse gateway: generic gateway launcher. It starts the web UI and auto-starts configured channels.

  • omicverse claw: gateway mode by default. Use -q/--question only when you want one-shot code generation.

2. What Each Entry Point Actually Does

Entry point

Current behavior

Recommended use

omicclaw

Starts gateway mode with forced login and OmicClaw branding

Main product entry for users

omicverse gateway

Starts gateway web UI and background channel runtime

Generic deployment / ops

omicverse claw

Starts gateway mode unless -q, --daemon, --use-daemon, or --stop-daemon is given

Mixed CLI, especially code-only mode

3. Gateway-Only vs Channel-Backed Mode

If you launch gateway mode without --channel, OmicVerse keeps the web UI running in web-only mode.

Example:

omicclaw

or:

omicverse gateway

If you add a channel, the same gateway runtime starts the web UI and the selected message channel together.

Example:

omicclaw --channel telegram --token "$TELEGRAM_BOT_TOKEN"

4. Shared Runtime Layout

The current gateway/channel stack still stores runtime state under:

~/.ovjarvis

Typical contents include:

  • config.json: persisted launcher and channel defaults

  • auth.json: saved auth state

  • workspace/: user-visible files and prompts

  • sessions/: runtime session data

  • context/: cached context

  • memory/: daily summaries and memory artifacts