You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -177,7 +177,7 @@ The spike tests are the heavy end-to-end path. They build images, run Docker, an
177
177
- Multi-arch cllama image: `docker buildx build --platform linux/amd64,linux/arm64 -t ghcr.io/mostlydev/cllama:latest --push cllama/` using the `multiarch-builder` buildx builder.
178
178
- User-defined `healthcheck:` in `claw-pod.yml` takes precedence over driver defaults. The override happens in `compose_emit.go` — check `serviceOut["healthcheck"]` before applying `result.Healthcheck`.
179
179
-`Service.Compose` in the pod parser preserves all non-`x-claw` compose keys as a deep-copied `map[string]interface{}`. This is how user healthchecks, depends_on, command, etc. flow through.
180
-
- Releases: use `gh release create` with semver tags. cllama has its own tag namespace (e.g. `v0.1.0`) published from the submodule repo. ghcr.io packages default to private; must be set public via GitHub UI after first push.
180
+
- Releases: use `gh release create` with semver tags. cllama has its own tag namespace (e.g. `v0.1.0`) published from the submodule repo. ghcr.io packages default to private; must be set public via GitHub UI after first push. Pre-built `claw` binaries are published via `goreleaser` (`.goreleaser.yml` is in-tree) — do not suggest adding goreleaser, it already exists. `install.sh` downloads the latest release with checksum verification; `claw update` re-runs it.
181
181
-`claw-api` image is not published to ghcr.io. The `ensureImage` fallback tries a git URL build which fails because the Docker builder cannot access the private cllama submodule. Build it locally from the repo root: `docker build -t ghcr.io/mostlydev/claw-api:latest -f dockerfiles/claw-api/Dockerfile .`
182
182
-`claw-wall` image is built from `dockerfiles/claw-wall/Dockerfile` with `.` context and published to `ghcr.io/mostlydev/claw-wall:latest`. The `ensureInfraImages` fallback applies: local image → `docker pull` → local Dockerfile build. Multi-arch build: `docker buildx build --platform linux/amd64,linux/arm64 -t ghcr.io/mostlydev/claw-wall:latest --push -f dockerfiles/claw-wall/Dockerfile .`
183
183
-`hermes-base` image is built from `dockerfiles/hermes-base/` and published to `ghcr.io/mostlydev/hermes-base:<tag>` (e.g. `v2026.3.17`). It installs `hermes-agent[messaging,cron]` from the pinned upstream tag, then runs `patch-hermes-runtime.py` to apply compatibility fixes. The patch disables the `members` and `voice_states` Discord intents, makes slash-command sync non-blocking (best-effort with timeout), and — critically — sets `allowed_mentions=discord.AllowedMentions(replied_user=False)` on all `channel.send()` calls that carry a reply reference. Without this last fix, Hermes's reply feature auto-pings the original author, which in multi-agent pods creates mention loops even when `DISCORD_REQUIRE_MENTION=true`. Build: `docker buildx build --platform linux/amd64,linux/arm64 -t ghcr.io/mostlydev/hermes-base:v2026.3.17 --push dockerfiles/hermes-base/`.
0 commit comments