v1.0.0

botler-agent 1.0.0 — the Go implementation is the release.

A single static binary, no Node runtime: the TypeScript + pi SDK pipeline has been rewritten in Go on
adk-go. Config and data layout are unchanged from v1 (~/.botler-agent/, DATA_ROOT,
schedules.json, task logs), so an existing install keeps working — only the artifact you run changes.

What 1.0 ships

• One static binary (CGO-free) or the multi-arch Docker image (linux/amd64 + linux/arm64).
• Same bounded toolset: read / write / edit / run / schedule, plus IM-only clear_conversation_context. run still only executes existing in-project python3/node scripts; schedule still only writes the fixed externalized schedules.json. No arbitrary shell, path allowlist unchanged.
• Channels: Telegram, and WeChat iLink with QR login, inbound images (vision input), and 24h-window renewal reminders.
• Scheduler: cron / interval / at / once, holidayMode: "workday" (China legal-workday gating incl. 调休补班), and push delivery with channel fallback.
• Ops: WebUI, /healthz + metrics, JSONL task logs, per-subproject git commit and self-healing push (GIT_PUSH=1, with ssh/known_hosts/identity mounted into the container).
• Parity harness: go run ./scripts/parity diffs the Go runtime against the v1 TypeScript reference, which stays in-tree at src/ for that purpose only.

Upgrade

# Docker
docker compose pull && docker compose up -d --force-recreate

# from source
git pull && go run ./scripts/install

Breaking change

The npm CLI is no longer distributed — install from source (go run ./scripts/install) or run the
Docker image. src/ is kept solely as the parity reference.

What's Changed

• feat: Go rewrite of botler-agent on adk-go (v2-golang) by @crossoverJie in #17
• build: stop shipping the npm CLI, distribute only the Go binary and image by @crossoverJie in #18

Full Changelog: v0.5.1...v1.0.0