mBm / mbm2

PREVIEW DOCUMENTATION · RELEASE PENDING

Your First mBm Session

Need Path
A local mbm serve executable Start mbm2 in your project directory
An already running server Use mbm2 --attach <url> --dir <path>
An account or a paid plan Use the existing console; neither is collected by this docs site

mbm2 is the new terminal client. It does not replace the v1 mbm command. This preview assumes you already have a trusted mbm2 build: a public installer and checksum workflow are not released yet. The CLI reports its supported flags with mbm2 --help (cmd/mbm-tui/flags.go:94-112).

Prerequisites

  1. Open a terminal in the directory you want the session to use.
  2. Have either the v1 mbm server executable on PATH or a reachable server URL.
  3. Choose a configured model/provider before sending the first prompt. A missing provider or model is a setup issue, not a reason to paste credentials into the docs site.

The default client mode starts a local mbm serve; --attach connects to an existing server without spawning one (cmd/mbm-tui/main.go:124-154). Remote use should keep TLS verification on.

Start Locally

mbm2 --dir /path/to/project

The home screen appears first; creating a session happens when you submit a prompt, not when you launch the client (docs/06-flow/attach-flow.md §Seed prompt). Select an agent and model, type a small task such as asking for an explanation of one file, and review any permission request before responding. Nothing on this page authorizes a tool action automatically.

Attach To A Server

mbm2 --attach https://your-server.example --dir /path/to/project

The server's address and authentication must come from your operator. The client also supports username/password flags and environment defaults (cmd/mbm-tui/flags.go:102-111); avoid putting passwords directly in shell history. Do not use --insecure as a routine fix for a certificate failure. A failed connection is not an empty session: check the URL, credentials, TLS certificate and server status, then retry.

Continue And Leave

Action Command or route
Open the latest session mbm2 --continue
Open a known session mbm2 --session <id>
Open a known session on a remote server mbm2 --attach <url> --session <id>
Leave Use the client exit binding; the clean-exit output identifies how to reopen

Sessions live on the runtime server, not on this documentation host. A different attach URL can show a different set of sessions; check the target before concluding that data is missing.

Next

Topic Availability
Installation and checksums Public release workflow pending P9 verification
Agents, approvals and sessions Detailed task guides are being authored
Account and billing Existing console.mbm.mn/auth and /account/payment routes