One organization manifest gives every AI harness generated guidance, mounts, launch profiles, and local operating context — on any machine, with one command.
curl -fsSL https://my-cli.com/install.sh | shThe installer needs no Go or Node, persists the user-local binary path, and starts guided onboarding on a fresh interactive install. Run my update for later updates; re-running the installer also works.
Install and authenticate one supported AI harness first; it guides the rest of setup. Other prerequisites are Git, curl, and a logged-in GitHub CLI (gh) for organizations hosted on github.com; the installer and my doctor tell you what is missing. On Windows, use the Linux CLI and Git together in one WSL distribution, with the umbrella under /home.
Create a new organization manifest and local umbrella:
my init acme --name "Acme"
cd "$(my root)"
my setup
my doctor
my ai codexTo join an existing organization, use the organization-provided one-liner:
curl -fsSL https://my-cli.com/install.sh | sh -s -- --manifest acme git@github.com:acme/manifest.gitThe agent continues from the first missing prerequisite through private GitHub authentication, manifest sync, setup, required organization tools, and verification.
my init creates a private manifest control plane plus a content workspace, all local and working offline. Preview publication with my publish --print, then run my publish when the repositories should be created and pushed. See the complete Quick Start for prerequisites, harness choices, guided onboarding, daily sync, sessions, and publication.
~/acme/
├── .my-cli/ # workspace identity and local state
├── workspace/ # manifest-declared content mount (its own repo)
├── repos/ # opted-in catalog repositories
├── personal/ # local-only scratch
├── .mcp.json # generated local MCP config
├── AGENTS.md # generated root guidance
└── CLAUDE.md # compatibility pointer when supportedThe organization manifest lives in its own private repository outside the umbrella — the workspace is a mount of things the manifest defines, and day-to-day work never edits the manifest itself.
my is the organization layer of a broader agentic stack: org context and knowledge for every agent and human, from one manifest. It composes with gnit (git-native multi-repo workspaces, the umbrella's publish substrate) and clawdapus (governed agent containers whose cognition is mediated by the cllama proxy) — manifest roles compile into contained fleet agents that carry the my CLI as a governed work surface. Gated organization services (credential brokers, human-reviewed communications) are declared in the manifest and consumed the same way by human and AI operators.
Start with the quickstart, then read the model for the boundary between the public CLI and a private organization manifest.