Front Stays the Truth While Agents Do Support Work

·https://github.com/skillrecordings/support
repoaicustomer-supportagentshitlinngestslackfronttypescriptcli

The Front source-of-truth plus Slack approval loop maps cleanly to joelclaw gateway workflows and agent trust gates.

Skill Recordings Support is an agent-first support platform for Skill Recordings products like Total TypeScript and Pro Tailwind. Front stays the conversation source of truth. Agents classify, draft, route, and remember. Humans approve through Slack or a Next.js dashboard.

That’s the clever bit: don’t replace the support desk. Keep Front where the actual customer conversation lives, then run the messy agent work in the middle with Inngest durable workflows, trust scoring, audit logs, and approval buttons. If confidence and trust are high enough, the system can auto-send through the Front API. Otherwise a human reviews the draft.

Joel’s original Slack note was short: “this is workin very well.” That’s useful signal. This is not just a toy agent bolted onto a help desk. It’s a full operating surface: Bun workspaces, Turborepo, PlanetScale with Drizzle, Upstash Vector, Upstash Redis, Claude through the AI SDK, Axiom, Langfuse, and a skill CLI with skill doctor so agents and teammates can actually get the damn thing running.

The pattern is very joelclaw: make the human approval point explicit, keep the system observable, and give agents a CLI they can use without spelunking through docs every time.

Key Ideas

  • Front remains the source of truth, which avoids the classic support automation trap where the bot invents its own parallel customer record.
  • Inngest runs the durable support workflow: inbound webhook, classify, draft, request approval, send through the Front API, and update trust.
  • Slack approval buttons make the human-in-the-loop step fast enough to use without opening a whole dashboard.
  • Trust scoring creates a path from manual approval to auto-send instead of pretending every ticket should be automated on day one.
  • The skill CLI gives agents an install, auth, and doctor surface, which is the difference between “interesting repo” and “team can operate this thing.”
  • The architecture splits concerns cleanly across apps/front, apps/slack, apps/web, and packages for core workflows, database, SDK, memory, UI, and the CLI.

Links

← All discoveries