Glossary
- Agent — A Codex-powered persona (planner, worker, reviewer, orchestrator, or LLM) created through
computer-agents. - Agents SDK — The TypeScript package (
computer-agents) that configures and runs agents locally or in the cloud. - Artefact — Files emitted during a session: turn transcripts, summaries, diffs, logs. Stored under
docs/sessions/locally or in GCS for containers. - Codex CLI — Command-line runtime that gives agents shell, filesystem, and git access. Bundled with TestBase containers.
- Container — Managed Cloud Run environment that executes agents remotely with persistent storage.
- Files API — REST interface (and SDK helpers) for listing, uploading, downloading, and deleting workspace files inside a container.
- GCS (Google Cloud Storage) — Storage backend used to persist container workspaces and session artefacts.
- MCP (Model Context Protocol) — Specification for attaching external tools to LLMs/agents. Supports hosted HTTP/SSE servers and local stdio servers.
- MCP Server — Implementation of the MCP spec that exposes capabilities (filesystem, search, SaaS APIs) to agents.
- Persistent Container — Container created with
persistContainer: true, keeping the runtime alive across tasks until explicitly deleted. - Planner/Worker/Reviewer — Codex agent roles. Planner writes plans, worker executes changes, reviewer validates results.
- Runtime client — Object passed to
runtime.clientin agent config when executing in the cloud. Usually created byTestbaseCloud.forContainer. - Session ID — Unique identifier for an agent run. Use it to correlate logs, artefacts, and telemetry.
- TestBase Cloud — Managed platform plus REST API that provisions containers and stores artefacts.
- TestBase Container — Individual compute instance running inside TestBase Cloud.
- Workspace — Directory (typically
/workspace) where agents read/write files. Mirrors a git repository.
Last updated on