The template carried the old multi-tool/agentsquad-era CAD-executor scaffold. Refresh it to the consolidated single-harness reality (hyperguild#75/#76): Claude Code + hyperguild, session-based, brain + gitea MCP. No dispatch automation added (out of scope — dispatch stays manual until real friction warrants it). Removed (multi-tool + dead generator + deployed-agent-era): - .aider.conf.yml, .aider.conventions.md, .cursorrules - .context/ (mcp.json, PROJECT.md, system-prompt.txt) - agent-policy.yaml (k8s NetworkPolicy scaffold) - scripts/context-sync.sh (generated the above from .context/PROJECT.md — now input-less) + its context:sync* Taskfile tasks Added / updated: - .mcp.json (root, hyperguild-shaped: brain + gitea, Bearer env tokens) - CLAUDE.md / AGENTS.md / README.md → single-harness workflow (issue → hyperguild session → PR → report-back comment → brain capture) - AGENT_BOUNDARIES.md kept (harness-agnostic egress/scope guidance); repointed its two references to the removed agent-policy.yaml Left alone: cd.yml, Dockerfile, Taskfile (build/test), go.mod, cmd/, internal/, pkg/, .claude/. No dangling refs to removed files (verified). Refs infra#178. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.5 KiB
PROJECT_NAME
Identity
- Name: PROJECT_NAME
- Owner: Mathias
- Client: personal
- Repo: git.d-ma.be/mathias/PROJECT_NAME
- Status: active
Stack
Go + ADK + LiteLLM. Claude Code tree-walks to ~/dev/CLAUDE.md for cross-project conventions.
Agent
TODO: describe what this agent does, what tools it has, and what it's responsible for.
Harness & workflow
Single harness: Claude Code + hyperguild — session-based (you start a session, it works,
it stops; there is no push-triggered dispatch). MCP connections are in .mcp.json: brain
(knowledge query/write) and gitea (issues/PRs/repo — the audit trail). Provide
BRAIN_MCP_TOKEN and GITEA_MCP_TOKEN in the environment.
The loop for a unit of work:
- Issue — the work is a Gitea issue (scope, acceptance criteria, report-back format).
- Session — a Claude Code + hyperguild session does the work in this repo.
- PR — branch off
main, open a PR; CI (task check) is the gate. - Report-back — comment the outcome on the issue (issue comments are the audit surface).
- Brain capture — if a learning is durable and non-obvious, write it to the brain.
Observability
Traces → Jaeger via OTLP_ENDPOINT. Set ADK_SERVICE_NAME=__PROJECT_NAME__ per deployment.
Spans emitted: invoke_agent, generate_content. Tool spans require custom callbacks.
Boundaries
Runtime scope (network egress, file scope, approved operations) is in AGENT_BOUNDARIES.md —
read it before adding tools, endpoints, or write access.