Multi-Agent Personal Assistant

Amara

An always-on AI assistant that monitors your communication channels, triages autonomously, delegates to specialist agents, and ensures nothing slips through the cracks. A digital chief of staff, not a chatbot.

Most AI assistants wait to be asked
They're powerful when directly invoked and inert otherwise. They don't track tasks across sessions, follow up on stalled work, or monitor your channels for urgency. A real assistant is proactive. Amara is proactive.
Built for speed and reliability
<200ms
Triage decision latency (P95)
90%
Messages handled autonomously
<1s
Acknowledgment latency (P95)
Manager, not doer
Amara runs on a fast, inexpensive model and acts purely as a coordinator. She never does deep work herself. She delegates to specialist agents, each with their own model, tools, and mandate.

Communications Agent

Monitors all inbound messages. Classifies urgency. Drafts replies. Handles 90% of traffic autonomously.

Research Agent

Web search, document analysis, and summarization. Surfaces what you need to know when you need it.

Coding Agent

Code changes, pull requests, and deployments. Delegated work with structured input/output contracts.

Writing Agent

Prose, content creation, and document drafting. Specialist quality without context-switching.

Two modes of operation
  • Direct mode. Talk to Amara explicitly. Every message enters the full orchestrator pipeline for planning and delegation.
  • Monitored mode. Passive observation of all your channels. A fast triage layer makes autonomous decisions on 90% of messages in under 200ms. Only 10% escalate to the orchestrator.
  • Task persistence. Every task persists in SQLite with WAL mode. Nothing is forgotten across restarts. Stalled work is automatically re-queued.
  • Follow-up engine. A scheduler heartbeat re-checks in-progress tasks. If something stalls, Amara escalates to you rather than letting it rot.
  • Multi-channel. WhatsApp, Gmail, Calendar, iMessage, Telegram, and more via a normalization layer that makes adding new channels trivial.
Read-only by default
Monitored channels are read-only. Sending a message in a monitored channel requires explicit user authorization. Every outbound message is logged with an audit trail. PII auto-purges after 90 days. Docker sandboxing with network isolation per session.
Discuss a build like this