AutoTalon is a local-first personal agent for governed, memory-aware daily execution.
It is not just a prompt runner and not a hosted assistant. AutoTalon gives a
single operator a long-lived agent that can talk, use tools, remember work, run
schedules, enter through chat gateways, and leave behind traces you can inspect.
The primary interactive surface is talon tui; the CLI is the automation and
diagnostics surface; Feishu/Lark and local webhook gateways connect external
conversations to the same runtime.
- A long-lived operator agent:
talon tuibrings conversation, sessions, inbox, todos, memory review, approvals, and runtime status into one terminal surface for the same agent. - Governed tool use by default: shell, process, network, and file tools run through sandbox policy, approval rules, trace events, audit logs, and rollback artifacts.
- Memory that compounds: layered memory keeps profile, project, working, experience, and skill references available across tasks without hiding where recall came from.
- Provider freedom: configure OpenAI-compatible, Anthropic-compatible, Ollama, OpenRouter, GLM, Moonshot, Qwen, xAI, Gemini, MiniMax, iFLYTEK, mock, or custom compatible endpoints through one provider catalog.
- Multiple entry points, one runtime: use the same sessions and governance from TUI, CLI, Feishu/Lark, local webhooks, and MCP surfaces.
- Maintainer-grade diagnostics: replay, smoke fixtures, eval reports, beta readiness, release checks, and package dry-runs are built into the source checkout.
Requirements:
- Node.js
>=22.13.0 - A provider API key for real assistant runs
- Corepack only when running from source
Install the published package:
npm install -g auto-talon
talon init --yes
talon provider setup openai --api-key "$OPENAI_API_KEY"
talon provider test
talon tuiRun from source:
corepack pnpm install
corepack pnpm build
corepack pnpm dev init --yes
corepack pnpm dev provider setup openai --api-key "$OPENAI_API_KEY"
corepack pnpm dev provider test
corepack pnpm dev tuiDaily agent surface:
talon tui
talon opsScriptable terminal execution:
talon run "review the changed files"
talon continue --last
talon task list
talon trace <task_id> --summary
talon audit <task_id> --summaryProvider operations:
talon provider list
talon provider setup openai --api-key "$OPENAI_API_KEY"
talon provider use ollama
talon provider status
talon provider test
talon provider route "large coding task"External entry points:
talon gateway serve-webhook --port 7070
talon gateway serve-feishu --cwd .
talon gateway list-adaptersAutomation and continuity:
talon schedule create "Review my inbox and summarize blockers" --name "Daily inbox review" --every 1d
talon inbox list
talon commitments list
talon next list
talon memory review-queue list| Area | What is included |
|---|---|
| Agent experience | TUI chat, session browsing, transcript view, status line, approvals, memory, todos, and operational panels |
| CLI execution | run, continue, task/session inspection, trace/audit views, workspace map, rollback, doctor |
| Governance | Policy engine, sandbox scopes, approval prompts, persisted allow rules, audit log, rollback snapshots |
| Memory | Profile/project/working memory, experience refs, skill refs, recall explanation, review queue, snapshots |
| Scheduling | One-shot, interval, cron, natural-language timing, execution modes, run queue, inbox/origin/webhook delivery |
| Providers | Provider catalog, setup/use/promote, health checks, smoke tests, route diagnostics, usage statistics |
| Gateways | Local webhook and Feishu/Lark adapters sharing the same runtime, identity mapping, and session commands |
| MCP and skills | MCP client/server surfaces, skill registry, skill assets, drafts, promotion, enable/disable overrides |
| Diagnostics | Smoke suite, eval report, beta readiness, replay, release checklist, npm pack contents validation |
AutoTalon is designed for a local operator who wants an agent with real tool access and visible guardrails.
- Local state is stored under
.auto-talon/, including SQLite data, logs, artifacts, config, approval rules, and rollback snapshots. - High-risk tools can require explicit approval before execution. Approval decisions are fingerprinted and can be scoped through persisted rules.
- Shell and filesystem access are checked against sandbox policy and project boundaries before execution.
- Tool calls, provider events, approvals, policy decisions, file writes, and rollback artifacts are recorded for later inspection.
- Feishu/Lark and webhook inputs enter through gateway adapters, so they share the same runtime policy instead of bypassing the local governance layer.
Read SECURITY.md before exposing gateways or running AutoTalon against sensitive project directories.
- Node.js 20 is not supported. AutoTalon requires Node.js
>=22.13.0because runtime storage uses the built-innode:sqlitemodule. - AutoTalon is local-first and single-operator oriented. It is not a hosted SaaS, team control plane, or multi-tenant agent service.
- Real provider runs require user-supplied credentials. Mock and scripted smoke providers are for tests and diagnostics.
- v0.1.0 includes Feishu/Lark and local webhook gateway adapters. Slack, Telegram, Discord, voice, browser automation, image generation, and companion mobile/desktop apps are outside this release.
talon release check,talon eval run, andtalon smoke runare maintainer diagnostics for source checkouts. Installed-package users should start withtalon doctorandtalon provider test.
| Goal | Start here |
|---|---|
| Install and first run | Install, Quickstart |
| Learn CLI/TUI commands | Commands |
| Configure providers and runtime | Config reference, Provider troubleshooting |
| Understand approvals and sandboxing | Approvals, Sandbox troubleshooting |
| Connect external entry points | Gateway, Gateway troubleshooting |
| Use memory and skills | Skills, Memory troubleshooting |
| Integrate MCP | MCP |
| Validate a release | Replay and eval, Compatibility matrix |
| Develop AutoTalon | Architecture, Module boundaries, Testing |
Run these checks before tagging or publishing v0.1.0:
corepack pnpm check
npm run release:check
npm pack --dry-run --jsonAfter installing or updating a local project:
talon doctor
talon provider testThe release checklist covers lint, tests, build, smoke/eval threshold, beta readiness, schema baseline, Node version policy, npm metadata, lockfile policy, setup scripts, and package contents.
MIT. See LICENSE.