Skip to main content
agent-workspace/ is Fleet Pi’s living directory. It is the repo-local home for the durable context that lets Fleet Pi behave like an adaptive, self-improving coding system instead of a stateless chat window.
For the accepted canonical workspace contract, manifest and section boundaries, and projection rules, see the adaptive workspace contract.

​
What lives here

​
Why it matters

Fleet Pi keeps important agent context in normal repository files so that:
  • Project memory can be reviewed and refined over time.
  • Plans stay visible to humans and agents.
  • Newly installed Pi resources are discoverable instead of hidden in transient runtime state.
  • Self-improvement remains part of the repository’s change history.

​
Relationship to .pi/ and docs/

  • docs/ is the human-facing documentation surface.
  • agent-workspace/ is the agent-facing operational surface.
  • .pi/ contains committed project Pi configuration and built-in runtime bridges.
  • agent-workspace/pi/ is the canonical home for workspace Pi resources, including skills.
Root .pi/settings.json remains a compatibility bridge that points Pi at the workspace-native resource directories.

​
Workspace skills

Pi loads workspace skills from one root: agent-workspace/pi/skills/. Put each skill in its own folder named after the skill, with name and description frontmatter:
agent-workspace/pi/skills/codebase-research/SKILL.md
Supporting files such as examples.md, evals.md, or changelog.md can sit next to SKILL.md. Skills you install from chat with resource_install land in the same folder and become available after reload. agent-workspace/skills/ is a legacy location. Pi does not load skills from it, so move any skill folders there into agent-workspace/pi/skills/. With Daytona sandboxes, Fleet Pi moves legacy skills/<name>/ folders on your workspace volume into pi/skills/ when it prepares the sandbox. If a skill with the same name already exists in pi/skills/, Fleet Pi quarantines the legacy copy instead of overwriting it.

​
Durable self-improvement

Fleet Pi is intentionally opinionated:
  • Durable improvements belong in reviewable Git diffs.
  • Canonical memory should live in the smallest relevant file.
  • Ad hoc notes should stay temporary unless they are later synthesized.
  • Transient runtime or session state should not be treated as the source of truth.

​
Next steps

Adaptive workspace contract

Canonical sections, manifest, and the projection boundary.

Architecture

Where the workspace fits in the runtime topology.
Last modified on November 10, 2026