gald3r_core — Product Docs¶

This is the end-user product documentation for gald3r_core: the thing you install and run to get task/bug tracking, agent runs, and the CRASH (Commands/Rules/Agents/Skills/ Hooks/Verbs) system in your own project. It is deliberately separate from this repo's contributor docs (AGENTS.md), which describe how to work on gald3r_core itself, not how to use the finished gald3r command in a project of your own.

Runs on Windows, macOS, and Linux. One CLI, three platforms — signed Windows binaries (.msi + dual-exe), a macOS .pkg (notarized binary), and a Linux tarball installer ship from every release. See Install for the per-OS quick start.

What is gald3r?¶

gald3r is a single-binary CLI coding-agent platform: a task/bug tracker, a multi-provider agent runtime (local models via Ollama/LM Studio/vLLM, or cloud providers), and the CRASH component system (Commands, Rules, Agents, Skills, Hooks, and CLI Verbs) that turns those into enforced, executing behavior in a project — not just markdown instructions an LLM might follow.

It is built to be comparable to tools like Claude Code, Cursor's agent, or OpenCode, but standalone: one binary, no required IDE.

Who this is for¶

Someone who wants to use the gald3r command in their own project (task tracking, agent runs, project scaffolding).
Someone evaluating gald3r_core as a product, distinct from the frameworks/templates it absorbs capability from.

If you are instead working on gald3r_core's own source code, start with the root AGENTS.md instead — this directory is not for you.

Where to go next¶

Doc	Covers
`install.md`	Every supported install path — signed binary, from-source build, per-platform IDE overlays
`quickstart.md`	Install → first run → first useful command
`first-project.md`	A complete walkthrough — scaffold a new project, create real tasks, run one through to `completed`
`concepts.md`	The handful of ideas you need before anything else makes sense: CRASH, `.gald3r/`, tasks/bugs, sessions
`commands.md`	Slash commands (`/g-` / `@g-`) — what they are, when to reach for one, the highlights
`skills.md`	Skills — the instruction packages commands dispatch to, and what loads automatically
`agents.md`	Named agents — when to invoke one directly instead of letting a command route for you
`verbs.md`	The `gald3r <verb>` CLI surface — the commands you type straight into a terminal
`crash.md`	CRASH (Commands/Rules/Agents/Skills/Hooks) explained end to end, with real examples
`task-bug-workflow.md`	The full task/bug lifecycle — create, claim, verify, archive — with real command output
`autopilot.md`	`go` / `go-code` / `go-review` / `autoclaim` / `swarm` / `autopilot` — letting gald3r work the queue itself
`coordination.md`	Multi-project coordination: Valkyrie (live) and WPAC (file-based, offline-first)
`memory.md`	Scoped memory records and the file-first vault knowledge base
`local-ai.md`	Running gald3r entirely against a local model (Ollama, LM Studio, vLLM, llama.cpp) — no cloud account required
`plugins.md`	Installing community plugins and curated skill packs
`troubleshooting.md`	`doctor`/`selftest`/`errors` output explained, and fixes for the most common issues

Current status¶

gald3r_core is in public beta. Every release ships signed binaries and per-OS installers for Windows, macOS, and Linux — see Install for the current recommended path. Some verbs depend on optional network services (e.g. world_tree for multi-project sync via Valkyrie); those are called out on the pages that cover them. This doc set documents commands as actually run against a real project, not written from memory — treat anything shown running on a page as the current, verified behavior for that page.

No PyPI package exists. pip install gald3r-core does not work — use one of the install paths on the Install page instead.

Scope note¶

This directory's Markdown is also wrapped in a generated static site (MkDocs + Material) — see "Building the docs site locally" below. The Markdown itself remains the source of truth (readable directly on GitHub, no build step required); the site is a richer presentation of the same pages with navigation and search.

Building the docs site locally¶

The site config lives at mkdocs.yml (repo root) and builds every page in this directory into a searchable static site with Material for MkDocs navigation. It does not include this repo's contributor docs (root AGENTS.md and friends).

# One-time: install the docs build tooling
uv sync --extra docs
# or: uv pip install mkdocs mkdocs-material

# Build a static site into ./site/ (gitignored — never commit build output)
uv run mkdocs build --strict

# Or serve it locally with live-reload at http://127.0.0.1:8000
uv run mkdocs serve

mkdocs build --strict is the verification command — it fails the build on any content warning. Links from these pages out to the repo-root contributor docs (../../AGENTS.md, ../../GALD3R.md) are expected to resolve outside docs_dir; mkdocs.yml's validation.links config downgrades that specific, known pattern from warn to info so the build stays clean without masking genuine in-site broken links.