Start & Session Upload

metateam start is the canonical context loader behind crew startup. Managed summon calls the same loader before launch and writes the result to START.md beside the generated instruction file; the command remains available for manual/debug context loading.

Transcript upload for managed crew sessions is communicator-driven. When automatic upload misses a transcript, agents can use metateam session upload for explicit catch-up.

Start

$ metateam start [PROMPT]

Loads the context block (relevant past sessions, KB entries, recall) used at session start. In managed crew summons, Metateam calls this loader before launching the agent and writes START.md into the agent workdir; the agent reads that file. SessionStart hooks still do not inject context — see Hooks & Setup.

Use this command directly for debugging, custom launches, or inspecting what would be written to START.md.

Option	Purpose
--as <IDENTITY>	Override identity as station:crew:persona (for debugging recall and context selection)

Example workflow:

$ metateam start "fix the auth module" > context.txt
$ metateam start --as bronto:titan:data "review this architecture"

If no prompt is provided, it uses an empty string and returns context based on the working directory and git metadata alone.

Manual Session Upload

$ metateam session upload [SOURCE_OR_TARGET] [FILE]

Uploads sessions from known client transcript locations or from an explicit transcript file. This is a catch-up/debug path for transcripts that were not uploaded automatically by the communicator-driven crew path.

Examples:

$ metateam session upload codex
$ metateam session upload gemini
$ metateam session upload grok
$ metateam session upload /path/to/transcript.jsonl

Run metateam session upload --help for the full argument contract.