Files
headquarter/tool-images
Developer 070cd4d5a5 chore: track all project map and index files
Add generated .pi-map.md and .pi-map.index.md files across the repository
so the project navigation maps are shared and versioned. These artifacts
are maintained by project_map_init/patch/validate and must be kept in
sync with source edits.

Note: .cache/ remains ignored (added in previous commit).
2026-06-12 13:46:23 +00:00
..

Tool Images

This directory contains Dockerfile templates for the base tool types used in Headquarter.

Available Images

File Tool Description
base.dockerfile - Common base with git, nvim, ranger, tmux, node
code-server.dockerfile VS Code Browser-based VS Code with extra tools
jupyter.dockerfile Jupyter Jupyter Lab/Notebook with extra tools
opencode.dockerfile OpenCode OpenCode agent server
pi-agent.dockerfile Pi Agent Pi coding agent with full terminal setup

Usage

When creating a tool type in the Tool Workshop, you can reference these Dockerfiles:

  1. Copy the contents of the desired .dockerfile
  2. Paste into the "Dockerfile Template" field
  3. Set definition_type to dockerfile

Building Locally

To test an image locally:

cd tool-images
docker build -f pi-agent.dockerfile -t pi-agent:latest .
docker run -it pi-agent:latest

Customizing

All images include:

  • git - Version control
  • neovim - Terminal editor
  • ranger - Terminal file manager
  • tmux - Terminal multiplexer
  • htop - Process viewer
  • tree - Directory tree
  • jq - JSON processor
  • Node.js 20 - For npm-based tools

The pi-agent image additionally includes the Pi Coding Agent for AI-assisted development.

Adding New Images

  1. Create a new .dockerfile in this directory
  2. Use base.dockerfile as a starting point if applicable
  3. Document it in the table above
  4. Update the tool type in the database via the Tool Workshop