Skip to main content
Everything your assistant’s brain does — the reasoning loop, memory, steerable tasks, voice — lives in the MIT-licensed unifyai/unify repository, and you can run it locally. A local deployment gives you one teammate running entirely on your laptop, talking to the hosted Orchestra backend for persistence, so you can trace exactly how it thinks while keeping the zero-maintenance storage layer. The shape is deliberately simple: install once, and the runtime lives on your machine, accumulating state across every session. No Docker, no Kubernetes, no local database.

​
What runs where

The local runtime drives the assistant record whose ASSISTANT_ID you set, provisioned at console.unify.ai. Locally you get:
  • Chat — an interactive REPL with the full ConversationManager + Actor runtime behind it. An LLM key (OpenAI, Anthropic, or DeepSeek) is what lets it think and reply.
  • Browser voice calls — the production fast-brain (interruption-handling, telephony-aware) running locally with sub-second latency. See Voice.
  • Web search — a free Tavily key lets it look things up while researching.
  • Computer use — it drives a real browser and desktop; an optional AntiCaptcha key lets it get past CAPTCHAs instead of stalling.
The onboarding flow, inbound messaging channels (SMS / WhatsApp / phone, Slack, Gmail, Outlook, Teams, Discord), Google / Microsoft workspace connect, third-party app integrations, screen-share, and the multi-teammate experience are part of the hosted product at console.unify.ai.

​
The runtime stack

The open one-teammate runtime is three MIT-licensed repos. They talk to the hosted Orchestra backend; you can also use any of them independently.
RepoRole
unifyAgent runtime — managers, tool loops, CodeAct, voice, orchestration
unisdkPython SDK — how the runtime talks to Orchestra
unillmLLM access layer — OpenAI, Anthropic, or any compatible endpoint
orchestraPersistence backend — hosted at console.unify.ai

​
Start here

Installation

One command, a key wizard, and a unify CLI in your PATH — a few minutes on macOS, Linux, or WSL2.

Voice

Real browser voice calls with sub-second latency — LiveKit Cloud plus free-tier speech keys.

Day-to-day usage

The CLI commands, chatting, and steering work while it’s mid-task.

Custom overrides

Seed contacts, guidance, tasks, secrets, and reference data from version-controlled files.

Developers

How the runtime is put together, running the tests, and where to start reading the code.