Skip to main content

Changelog

Notable SLAW releases, newest first. Each entry lists the highlights; follow the version link for the complete release notes.

SLAW uses calendar versioning — vYYYY.MDD.0, where the date is the release day. Full release notes live in the releases/ directory of the repository.

Lineage

SLAW began as a fork of an upstream open-source project in June 2026. Releases and release notes that predate the fork belong to the upstream project and are not listed here.

13 June 2026 — Webhook signatures & cloud-tenant IP allowlist​

Security hardening for inbound trust (audit findings H2, H5):

  • Signed webhook deliveries — the jira-sync plugin can verify inbound Jira webhooks. Set webhookSecretRef and deliveries must carry a valid X-Hub-Signature (HMAC-SHA256 over the raw body) or they're rejected before any work runs.
  • Cloud-tenant source-IP allowlist — the trusted x-slaw-cloud-* header path can be restricted to edge-proxy IPs/CIDRs via SLAW_CLOUD_TENANT_ALLOWED_IPS, so a leaked shared token can't be replayed from elsewhere. Slaw warns at startup if the token is set without an allowlist.

See Jira Sync → webhook verification and Environment variables.

13 June 2026 — Botfather: enrollment trust hardening​

Security hardening for fleet enrollment (audit finding C2):

  • Pre-shared enrollment secret — set BOTFATHER_ENROLLMENT_SECRET and POST /enroll must present the matching secret (request field or x-botfather-enrollment-secret header), compared in constant time and rejected before any row is written, so the network can't seed the pending queue. Towers without a secret keep token-less enrollment (admin still gates admission).
  • Wildcard auto-approve guardrail — overly-broad rules (*, *.*, …) are refused at creation; machineId/hostname are self-asserted and spoofable, so a wildcard would admit any identity.

See Self-Hosting → Enrollment trust.

13 June 2026 — Botfather: admin auth & safe bind​

Security hardening for the control tower (audit findings C1, M5):

  • Loopback bind by default — the tower binds to 127.0.0.1 and refuses to start exposed off-loopback (BOTFATHER_BIND) without an admin token, so the admin API is never reachable off-box unauthenticated.
  • Authenticated admin API — /api/admin is guarded by a shared admin secret (BOTFATHER_ADMIN_TOKEN), compared in constant time; exposed-and-unconfigured admin requests return 503 admin_auth_required, while loopback dev stays zero-config.

See Self-Hosting and Security & sovereignty.

10 June 2026 — Public launch​

SLAW is open source under github.com/slaw-ai.

  • Telemetry-free — no product telemetry or feedback collection; the only data that leaves your machine is the model-provider traffic your own agents generate (see Security & sovereignty).
  • Leads-based roles — squads are structured around a Squad Lead with engineering, marketing, finance, and other lead roles beneath.
  • Operator governance — governance is exercised by the Operator, with approvals, budgets, and an audit trail.
  • Reliability & cost control — usage-limit circuit breaker, quiescence stand-down, wake-loop deduplication, done-acceptance gating, and bounded context (see Reliability & cost control).
  • Botfather control tower — optional self-hosted fleet control: enrollment approvals, budgets and limits, cost analytics, alerts, and a tower-mastered skill registry.
  • Jira sync plugin — bundled two-way board sync via a managed agent and routine (see Jira sync).

Next steps​