Repositories¶
The ecosystem spans our own repositories on gitea.jordbo.se and several third-party projects. This page says what each one is for. The details are in each repository's own README.
Access
Repositories marked private need an account with access on gitea.jordbo.se. Links to them do not work for other readers.
Our repositories¶
| Repository | Visibility | What it is for |
|---|---|---|
| pi-devbox | public | The Docker image that runs pi, with a curated toolset, memory integration and shell improvements. Built in two stages (a base image and a variant) and published to Docker Hub for amd64 and arm64, in a core and a -studio flavour. |
| opencode-devbox | public | The same idea for the opencode agent. pi-devbox started as a variant of it and became independent at pi-devbox v1.0.0; much of its base infrastructure came from here. |
| pi-extensions | public | Our own and modified pi extensions: confirmation gates, secret redaction, AWS SSO keep-alive, SSH remote execution, the task tool and others. |
| pi-toolkit | public | Harness bring-up: example settings, key bindings, shell environment, and the pi-task command that runs a delegated task in an isolated child agent. |
| mempalace-toolkit | public | Tooling around MemPalace: the pi extension that injects memory at session start and feeds transcripts to the palace, export and backup scripts, and the design documents for the shared palace and the coordination log. |
| skillset | private | A collection of agent skills. The image bakes in a copy of one of them, mempalace, and records which skillset commit that copy came from. |
| docker-compose-repo | private | Compose configurations for the home-network hosts, the Gitea Actions runners and each device's pi-devbox stack. Its common/pi directory holds the extensions and model list shared by the whole fleet. |
| fleet-ops | private | The fleet inventory and host-specific runbooks. The general mechanisms they rely on are documented in mempalace-toolkit. |
| cli_utils | private | Command-line helpers, including the devbox sanity checks, session repair, multi-repo git helpers and fzf-based pickers. |
| myconfigs | private | Dotfile management: backs up, restores and provisions configuration on several macOS and Linux machines. |
| studio-demo | private | A plain-language guide to Pi Studio and a hands-on demo of everything it can render. |
| pi-atlas | private | This site. |
Third-party¶
These projects are not ours. The image installs them at pinned versions, and we track their upstream releases.
| Project | What we use it for |
|---|---|
| pi | The coding agent itself, installed from npm. |
| pi-fork | Hands a focused subtask to a child agent that inherits the conversation. |
| pi-observational-memory | Compacts a long session into observations and reflections that the agent can recall exactly. We keep a fork (private) with a fix for providers that sign each request. |
| pi-atelier | The terminal user interface: sidebar panels, status line and theme. |
| pi-studio | A browser workspace attached to a pi session, for editing and rendering documents. |
| MemPalace | The memory store: drawers of verbatim text, a knowledge graph, agent diaries, and an event log. |
Services¶
| Service | Role |
|---|---|
| Gitea and Gitea Actions | Hosts our repositories and runs CI, including the image build. |
| Docker Hub | Distributes the published images. |
| Central MemPalace server | The palace shared by every device: memory, diaries, knowledge graph and the mailbox. |
| Amazon Bedrock | The default model provider. |
| ERDC inference | A second model provider, plus the classifier models that the safety guardrails use. |