Continuity
resumes saved sessions and allows a person to steer the assistant while it is working.
Animus
Persistent agent assistance and a related configurable voice-reception backend.
My role
migrated the assistant to persistent Pi, connected proactive workflows and implemented the related receptionist backend.
The problem
Ongoing agent work and service-business calls need useful context, configured actions and clear boundaries around human decisions.
The approach
Extended third-party Pi for persistent agent work and built a separate tenant-aware receptionist backend. The assistant uses memory and reviewed actions; voice-provider adapters connect configured businesses to calendars, technician matching and confirmations.
What it enables
Supports continuing agent work across sessions and gives service-business reception a configurable path to availability, bookings and confirmations.
The work,
and its boundaries.
Connected capabilities
combines memory, MCP tools, and delegated agent tasks within the same assistant experience.
Architecture
separates the conversational runtime from email/calendar event handling and notification delivery.
Human oversight
routes intercepted actions to an approver and sends relevant events or escalations through Discord.
Operational boundaries
respects active hours and disables proactive Google workflows when the required access or configuration is unavailable.
Receptionist architecture
a separate tenant-aware service routes verified voice-provider events to calendar, technician and optional messaging adapters, retaining call events for investigation.
Scope
the receptionist is a connected backend implementation with synthetic demo setup, not a demonstrated production deployment or compliance-certified platform.
Technology
- TypeScript
- Pi Runtime
- MCP
- Discord.js
- Google APIs
- SQLite
- Fastify
- Vapi
- Twilio
Let’s make your next project workable.
Talk with me about the product, the engineering and the decisions that need to stay with people.