Desktop · local-first · MIT

TonWorker

Ask for finished work — a brief, a report, a calendar block — not another chat thread.

The desktop you actually get

Sidebar sessions, inbox approvals, plan steps, and deliverable files — same structure as the app.

TonWorker

What should we produce?

Summarize this week's GitHub activity and draft a status note for my team.
Plan
  1. Fetch commits & PRs from GitHub
  2. Draft markdown summary
  3. Propose calendar hold for review
Run a command
gh api repos/…/commits --paginate
Allow once Deny
Message TonWorker…

Built for everyday work

Personas

Coworker, Chat, and Code surfaces — each with its own sessions, tools, and workspace rules.

Inbox

Approvals, questions, and unattended prompts land in one queue. Resolve without losing session context.

Scheduled

Morning briefs, weekly reports, standing watches — cron-style automations with full run transcripts.

Connectors & MCP

GitHub, Slack, Notion, HubSpot, Gmail, Calendar, terminal, files — plus any MCP server you wire in.

Artifacts

Deliverables show up as real files — preview markdown, PDF, sheets, and code in the right rail.

Bring your model

OpenAI, Anthropic, Gemini, DeepSeek, Kimi, Ollama, and more — switch per task, keys stay local.

Download

macOS, Windows, and Linux builds from GitHub Releases.

https://github.com/toninfo/tonworker/releases/latest/download/TonWorker-macos-arm64.dmg

Download

Your data stays local

Conversations, connector tokens, and model keys run and stay on your machine. Work context does not need to pass through a third-party cloud — less exposure, lower leak risk.