teabot go-live: install the user daemon and wire it to the estate #2

Open
opened 2026-08-02 16:24:31 +10:00 by unkinben · 0 comments
Owner

Problem
teabot is built, released (v0.1.0 RPM), and its personality bot users + the vault-plugin-secrets-gitea engine exist, but it is not yet running anywhere.

Proposal

  • install the teabot RPM as a systemd user service on the chosen host
  • write config: watched repos, poll interval, allowed_authors allowlist (start with benvin), personalities (implementer/reviewer) pointing at tea configs whose tokens come from the gitea Vault engine (gitea/creds/teabot-*)
  • ensure the container image (agent-dev) + docker + claude subscription config passthrough are present on the host; SELinux :z mounts
  • grant the two bot users collaborator access on the watched repos

Acceptance

  • teabot polls the watched repos, dispatches a one-shot Claude container on a new issue/PR from an allowlisted author, and posts back as the right personality; loop-prevention verified.
**Problem** teabot is built, released (v0.1.0 RPM), and its personality bot users + the vault-plugin-secrets-gitea engine exist, but it is not yet running anywhere. **Proposal** - install the teabot RPM as a systemd user service on the chosen host - write config: watched repos, poll interval, allowed_authors allowlist (start with benvin), personalities (implementer/reviewer) pointing at tea configs whose tokens come from the gitea Vault engine (gitea/creds/teabot-*) - ensure the container image (agent-dev) + docker + claude subscription config passthrough are present on the host; SELinux :z mounts - grant the two bot users collaborator access on the watched repos **Acceptance** - teabot polls the watched repos, dispatches a one-shot Claude container on a new issue/PR from an allowlisted author, and posts back as the right personality; loop-prevention verified.
Sign in to join this conversation.