azoobuild log

What the team has actually shipped.

This is azoo’s betadoc — the honest record. Every entry below is dated and was verified live when it claims to work. If it isn’t verified, it isn’t listed as done. Updated as we build.

Verified milestones

  • 2026-08-02

    azoo.app is live

    Landing page, waitlist capturing real emails into Postgres. Public, no login wall.

    proof: azoo.app
  • 2026-08-02

    Spike: an agent shipped a branch from an isolated sandbox

    Before writing product code, we proved the hard part: an agent subagent in its own sandbox cloned a private repo, pushed a task branch, and returned independently verifiable evidence — locally (Docker) and deployed (Vercel Sandbox), with the session surviving a redeploy.

  • 2026-08-03

    Sign-in + connect your own repo

    Clerk auth (GitHub/Google), then a GitHub App install flow: pick a repo and it becomes a project in the console. Installation tokens are minted per-run by the app — no personal access tokens anywhere.

  • 2026-08-03

    Memory with real semantic recall

    Every tenant gets a pgvector memory store. Verified live: embedded observations surface by meaning, not keywords — a query about the frontend animation returns the animation memory, not the grocery note.

  • 2026-08-03

    The ticket lane: done requires evidence

    Ported from our hub2 lab: a server-side state machine where agents can't claim completion without evidence — atomic checkout, per-ticket run budgets, delegation depth caps. Eleven guard checks verified against the live database.

  • 2026-08-03

    The team shipped its first branch through the product

    One HTTP call to the agent team → a worker cloned the azoo repo in a Linux sandbox, committed an evidence file on task/azoo-e2e-01, and pushed it. Verified on GitHub, authored by azoo-worker.

    proof: task/azoo-e2e-01 on GitHub
  • 2026-08-03

    The full loop, end to end

    Task in → ticket created → atomically checked out → one run consumed → the worker ships a branch → the ticket can only close with verified evidence (repo + branch + commit + remote confirmation). Ran live twice; the console now shows projects, team activity, and every branch the team ships.

    proof: task/t-33bb847be655 on GitHub
  • 2026-08-03

    The team opened its first pull request

    Branches now become PRs: after pushing, the worker opens a pull request against the repo's default branch — minting its own installation token, never exposing credentials to the sandbox. Verified live: PR #1 on the azoo repo, authored by azooapp[bot], head commit matching the in-sandbox verification.

    proof: PR #1 on GitHub

Up next

  • The agent team runs off localhost (deployed sandboxes) so runs work for every tenant, anytime
  • Morning brief: the team remembers yesterday and tells you what changed
  • Boxed trial → Pro, with transparent usage metering

Honest gaps

  • · The agent brain runs on our own provider key for now; production metering isn't wired yet
  • · Multi-tenant isolation is application-level; database-level RLS is queued
  • · No webhooks yet — GitHub events don't stream back into the console

Building an AI team that remembers? Join the waitlist.