Not a VM in someone else’s cloud — Agenvoy runs as a daemon on your computer and keeps memory, schedules, tools, and credentials on your own disk.
Say what you need in one sentence; it builds the tool, sandbox-tests it, and shares it with Claude Code, Codex, and any MCP agent.
curl -fsSL https://agenvoy.com/scripts/install.sh | bash
Agenvoy is a Taiwan-developed AI Agent Harness by Pardn Chiu, built to turn conversation into completed work on your computer. It coordinates models, context, tools, real-time data, task routing, memory, schedules, and execution in one workflow, while keeping control of your files and environment in your hands. Through the Web interface, it also supports real-time voice conversation you can interrupt mid-sentence, which hands work to the chat agent and narrates its progress aloud; the full result remains available in the chat.
Meta Muse, OpenAI dots, and Grok Bot each run your agent on a cloud VM the vendor operates, with your logins inside it. Agenvoy runs on the computer you already own, so you decide what leaves it.
Sessions, memory, and schedules live in SQLite under ~/.config/agenvoy. No Agenvoy account, no hosted copy.
API keys and OAuth tokens sit in the OS keychain and are used by the local daemon. The browser page never receives them.
Commands run under sandbox-exec on macOS or bwrap on Linux with network off unless you approve it for that call. Management endpoints answer localhost only.
Use the provider you trust, or point Agenvoy at Ollama or LM Studio so prompts never leave your machine.
Manage sessions, tools, schedules, and memory from a browser. The dashboard ships inside the binary — start the daemon and open http://127.0.0.1:17989. It is served by your own machine, so nothing leaves your device.
Auto-built tools and a built-in MCP server at the core — plus multi-model routing, scheduling, and memory, all in a single Go binary.
Ask for anything. If no tool exists, the agent builds one — writes the script, tests it in a sandbox, and registers it. Next time, it's already there.
Server mode shares every sandboxed tool with Claude Code, Codex, and any MCP client — which can auto-build new tools too. Client mode calls external MCP services.
Eleven providers behind one interface, plus any OpenAI-compatible endpoint. The dispatcher routes each task to the best model automatically.
Cron jobs and one-shot tasks with skill binding. Daemon fires them, hot-reloads on change, auto-disables on failure.
Context window, semantic vector search, full-text SQLite archive. Tool failures and their fixes persist across sessions.
Every command and script runs inside an OS-native sandbox — bubblewrap on Linux, sandbox-exec on macOS.
Loadable markdown instruction packs with YAML frontmatter. Slash-command activation, natural language trigger, or cron-bound.
When a tool fails, the agent rewrites it, sandbox-tests it, and retries — the fix and whether it worked carry into later sessions. Every file the tools touch is snapshotted, so a version or a whole task can be restored.
The browser dashboard talks with you live through Gemini Live, hands real work to the chat agent, narrates its progress, and lets you cut in mid-sentence. Every request it hands over still lands in the chat transcript.
Optional KuraDB, registered as an MCP server for external document search. Keyword + semantic dual-track over your personal knowledge base.
When no tool fits a request, the agent builds one in real-time — finds an API, writes the script, tests it, and saves it for reuse. No code required.
User asks for live data. No matching tool found.
→Search public APIs, fetch docs, pick the best match.
→Generate script + schema. Run test_tool to verify.
→Execute the new tool. Auto-persisted for all agents.
One config line gives Claude Code, Codex, and any MCP agent your entire sandboxed tool library — and they can auto-build new tools that everyone instantly shares.
Any MCP-compatible agent connects via stdio and gets access to all tools — built-in, script, API, and extension.
Connect third-party MCP servers via stdio or HTTP/SSE. Tools auto-registered and available to the agent immediately.
Same agent, same tools, same memory — accessible from terminal, chat apps, HTTP, or other AI agents.
Interactive terminal with slash commands and session switching
OTP-authenticated bot with HTML output and voice input
Guild-verified bot with markdown and button confirms
OpenAI-compatible chat completions endpoint
Expose tools to Claude Code, Codex, and more
Eleven model providers behind one Agent.Send() interface, plus as many OpenAI-compatible endpoints as you want — Ollama, LM Studio, vLLM or self-hosted. Subscription routes — Claude Code, Codex, Copilot, xAI — are authentication paths, not extra providers. The dispatcher auto-routes each task to the best model.
Related actions sit behind one name and a mode argument instead of a dozen near-identical tools. 27 always register; pkg_manage is added on Linux and macOS, and four more once their credential or setting exists. A run carries only find_tools and run_tool; every other tool is listed by name, its schema fetched through find_tools and called through run_tool, so the tool block never changes mid-session and the prompt cache survives. Missing a tool? The agent builds it.
Locate, read, edit and roll back files. Every change is recorded, so one version — or an entire task — can be put back.
Discover what already exists, author new tools and skills, sandbox-test one before it goes live.
Web results and news headlines in one call, a page as markdown, or a raw HTTP request with multipart upload.
Run a binary under sandbox constraints, hand a file to the OS, fetch an asset, drive the Linux package manager outside the sandbox.
Delegate a subtask to its own session, queue timed and recurring runs, keep a live checklist, pause for an answer.
The session's own action log, tool failures kept across sessions with what fixed them, reasoning rules pulled in by topic.
Arithmetic and unit conversion, keychain-stored secrets. Speech synthesis, image generation and chat push register only once their credential or setting exists.
Auto-generate tools from natural language. Drop scripts, API descriptors, or connect an MCP server — KuraDB RAG arrives this way.
One command to install, one command to start. Add a provider and you're ready.
Single binary. macOS and Linux.
curl -fsSL https://agenvoy.com/scripts/install.sh | bash
TUI opens. Daemon auto-starts.
agen
In the TUI. Any of 11 providers; the key goes to your keychain.
/model
Name it. Persists across restarts.
/new