The nebula command.#

The nebula binary owns onboarding, chat, the Telegram bridge, and the gateway daemon. Run it through Bun from the repo (bun run nebula <command>).

Init#

bun run nebula init

Generates a fresh agent wallet and writes a local encrypted keystore. The default identity is a plain EOA, so there is no on-chain mint and no operator signature required. Set your OPENAI_API_KEY (and any NEBULA_LLM_* overrides) before you start so the brain is configured.

Chat#

bun run nebula chat

Drops into the interactive terminal session. Ask the agent to read or act: "what's my balance?", "best stablecoin yield on Mantle?", "swap 1 MNT for USDC", "supply 5 USDC to Aave". Reads return directly. Every value-moving action runs the four-gate pipeline, and material-risk actions pause for your approval inline.

Telegram#

bun run nebula telegram setup

Pairs a Telegram bot so you can drive the same agent from your phone, with the same approval gates. Approval prompts arrive as inline-keyboard buttons.

Gateway#

The gateway is a long-running daemon that keeps Telegram online and routes approval prompts even when you do not have an interactive session open. It is the process that lets the agent stay reachable between chats.

Setting the policy#

The CLI reads the boundary from the environment. Set the NEBULA_POLICY_* variables (caps, allowlists, slippage, autonomy tier, read-only) before launching; see Configuration for the full list. The limits are enforced in deterministic code, so the agent cannot raise them at runtime.

Read Configuration next.

Source: packages/cli↗.