English · 中文
The original Mega was the first-generation monorepo platform. Mega2 is the second-generation engine built for Agents, with two core capabilities: the Monorepo engine and optional Agent Session Capture. The recommended Agent setup combines Mega2, ScorpioFS, and Libra: Mega2 hosts the Monorepo and exposes the capture API, ScorpioFS mounts repository paths as a local filesystem, and Libra provides Agent version-control workflows and terminal browsing.
The open-source edition of Mega2 has no Web UI. Run libra mega2 browser --server <URL> to open Libra's terminal browser: it browses remote directories one level at a time, supports creating, deleting, moving, and renaming directories, and can list, create, and delete root tags. Write credentials are required to create or delete tags. The command does not replace Git clone, fetch, or push.
Choose a guide by task. The quick start and user guide cover day-to-day use; configuration, deployment, and development guides are for operators and contributors. Subsystem contracts and planning records remain in their own directories.
| Capability | Description | Further reading |
|---|---|---|
| Monorepo engine | Hosts code trees and Git repositories. Use Git clients for clone, fetch, and push; use Libra browser for basic remote directory browsing and tag operations. | User Guide |
| Agent Session Capture | Optional HTTP capability for ingesting and querying Agent sessions, events, checkpoints, transcripts, and file operations. It is separate from Git push and requires explicit enablement plus an ingest token in storage-only mode. | Agent Capture configuration and API (Chinese) · Deployment Guide |
Other capabilities—including LFS, OCI, build artifacts, Vault, notifications, and configuration—are covered in Usage Recipes, the User Guide, and the Configuration Reference.
| Task | Guide |
|---|---|
| Start mega2 locally and make your first push | Quick Start |
| Follow examples for repository migration, LFS, OCI, artifacts, and persistent data | Usage Recipes |
| Learn Git, HTTP API, Libra, and CLI workflows | User Guide |
| Task | Guide |
|---|---|
| Find config sources, SecretRef, hot reload, and validation behavior | Configuration Reference; full settings are in ../config/config.toml |
| Deploy or harden a trunk / storage-only service | Deployment Guide; operating rules are in the trunk deployment manual (Chinese) |
| Configure authorization or initialize the Monorepo directory layout | Authentication and authorization manual (Chinese) · Architecture · Initialization Manual |
| Task | Guide |
|---|---|
| Build locally, run tests, and start integration-test services | Local development and testing (Chinese) · Contributing Guide |
| Understand module boundaries, storage, and the write path | Architecture |
| Prepare a change, run the required checks, or add a module | Contributing Guide; repository conventions are in ../AGENTS.md |
| Look up how error types map to HTTP status codes | Error model (Chinese) · Architecture |
refactoring/(Chinese): contracts and implementation records for subsystems such as configuration, protocols, storage, Vault, and notifications. Some documents record how a subsystem evolved; check the current source and config for shipped behavior.plan/(Chinese): task cards, roadmaps, and plan templates. Plans record decisions and scheduled work, not the current implementation state.gap/(Chinese): competitive gap analysis and follow-up leads.- OOM / SIGKILL troubleshooting notes (Chinese): an internal troubleshooting record (not a user guide) for diagnosing and monitoring terminated test processes on the author's machine.