# Fibe — user guide & skills

> Fibe runs your projects in real Docker environments connected to your compute hosts and Git repositories. The guide covers Marquees, Props, Templates, Playgrounds, Tricks, Genies, and a full reference library of authoring skills.

## Get started

- [Welcome to Fibe](https://whats.fibe.gg/intro/): Fibe runs Docker environments on your hosts from a browser. Add a Marquee, connect a Prop, launch a Playground.

## Concepts

- [Agents](https://whats.fibe.gg/concepts/agents/): Configured AI assistants (Genies), Build in Public, and the artefacts and activity they leave behind.
- [Bazaar](https://whats.fibe.gg/concepts/bazaar/): The public Template marketplace. Browse, fork, launch Templates other Players have published.
- [Billing](https://whats.fibe.gg/concepts/billing/): Plans, Wallet, Mana, Sparks, top-ups, subscriptions, referrals, Runes. Everything that goes through Profile → Billing.
- [Marquees](https://whats.fibe.gg/concepts/marquees/): A Marquee is a Docker host where Playgrounds and Tricks run. Connect your own or use a managed tutorial host. Marquees handle routing, TLS, registry credentials, capacity.
- [Playgrounds](https://whats.fibe.gg/concepts/playgrounds/): A Playground is the running environment a Playspec produces — services, URLs, logs, terminals, lifecycle controls.
- [Playspecs](https://whats.fibe.gg/concepts/playspecs/): A Playspec is a launch blueprint. A Template is a reusable recipe many Playspecs can share. Both manage what a launch becomes — from different angles.
- [Props](https://whats.fibe.gg/concepts/props/): A Prop is a connected Git repository. Fibe reads branches and files from it, mounts source into containers, and reacts to pushes.
- [Scrolls](https://whats.fibe.gg/concepts/scrolls/): A searchable workspace that collects artefacts, mutters, messages, raw provider traces, memories, and Pantry templates in one place.
- [Tricks](https://whats.fibe.gg/concepts/tricks/): A Trick runs a task and finishes — tests, migrations, backups, scheduled jobs, CI on push. Plain Compose, with Fibe enforcing one-shot rules.

## Authoring templates

- [App playbooks](https://whats.fibe.gg/authoring/playbooks/): Examples by app shape. Each one shows the before/after diff for the input and explains every line.
- [Authoring a template](https://whats.fibe.gg/authoring/overview/): A Fibe template is a Docker Compose file with a few Fibe-specific additions — labels on the services that need them, and an optional settings block at the top.
- [Compose → Fibe](https://whats.fibe.gg/authoring/compose-to-fibe/): Nine-step path for taking an existing docker-compose.yml and turning it into a Fibe template. Includes a quick-reference cheatsheet.
- [Decision guides](https://whats.fibe.gg/authoring/decisions/): Short answers to the questions you'll ask while authoring — static or dynamic, exposed how, rolling updates or not, where does the credential go.
- [Execution modes](https://whats.fibe.gg/authoring/execution-modes/): A template runs in one of four shapes — long-running HTTP, Trick, scheduled Trick, triggered Trick. Decide first; everything else follows.
- [Launch variables](https://whats.fibe.gg/authoring/variables/): Two ways to weave a variable's value into the template — inline inside a string, or as a whole-node replacement at a specific location.
- [Recipes](https://whats.fibe.gg/authoring/recipes/): Pattern-level building blocks. Each one is a small set of changes that solve a single authoring question.
- [Service labels](https://whats.fibe.gg/authoring/service-labels/): The complete set of fibe.gg/* labels you can add under labels on a service. Source & build, routing & exposure, rolling updates, automation.
- [The x-fibe.gg settings block](https://whats.fibe.gg/authoring/settings-block/): Optional root key on the template. Holds launch-time variables and template metadata. Compose silently ignores it, so the file remains a valid docker compose file.
- [Variable placement (paths)](https://whats.fibe.gg/authoring/variable-placement/): When you bind a variable to a location with path or paths, the location is a dotted reference into the template body.

## Operate

- [Before you publish](https://whats.fibe.gg/operate/publishing/): A checklist for templates that will appear in the Bazaar. Walk it once before you click publish; re-walk it on major updates.
- [Common problems & fixes](https://whats.fibe.gg/operate/common-problems/): What the message means, and the smallest change that resolves it. Template validation, variables, triggers, runtime — every common error.

## SDK, CLI & MCP

- [Authentication & profiles](https://whats.fibe.gg/sdk/authentication/): Two login flows — API key or browser device-code. Multiple profiles for switching between accounts and environments. Env-var fallbacks for CI.
- [CLI reference](https://whats.fibe.gg/sdk/cli-reference/): Every fibe command grouped by resource family. Playgrounds, Tricks, Agents, Templates, repos, secrets, monitoring, and the lower-level utilities.
- [Common workflows](https://whats.fibe.gg/sdk/workflows/): Repo-backed launch, greenfield setup, brownfield transform, multi-step pipelines, live monitoring, CI integration. The end-to-end stories you'll actually use.
- [Go library](https://whats.fibe.gg/sdk/go-library/): Embed Fibe in your own Go programs. Client construction, resource managers, auto-retry, circuit breaker, idempotency, structured errors.
- [Install the fibe CLI](https://whats.fibe.gg/sdk/install/): Homebrew, Go install, prebuilt release binaries, or Docker. Whatever fits your environment. First run is fibe doctor.
- [MCP server](https://whats.fibe.gg/sdk/mcp-server/): Run fibe mcp serve to expose 42 typed tools to your AI agent. Stdio for single-tenant, SSE/HTTP for multi-tenant. Plug into Claude Code, Cursor, Antigravity, Codex.
- [The Fibe SDK](https://whats.fibe.gg/sdk/intro/): One binary, three modes — a fibe CLI for the terminal, a Go library to embed, and an MCP server for AI agents. The interface to Fibe.
- [Tools catalog](https://whats.fibe.gg/sdk/tools-catalog/): Every MCP tool fibe ships, organized by family. Each row links to a detail page. Read the catalog top-to-bottom or jump straight to a tool.
- [Troubleshooting](https://whats.fibe.gg/sdk/troubleshooting/): Debug mode, common errors, rate limits, the doctor command, schema introspection. What to check when something isn't working.

## Reference: API

- [Agents and knowledge API](https://whats.fibe.gg/api/agents-and-knowledge/): Public /api endpoints for agents, conversations, artefacts, feedback, events, and memory.
- [API reference](https://whats.fibe.gg/api/): Public /api namespace conventions for authentication, response envelopes, pagination, async operations, and endpoint groups.
- [Integrations API](https://whats.fibe.gg/api/integrations/): Public /api endpoints for API keys, secrets, job environment, repositories, installations, webhooks, and audit logs.
- [Platform API](https://whats.fibe.gg/api/platform/): Public /api endpoints for Marquees, props, playgrounds, playspecs, imports, launches, and compose validation.

## Reference (skills)

- [Add Metadata](https://whats.fibe.gg/reference/recipe-add-metadata/): Use to fill in `x-fibe.gg.metadata.description`, `category`, `source_defaults`, and execution settings such as `job_mode`, `schedule_config`, and `trigger_config`.
- [Add Path Rule](https://whats.fibe.gg/reference/recipe-add-path-rule/): Use to write `fibe.gg/path_rule` Traefik path matchers (`Path`, `PathPrefix`, `PathRegexp`) when multiple services share a subdomain. Avoid forbidden matchers.
- [Add Subdomain](https://whats.fibe.gg/reference/recipe-add-subdomain/): Use to set the public hostname leftmost label via `fibe.gg/subdomain` - including the root `@`, defaults, allowed character set, and variable interpolation.
- [Agents And Automation](https://whats.fibe.gg/reference/fibe-agents-and-automation/): Use for Fibe AI Genies, standalone chats, Playground sidecars, Bridge, artefacts, mutters, feedback, job-mode Tricks, CI repair, scheduled jobs, VCS triggers, and mutation-testing automation.
- [Anchors And Aliases](https://whats.fibe.gg/reference/recipe-anchors-and-aliases/): Use YAML anchors (`&name`) and aliases (`*name`) to share `depends_on`, `environment`, `build`, healthcheck, or label blocks across multiple Fibe services without copy-paste.
- [Build Args And Target](https://whats.fibe.gg/reference/recipe-build-args-and-target/): Use to map Compose `build.args` / `build.target` into Fibe `fibe.gg/build_args` (comma-separated KEY=value) and `fibe.gg/build_target`. Includes variable interpolation and parsing rules.
- [Build To Repo Url](https://whats.fibe.gg/reference/recipe-build-to-repo-url/): Use to convert a Compose `build:` block into Fibe dynamic-service labels (`fibe.gg/repo_url`, `fibe.gg/dockerfile`, `fibe.gg/branch`) so Fibe clones, builds, and rolls out the service.
- [Common Errors And Fixes](https://whats.fibe.gg/reference/common-errors-and-fixes/): Use as a diagnostic table for typical errors when converting docker-compose to Fibe templates - unknown labels, bad regex matches, missing repo_url, zerodowntime conflicts, undeclared/unused variables, and trigger/schedule issues.
- [Configs Block](https://whats.fibe.gg/reference/recipe-configs-block/): Use Docker Compose top-level `configs:` to inline small config files (init scripts, conf templates) without bind-mounting from the host. Distinct from Fibe Mounted Files.
- [Convert Compose To Fibe](https://whats.fibe.gg/reference/convert-compose-to-fibe/): Use as the entry point for converting any existing docker-compose.yml into a Fibe Compose template (fibe.gg labels + x-fibe.gg namespace). Orchestrates which surgical skills to load next.
- [Cron Scheduled](https://whats.fibe.gg/reference/playbook-cron-scheduled/): Use to build a Fibe template for a scheduled cron job - daily DB backup, periodic data sync, log cleanup. Combines `metadata.job_mode: true` + `metadata.schedule_config` + watched service.
- [Depends On](https://whats.fibe.gg/reference/recipe-depends-on/): Use Compose `depends_on` with `condition: service_healthy` / `service_completed_successfully` / `service_started` to order service startup correctly in Fibe templates.
- [Env File](https://whats.fibe.gg/reference/recipe-env-file/): Use to set `fibe.gg/env_file` for dynamic services so Fibe knows which example env file in the repo to read defaults from. Covers the difference between Compose `env_file:` and Fibe `fibe.gg/env_file`.
- [Exposure Strategy](https://whats.fibe.gg/reference/decide-exposure-strategy/): Use to decide how a service should be reachable - external public HTTPS via subdomain, internal Basic-Auth-protected HTTPS, sharing a subdomain via path rule, root subdomain, or not exposed at all.
- [Extract Env Variables](https://whats.fibe.gg/reference/recipe-extract-env-variables/): Use to lift `${VAR}` / `${VAR:-default}` Compose interpolations into `x-fibe.gg.variables` so the launcher can configure them, with optional defaults, validation, and path bindings.
- [Feature Surface](https://whats.fibe.gg/reference/fibe-feature-surface/): Use to answer broad \"what can Fibe do?\" questions and choose the correct user-facing Fibe feature area without leaking implementation details.
- [Fibe Labels](https://whats.fibe.gg/reference/reference-fibe-labels/): Use as the definitive reference for every supported `fibe.gg/*` Docker Compose label - exact value regexes, defaults, required-when rules, and what runtime/schema each enforces.
- [Glossary](https://whats.fibe.gg/reference/glossary/): Use as the first reference for the meaning of any core Fibe term - Marquee, Playground, Playspec, Template, Trick, Prop, Bazaar, Agent, Mutter, Artefact, Secret, Player, and related concepts.
- [Inline Variables](https://whats.fibe.gg/reference/recipe-inline-variables/): Use to embed `$$var__NAME` (and `$$random__NAME`) inside Compose string values, label values, image tags, URLs, and partial strings - and to understand when the inline form is required vs optional.
- [Job Mode](https://whats.fibe.gg/reference/decide-job-mode/): Use to decide whether a template should be a long-running HTTP service, a one-shot job (Trick) with `job_watch`, a scheduled job via `schedule_config`, or a VCS-triggered job via `trigger_config`.
- [Job Trick](https://whats.fibe.gg/reference/mode-job-trick/): Use to convert a Docker Compose template into a Fibe job-mode template (Trick) with `fibe.gg/job_watch`, `x-fibe.gg.metadata.job_mode: true`, and the runtime constraints around restart, replicas, and exposure.
- [JSON Schema](https://whats.fibe.gg/reference/json-schema/): The official JSON Schema for Fibe Compose templates — fibe.gg/* labels, x-fibe.gg namespace, variables, metadata. Use it for editor autocomplete and CI validation.
- [Multi Service](https://whats.fibe.gg/reference/playbook-multi-service/): Use when converting a docker-compose with many services (5+) that share configuration - leverages YAML anchors, anchored env blocks, anchored depends_on, and `paths:` arrays for variables.
- [Named Volumes](https://whats.fibe.gg/reference/recipe-named-volumes/): Use to declare Compose named volumes for persistent data (databases, uploads, caches), and to replace host bind mounts that don't survive Marquee filesystem rules.
- [Nginx Static](https://whats.fibe.gg/reference/playbook-nginx-static/): Use to convert a static-image Compose service (nginx serving HTML, prebuilt SPA) into a one-service public Fibe template - the minimum viable conversion.
- [Nodejs Dev](https://whats.fibe.gg/reference/playbook-nodejs-dev/): Use to convert a Node.js dev-mode docker-compose (live source mount + hot reload via Vite, Next.js, nodemon) into a Fibe template using `fibe.gg/source_mount` and `fibe.gg/production: false`.
- [Ports To Expose](https://whats.fibe.gg/reference/recipe-ports-to-expose/): Use to convert Compose `ports:` declarations into `fibe.gg/expose` labels for public/internal HTTP routing through Traefik.
- [Postgres App](https://whats.fibe.gg/reference/playbook-postgres-app/): Use as a generic pattern for \"web app + Postgres\" Compose templates - the right env wiring, healthchecks, password generation, and volume layout for any framework.
- [Product Map](https://whats.fibe.gg/reference/fibe-product-map/): Use to understand Fibe's user-facing product model, core nouns, topology, and normal path from code repository to running Playground without relying on source code details.
- [Python App](https://whats.fibe.gg/reference/playbook-python-app/): Use to convert a Python web docker-compose (FastAPI / Django / Flask) with Postgres into a Fibe template, with optional dev-mode source mount and production zero-downtime variants.
- [Rails App](https://whats.fibe.gg/reference/playbook-rails-app/): Use to convert a Ruby on Rails docker-compose (web + db + redis + jobs + optional websocket) into a Fibe template.
- [Random And Secrets](https://whats.fibe.gg/reference/recipe-random-and-secrets/): Use to generate random values for passwords/secrets via `random: true`, mark variables sensitive for launcher UI, and persist them across rollouts in Fibe templates.
- [Reference (skills)](https://whats.fibe.gg/reference/intro/): A library of compact, task-focused skill files. Designed to be read by both humans and LLM agents working with Fibe.
- [Resource Lifecycles](https://whats.fibe.gg/reference/fibe-resource-lifecycles/): Use to explain how Fibe resources are created, updated, launched, shared, stopped, completed, upgraded, or retired from a user-facing perspective.
- [Runtime Implied Semantics](https://whats.fibe.gg/reference/reference-runtime-implied-semantics/): Use when you need to know what behavior Fibe infers from Compose YAML/labels at runtime (forced lifecycle fields, hidden constraints, stripped keys, and required co-conditions).
- [Schedule Cron](https://whats.fibe.gg/reference/mode-schedule-cron/): Use to add `x-fibe.gg.metadata.schedule_config` to a job-mode Fibe template - cron expression syntax, `marquee_id` requirement, and the relationship with `job_mode: true`.
- [Secrets And Randoms](https://whats.fibe.gg/reference/decide-secrets-and-randoms/): Use to decide where a credential or secret-like value belongs - template variable (with optional `random`/`secret`/`sensitive`), Fibe Secrets, or Job ENV - and how to wire it.
- [Security Access And Integrations](https://whats.fibe.gg/reference/fibe-security-access-and-integrations/): Use for Fibe authentication, sessions, sudo mode, two-factor auth, WebAuthn, API keys, Secret Vault, Job ENV, webhooks, audit logs, data portability and notifications.
- [Source Mount](https://whats.fibe.gg/reference/recipe-source-mount/): Use to set up Fibe live source mounting via `fibe.gg/source_mount` plus `fibe.gg/repo_url` and `fibe.gg/production: false`, including framework-specific dev/watch commands and the rules around `node_modules` and build artifacts.
- [Static Vs Dynamic](https://whats.fibe.gg/reference/decide-static-vs-dynamic/): Use when classifying a Compose service as a Fibe static (prebuilt image) or dynamic (source-backed - cloned/built/mounted from a Git repository) service.
- [Strip Incompatible Keys](https://whats.fibe.gg/reference/recipe-strip-incompatible-keys/): Use to know which Compose keys to delete or rewrite when converting to a Fibe template - `ports`, `container_name`, `hostname`, host-path bind mounts, and Compose-only directives that conflict with Fibe routing/scaling.
- [Template Variables](https://whats.fibe.gg/reference/reference-template-variables/): Use as the definitive reference for Fibe template variable mechanics - declaration shape, `$$var__NAME` / `$$random__NAME` / `$$root_domain` interpolation, validation regex, defaults, and random secret generation.
- [Templates Publish Checklist](https://whats.fibe.gg/reference/templates-publish-checklist/): Use as the final gate before publishing or submitting a reusable Fibe Compose template - covers safety, validation, naming, defaults, secrets, and security rejects.
- [Test Runner](https://whats.fibe.gg/reference/playbook-test-runner/): Use to build a Fibe template that runs a project's test suite on every git push or PR - job-mode + metadata.trigger_config + watched service running pytest/npm test/rspec/etc.
- [Trigger Vcs](https://whats.fibe.gg/reference/mode-trigger-vcs/): Use to add `x-fibe.gg.metadata.trigger_config` to a job-mode template - `event_type: push|pull_request`, repo URL, branch, prop/marquee binding, and `source_defaults` auto-fill.
- [Validation Pipeline](https://whats.fibe.gg/reference/reference-validation-pipeline/): Use to understand which public validation stage catches which class of Fibe template error and how to drive validation from MCP/CLI without relying on source code internals.
- [Whole Node Paths](https://whats.fibe.gg/reference/recipe-whole-node-paths/): Use to bind a variable to a whole YAML node (env scalar, label value, replica count, image, command element) via `path:` or `paths:`. Includes typing, multiple paths, and label-key path patterns.
- [Wikijs](https://whats.fibe.gg/reference/playbook-wikijs/): Use to convert a typical Wiki.js docker-compose.yml (Node app + Postgres) into a Fibe template - end-to-end before/after with all labels, variables, and metadata explained.
- [Wordpress](https://whats.fibe.gg/reference/playbook-wordpress/): Use to convert a WordPress + MariaDB/MySQL docker-compose into a Fibe template - static images, generated DB password, persistent volumes for wp-content and DB data.
- [X Fibe Gg Namespace](https://whats.fibe.gg/reference/reference-x-fibe-gg-namespace/): Use as the definitive reference for the `x-fibe.gg` template namespace - variables, metadata, job mode, schedule config, and trigger config blocks.
- [Yaml Paths](https://whats.fibe.gg/reference/reference-yaml-paths/): Use as the definitive reference for the dotted-path syntax used by `x-fibe.gg.variables.*.path` and `paths` to write whole YAML nodes during template compilation.
- [Zero Downtime](https://whats.fibe.gg/reference/decide-zero-downtime/): Use to decide whether to enable `fibe.gg/zerodowntime` on a service - the prerequisites, what to remove, optional healthcheck tuning labels, and when NOT to enable it.
- [Zero Downtime Healthcheck](https://whats.fibe.gg/reference/recipe-zero-downtime-healthcheck/): Use to tune the five optional `fibe.gg/healthcheck_*` labels for `fibe.gg/zerodowntime: \"true\"`. Covers path, interval, timeout, retries, and start_period with realistic values.

## Reference: Tools

- [Agent Defaults Get](https://whats.fibe.gg/reference/tools/agent-defaults-get/): Use when reading the current Player's Agent default overrides (LLM provider, settings, etc.) — the JSON shape used by the profile UI.
- [Agent Defaults Reset](https://whats.fibe.gg/reference/tools/agent-defaults-reset/): Use when you need to clear all Player Agent default overrides so the platform's admin defaults apply.
- [Agent Defaults Update](https://whats.fibe.gg/reference/tools/agent-defaults-update/): Use when you need to replace the current Player's Agent default overrides. Same JSON shape the profile UI uses. Affects new Agents and unset fields on existing ones.
- [Agents Activity](https://whats.fibe.gg/reference/tools/agents-activity/): Use when you need persisted Agent activity, optionally scoped to a runtime conversation. Overseer-only.
- [Agents Create Conversation](https://whats.fibe.gg/reference/tools/agents-create-conversation/): Use when you need to create or upsert a deterministic Agent runtime conversation. Overseer-only.
- [Agents Delete Conversation](https://whats.fibe.gg/reference/tools/agents-delete-conversation/): Use when you need to delete a specific Agent runtime conversation. Overseer-only.
- [Agents Duplicate](https://whats.fibe.gg/reference/tools/agents-duplicate/): Use when you need to duplicate an existing Agent's configuration (settings, mounted files, defaults). Overseer tool — operates on managed Agents.
- [Agents Interrupt](https://whats.fibe.gg/reference/tools/agents-interrupt/): Use when you need to stop a running Agent turn. Overseer-only.
- [Agents Live State](https://whats.fibe.gg/reference/tools/agents-live-state/): Use when you need current conversation-scoped runtime stream state for a managed Agent. Overseer-only.
- [Agents Messages](https://whats.fibe.gg/reference/tools/agents-messages/): Use when you need persisted Agent messages, optionally scoped to a runtime conversation. Overseer-only.
- [Agents Runtime Status](https://whats.fibe.gg/reference/tools/agents-runtime-status/): Use when you need to check an Agent's runtime reachability, authentication, queue depth, and processing state. Diagnostics for Agent chat health.
- [Agents Send Message](https://whats.fibe.gg/reference/tools/agents-send-message/): Use when you need to send one text message to a managed Agent's chat runtime. Overseer-only.
- [Agents Start Chat](https://whats.fibe.gg/reference/tools/agents-start-chat/): Use when you need to start (or reconnect) an Agent's runtime chat session on the current Marquee. First step before sending messages.
- [Artefact Upload](https://whats.fibe.gg/reference/tools/artefact-upload/): Use when you need to upload an Artefact (file/report/plan/result) for the current Agent. Persists to Rails AND mirrors into FIBE_WORKSPACE_PATH if set.
- [Auth Set](https://whats.fibe.gg/reference/tools/auth-set/): Use when you need to switch session-scoped Fibe API key and/or domain mid-session for multi-tenant work. Validates new creds via /api/me ping by default.
- [Call](https://whats.fibe.gg/reference/tools/call/): Use when you need to invoke a Fibe MCP tool that is registered server-side but not advertised in the current client tool surface (typical when running --tools core).
- [Doctor](https://whats.fibe.gg/reference/tools/doctor/): Use when you need to verify Fibe MCP connectivity, API key validity, and current player profile. First call when troubleshooting auth or environment selection.
- [Feedbacks Get](https://whats.fibe.gg/reference/tools/feedbacks-get/): Use when you need to fetch one feedback entry by id, including the full Player comment, source reference, and context.
- [Feedbacks List](https://whats.fibe.gg/reference/tools/feedbacks-list/): Use when you need to list all feedback entries (Player comments on Artefacts/Mutters/etc.) for the current Agent. Required reading after major milestones.
- [Find Github Repos](https://whats.fibe.gg/reference/tools/find-github-repos/): Use when you need to search GitHub repos across ALL the Player's connected GitHub App installations. Aggregates and deduplicates across orgs/accounts.
- [Get Github Token](https://whats.fibe.gg/reference/tools/get-github-token/): Use when you need to mint a short-lived GitHub installation access token for a specific repository. Auto-resolves the correct GitHub App installation.
- [Gitea Repos Create](https://whats.fibe.gg/reference/tools/gitea-repos-create/): Use when you need to create a new repo on the Player's connected Gitea (managed or external) and atomically register it as a Fibe Prop.
- [Github Repos Create](https://whats.fibe.gg/reference/tools/github-repos-create/): Use when you need to create a new GitHub repository under the Player's OAuth-connected GitHub account and register it as a Fibe Prop.
- [Greenfield Create](https://whats.fibe.gg/reference/tools/greenfield-create/): Use when bootstrapping a greenfield app in one call — creates one or more repos/Props from a template or GitHub repo snapshot, an app-owned template version, a deployed Playground, waits for running, and links it locally to /app/playground.
- [Help](https://whats.fibe.gg/reference/tools/help/): Use when you need to read the cobra CLI Long help for any fibe subcommand (flag descriptions, examples, payload shapes).
- [Launch Create](https://whats.fibe.gg/reference/tools/launch-create/): Use when deploying an existing Fibe-compatible Compose config from inline YAML, a local file, or a GitHub repository config file without creating new source repos first.
- [Local Playgrounds Info](https://whats.fibe.gg/reference/tools/local-playgrounds-info/): Use when you need to get filesystem-level info about one local Playground (name, path, playspec, mounts) without an API call.
- [Local Playgrounds Link](https://whats.fibe.gg/reference/tools/local-playgrounds-link/): Use when you need to symlink a local Playground's mounts into a working directory (default /app/playground) so the Agent has direct file access. Brownfield handshake.
- [Memorize](https://whats.fibe.gg/reference/tools/memorize/): Use when you need to create or update one Memory grounded in a local source conversation. Persistent agent memory tied to evidence (groundings + conversation snapshot).
- [Monitor Follow](https://whats.fibe.gg/reference/tools/monitor-follow/): Use when you need to stream Agent events live as MCP progress notifications. Bounded by duration and max_events. For Overseer waiting on Agent output.
- [Monitor List](https://whats.fibe.gg/reference/tools/monitor-list/): Use when you need to list Agent-produced events (messages, activities, mutters, artefacts) with standard pagination. Snapshot mode — for one-shot reads.
- [Mutter](https://whats.fibe.gg/reference/tools/mutter/): Use when you need to post one short progress/proof/blocker/problem/milestone note as the current Agent. The dedicated Agent progress channel.
- [Mutters Get](https://whats.fibe.gg/reference/tools/mutters-get/): Use when you need to retrieve one Agent's mutter stream — the \"thinking out loud\" feed of progress, proof, problem, and blocker notes — with optional query/status/severity/playground filters.
- [Pipeline](https://whats.fibe.gg/reference/tools/pipeline/): Chain multiple Fibe tool calls into one round-trip with JSONPath bindings. Use when latency matters or multi-step jobs (create→wait→link) need atomicity.
- [Pipeline Result](https://whats.fibe.gg/reference/tools/pipeline-result/): Use when you need to re-fetch a cached fibe_pipeline result by id, optionally projecting a specific JSONPath, within 5 minutes of the original run.
- [Playgrounds Action](https://whats.fibe.gg/reference/tools/playgrounds-action/): Use when you need to run a single Playground lifecycle action — rollout, hard_restart, stop, start, retry_compose, enable_maintenance, or disable_maintenance. Destructive; requires confirm:true.
- [Playgrounds Debug](https://whats.fibe.gg/reference/tools/playgrounds-debug/): Use when you need to fetch comprehensive Playground diagnostics — service/container names, ports, paths, labels, status, urls, recent logs — when troubleshooting a deployment.
- [Playgrounds Logs](https://whats.fibe.gg/reference/tools/playgrounds-logs/): Use when you need to fetch a bounded log snapshot for a single Playground service. Async on Rails — returns terminal payload after polling.
- [Playgrounds Logs Follow](https://whats.fibe.gg/reference/tools/playgrounds-logs-follow/): Use when you need to stream a Playground service's live logs as MCP progress notifications until duration elapses or max_lines reached. For waiting on a specific log pattern.
- [Playgrounds Transform](https://whats.fibe.gg/reference/tools/playgrounds-transform/): Use when an existing deployed playground needs to be transformed end-to-end to a different stack, service shape, source layout, or prop set while preserving its id. Single-call brownfield analog of fibe_greenfield_create. Authors a new template inline if needed and provisions Gitea-backed private Props on the fly for new repos.
- [Playgrounds Wait](https://whats.fibe.gg/reference/tools/playgrounds-wait/): Use when you need to block-and-poll until a Playground reaches a target status (running, stopped, has_changes, destroyed, etc.). Required after rollout/start/restart/job triggers.
- [Repo Status Check](https://whats.fibe.gg/reference/tools/repo-status-check/): Use when you need to verify Fibe's view of multiple GitHub repository URLs in one call — accessibility, App installation status, default branch, etc.
- [Resource Delete](https://whats.fibe.gg/reference/tools/resource-delete/): Use when you need to permanently delete a Fibe resource by id (or name for playgrounds/tricks/playspecs/props/marquees/agents). Destructive — requires confirm:true.
- [Resource Get](https://whats.fibe.gg/reference/tools/resource-get/): Use when you need to fetch a single Fibe resource by id, or by name for playgrounds, tricks, playspecs, props, marquees, and agents. Includes artefact_attachment download.
- [Resource List](https://whats.fibe.gg/reference/tools/resource-list/): Use when you need to list any flat Fibe resource (playground, prop, marquee, agent, secret, webhook, audit_log, memory, artefact, etc.) with schema-validated filters.
- [Resource Mutate](https://whats.fibe.gg/reference/tools/resource-mutate/): Use when you need a single tool for create/update and resource-scoped operations (attach, mirror, sync, fork, trigger, rerun, action, etc.) across Fibe resources. Schema-validates locally before API call.
- [Run](https://whats.fibe.gg/reference/tools/run/): Use when no native MCP tool fits and you need a last-resort escape hatch to invoke an arbitrary fibe CLI command when no MCP tool fits. Avoid; native MCP tools and fibe_call are safer.
- [Schema](https://whats.fibe.gg/reference/tools/schema/): Use before calling Fibe mutation/list tools that need schemas. Authoritative source for resource/operation JSON schemas. Required reading before calling fibe_resource_mutate, fibe_resource_list, or any tool with a payload field.
- [Status](https://whats.fibe.gg/reference/tools/status/): Use when you need to dashboard the current player's resource counts, quota usage, rate-limit budget, and subscription plan in one call.
- [Templates Change](https://whats.fibe.gg/reference/tools/templates-change/): Use when an advanced template-author or admin workflow needs the hidden lower-level primitive for patching, overwriting, or switching template versions, including Trick reruns and global template promotion.
- [Templates Launch](https://whats.fibe.gg/reference/tools/templates-launch/): Use when you need to bootstrap and launch a Playground directly from an existing import template, without creating a new repo. Greenfield-lite.
- [Templates Search](https://whats.fibe.gg/reference/tools/templates-search/): Use when you need to search the Fibe Import Template catalog (own + public + team) by full-text or PostgreSQL regex before greenfield/launch.
- [Tools Catalog](https://whats.fibe.gg/reference/tools/tools-catalog/): Use when you need to discover the full Fibe MCP tool surface (advertised + hidden). Required first step before fibe_call when targeting a tool not visible in ToolSearch.
- [Update Name](https://whats.fibe.gg/reference/tools/update-name/): Use when you need to update the current Agent's display name. Trigger when the conversation topic changes materially.

## Optional

- [llms-full.txt](https://whats.fibe.gg/llms-full.txt): full Markdown content of every page concatenated.