gcontext packages

The public registry of gcontext packages. One folder per package.

A package is a portable capability you install into a repo's context/packages/ folder. It holds instructions (act files), durable knowledge (known files), scripts, and its own state folders. The context standard is documented at https://gcontext.ai/standard.

Install a package

With the gcontext CLI:

uv tool install gcontext-ai
gcontext install <name>

Manually: copy the package folder into context/packages/ and run uv run context/_system/scripts/check.py --check.

Package layout

<name>/
  package.yaml        name, version, description, tags, secrets, deps
  act.<name>.md       the package's instructions
  _index.<name>.md    generated index
  scripts/            managed scripts (optional)
  state folders       package-owned state (backlog/, runs/, ...)
  local/              user space, never touched by updates

package.yaml fields: name (string, required), version (integer, required), description (string), tags (list), source (string), secrets (list of secret NAMEs, values live in the repo's secrets.env), deps (list of pinned Python packages), config_required (bool), state_gitignored (bool).

Submit a package

Open a pull request that adds one folder at the repo root. The folder must pass check.py when placed inside a standard context/packages/ tree. Keep state folders empty except their _index files.