Not gateway-first
E:Voice is the control surface, not just a remote dashboard. It lives where you are.
What sets E:Voice apart
E:Voice is not a chatbot skin and it is not trying to replace every advanced agent stack. It is a mobile-first cockpit for using agents, projects, tools, bridges, and proof without living in a terminal.
Control work naturally
Speak tasks, review status, and keep work moving without sitting at a terminal.
Frank to Foreman to Specialists
Frank scopes the request. Foreman plans the work. Specialists handle focused execution.
Obsidian-style context
Daily logs, sessions, project notes, core memories, tags, links, search, and cleanup controls stay visible to users and agents.
Proof should come back
Meaningful actions should leave a trace: who acted, what ran, what changed, and what proof came back.
Heavy work runs off-phone
Android stays light. Builds, logs, artifacts, and proofs run where they belong.
Low-latency speech loop
Native voice-to-text and TTS options keep the phone responsive without forcing every voice action through a cloud round trip.
Bring your bridge
Use E:Voice alongside OpenClaw, Hermes, custom HTTP runtimes, or other approved agent systems.
Pair E:Voice with AERIS OS.
E:Voice is the phone and voice cockpit. AERIS OS is the desktop and browser mission-control layer for agents, machines, dashboards, files, shared memory, calendar, email, docs, and stack orchestration.
E:Voice stands alone
Mobile control for agents and projects.
Speak tasks, review status, and approve work from Android.
Use Frank, Foreman, specialists, memory, receipts, downloads, and Build Factory lanes.
Keep the app focused as the mobile command surface for your work.
AERIS OS expands the stack
Mission control for machines, dashboards, and shared context.
Detect systems such as OpenClaw, Hermes Agent, Agent Zero, OpenHands, Open Human, and custom runtimes.
Localize files, dashboards, docs, email, calendar, and shared Obsidian-style memory.
Use E:Voice as the on-the-go voice surface for the same ecosystem.
E:Voice
Talk to agents, route work, review proof, and keep projects moving away from the desk.
AERIS OS
Connect the dashboards, machines, files, and agent systems that power the stack.
One context layer
Carry project facts across Hermes, Codex, Claude, AERIS agents, and E:Voice sessions.
$20/month target
E:Voice at $5/month and AERIS OS at $15/month are designed to work together without replacing your stack.
New to agents? Start simple. Already have a stack? Bring it with you.
For people starting from chat
You do not need to learn terminal agents first.
Talk naturally from the phone.
Let Frank turn the idea into a project.
Let Foreman organize the work into steps.
Review progress, blockers, artifacts, and proof in a mobile UI.
For power users
Keep your stack and add a cockpit.
Add voice and mobile approvals without throwing away your tools.
Add project orchestration, memory visibility, and receipts.
Use Build Factory, Codex, Companion, OpenClaw, Hermes, or a custom bridge where each one fits.
Treat E:Voice as the front door, not a forced replacement.
Where E:Voice fits
A careful comparison, not a takedown. Each category is useful. E:Voice focuses on making agent work mobile, visible, and project-centered.
| Category | ChatGPT-style chat | Terminal or gateway agents | E:Voice |
|---|---|---|---|
| Primary interface | Conversation window | Terminal, server, dashboard, or IDE | Android-native mobile cockpit |
| Voice-first workflow | Often available, usually conversation-focused | Usually not primary | Designed around speaking tasks and reviewing work from the phone |
| Mobile-native experience | Strong for chat | Often PC or server-first | Built for mobile approvals, status, projects, and routing |
| Project cockpit | Usually not a full project layer | Powerful, but often fragmented across tools | Projects, agents, bridges, receipts, updates, and build proof in one lane |
| Agent orchestration | Limited or hidden | Deep, but technical | Frank intake, Foreman planning, specialists, and bridge routing |
| Memory visibility | Varies by platform | Depends on the stack | Obsidian-style memory vault with layers, search, tags, links, metadata, and cleanup controls |
| Tool receipts and proof | Often conversational summaries | Logs and artifacts, if wired | Action receipts and proof surfaces keep work inspectable |
| Local desktop power | Not the primary model | Strong when configured | Desktop Companion is an early-stage local power layer for approved tools and proof |
| Works with existing stacks | Usually through plugins or APIs | Native to the stack | Designed to complement OpenClaw, Hermes, custom HTTP bridges, and Codex lanes |
| Beginner friendliness | High | Lower | Start with Frank and Foreman, then grow into advanced routing |
| Power-user depth | Good for reasoning and drafting | Very high | Mobile cockpit for advanced execution, not a replacement for every stack |
Architecture without the mystery
E:Voice keeps the control surface simple while leaving room for deeper execution lanes underneath.
Main Lane
User speaks->Frank scopes->Foreman plans->Specialists work->Build Factory executes->Receipts return
Power Lane
Custom Foreman->Custom Specialists->Secondary Bridge->CodexOpenClawHermesCustom HTTP
Companion Lane
E:Voice Android->E:Voice Companion->Local toolsFilesBuildsPlugins
What is in the cockpit now
E:Voice is already a working Android cockpit and keeps growing. These are the surfaces the product story now leads with.
- Android app
- Chat and voice input
- Model provider configuration
- Frank intake
- Foreman orchestration
- Specialist agent flow
- Build Factory routing
- Android update delivery
- Obsidian-style Memory Vault
- Daily logs, sessions, project notes, and core memories
- Search, tags, links, metadata, pinning, and deletion
- Local E:Voice Docs for notes, prompts, reports, and agent generated documents
- Local speech-to-text options
- Local TTS options
- Provider keys and OAuth image generation
- Agent profile picture generation
- Custom agent creation and role templates
- Codex task dispatch
- OpenClaw and Hermes bridge lanes
- Custom HTTP runtimes
- Theme maker
- Per-agent card colors and wallpapers
- Desktop Companion in early development
What you can use it for
Build an app from your phone
Start with a voice note, scope the project, route the build, and review proof when execution returns.
Manage work away from the desk
Check status, unblock tasks, and approve the next lane from Android.
Turn notes into projects
Frank captures intent and Foreman turns it into structured work.
Dispatch coding tasks to Codex
Use E:Voice as the intake and approval surface for source work.
Review artifacts and proof
Keep builds, logs, updates, receipts, and release proof attached to the work.
Use your existing stack by voice
Bridge to OpenClaw, Hermes, or custom runtimes without making them the only front door.
Power is useful only when you can see it.
E:Voice should show what agents can do, what they did, what they remembered, and which bridge handled the work.
Know which agent owns the conversation, the plan, and the execution lane.
Approved tools and bridges should be explicit, reviewable, and scoped to the project.
Every meaningful action should produce a trace users can inspect.
Users and agents can search linked daily logs, sessions, project notes, and core memories instead of relying on short-lived context.
Project bridge controls keep OpenClaw, Hermes, Codex, Companion, and custom runtimes understandable.
Artifacts, logs, update delivery, and proof should stay attached to the work.
Desktop Companion brings local power into the loop.
E:Voice Companion is in the early stages of development. It pairs your phone with your computer, exposes approved tools, manages local projects, and brings desktop proof back into the mobile cockpit without asking users to install a full agent gateway.
Easy pairing
Connect a phone to an approved desktop workspace.
Local projects
Keep project context close to the machine that can execute it.
Tool management
Expose only the tools and files that should be available.
Codex adapter
Route coding work through the desktop when the lane is approved.
Plugin packs
Reviewed skill packs can extend local execution safely.
Receipts and logs
Local actions should return proof to the mobile cockpit.
Local-first control
Use desktop power without giving up review and approval.
No forced replacement
Companion should work alongside advanced stacks instead of hiding them.
Gallery
The current photo shoot shows the product as it is used: chat, memory, docs, skills, voice settings, agent creation, image generation, appearance, themes, and stack-aware agent cards.
Agent cockpit
Landscape chat shows the core idea: color-coded agents, live connection, Frank intake, bottom navigation, and a focused project conversation.
Stack-aware agents
Agent cards expose roles, custom identities, recent activity, and visual colors for different stacks.
Memory Vault
Obsidian-style memory organizes daily logs, sessions, projects, core memories, links, tags, and searchable context.
E:Voice Docs
Local docs bring notes, to-do lists, prompts, reports, and agent-generated documents into the app.
Providers and images
Provider keys, services, OAuth image generation, navigation preferences, and local app settings stay visible.
Local voice models
Vosk offline STT and local TTS choices support low-latency voice loops on Android.
TTS control
Saved voices, local encryption, preview controls, and provider selection make voice output configurable.
Theme maker
Customize agent card colors for Frank, AERIS, OpenClaw, Hermes, and choose wallpapers for the app.
Create or add agents
Create native AERIS agents or add external runtimes with role templates and identity controls.
Generated profiles
Agent setup can upload or generate profile pictures using OAuth image generation and editable prompts.
Skills
Skill cards keep available agent capabilities organized by need, status, and workflow.
Research agents
Specialists can carry focused conversations while staying inside the same mobile cockpit.
Custom agents
Custom agents keep their own identity, wallpaper, color, and execution context.
Design specialists
Specialists like Torx can hold UI direction, critique, and design implementation context.
Visual work
Chat can carry image-heavy planning, references, and proof instead of staying text-only.
Long-form intake
Frank can keep detailed product, build, and planning conversations readable on mobile.
AERIS system lane
System identity, versioning, preview status, and execution boundaries are visible inside the app.
App preferences
Settings expose defaults, voices, models, and app behavior without hiding control in backend config.
Navigation and appearance
Bottom tabs, builder profile, runtime, and appearance controls make the app adjustable to the workflow.
Start with 10 free days. Keep E:Voice for $5/month.
Talk to Frank. Let Foreman organize the work. Choose where execution happens: Android, Build Factory, Codex, Companion, OpenClaw, Hermes, AERIS OS, or a custom bridge. Access codes can unlock trial, creator, tester, partner, or earned use windows.