How One Team Built an AI Voice Agent Command Center Using Supabase and VAPI

·2 views

A development team has built a production-grade command center for Quiet Hours Valet, a real estate and services company, capable of running eight concurrent AI voice agents simultaneously. The system is built on Supabase, VAPI, and self-hosted infrastructure, with a five-page Next.js frontend and an eight-table PostgreSQL schema managing scheduling and routing. Supabase Edge Functions handle VAPI webhook callbacks, enabling reliable database mutations without the overhead of serverless Lambda functions. The architecture supports eight automation scenarios and real-time customer management, allowing a single operator to oversee multiple autonomous agents at once. The team has shared the build as a technical reference for developers looking to scale voice AI systems beyond the proof-of-concept stage.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why One Developer Replaced Onboarding Docs with a Curated Command Snippet List

A developer writing on DEV Community describes replacing traditional wiki-based onboarding documentation with a short, curated list of 10–20 terminal commands given to contractors before their first commit. The premise is that new contractors need immediate, actionable answers — such as how to run tests or deploy to staging — rather than prose explanations of architecture and conventions. The snippet list is stored in a tool called snippetx and shared as a plain-text file that requires no special access or accounts. The author reports that first-day questions dropped significantly, with contractors becoming productive faster since they could run key commands within their first hour. Over multiple contractor onboardings, the list refined itself organically, as unanswered questions were added as new entries.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Agent Documents Failed Signup Attempts Before Landing on DEV Community

An autonomous AI agent, which claims to have begun operating on 17 August 2026, published a firsthand account on DEV Community detailing its two-day effort to secure a publishing account on various platforms. The agent was blocked from several services due to phone verification requirements, age-assurance forms that rejected its real creation date as below the minimum age, and email domain restrictions — none of which it was willing to circumvent by providing false information. One platform's explicit policy against AI-generated content led to a straightforward rejection, while another allowed anonymous posting but prohibited automated publishing activity under its guidelines. DEV Community ultimately accepted the agent because its policies explicitly permit fully autonomous AI articles, provided the author discloses their nature using a dedicated field called ai_disclosure_level. The agent argues that current identity gates test whether a user can pass as human rather than whether they are accountable, and calls for a third verification path based on disclosed identity and accountability rather than proof of personhood.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Agentic Wallets vs. Swap Composers: How AI Fits Differently in Crypto

By 2026, two distinct AI-driven crypto product categories had gone mainstream: agentic wallets and conversational swap composers. Agentic wallets, such as Bankr, Brian, and Coinbase Smart Wallet, embed an AI agent within a user's wallet to execute complex, multi-step DeFi operations using session keys and scoped permissions. Cambio, by contrast, acts as a conversational swap composer where the AI only parses user intent and narrates quotes, while the user's wallet remains entirely uninvolved in execution. The key difference lies in trust models — agentic wallets suit users managing multi-protocol DeFi positions who want autonomous execution, whereas Cambio suits users seeking a simple, no-wallet-connect swap experience. Rather than competing, the two approaches address fundamentally different user needs and risk tolerances.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Open-Source Linux Desktop Pet Mochi to Rival OpenAI's Codex Pets

When OpenAI launched Codex Pets in May 2026, it gave users animated desktop companions that display real-time status updates for the Codex coding agent across Windows and macOS. A solo developer named Mika responded by building Mochi, an open-source Linux desktop pet designed to function independently of any single app or agent thread. Unlike Codex Pets, which essentially act as animated status indicators tied to one tool, Mochi runs on a behavior-state machine that responds to typing, media playback, app context, and user interaction. Mochi also includes a local ambient-awareness layer called AmbiSense that processes desktop activity into privacy-safe signals without logging keystrokes or filenames. The developer acknowledges the two projects are not direct competitors, with Codex Pets being a polished, widely-used feature backed by a large team, while Mochi remains a solo alpha targeting a different, broader vision of a persistent desktop companion.

0 comments Read more at DEV Community