What it does
6 features
Timon · Agent workspace with orchestration
Product and access
Timon is classified as a standalone product with its standard access.
Core features
6 features from provider sources · checked on 6 November 2026. Availability and limits are listed directly below.
Roles in an agent team
Orchestrator, coder, reviewer and further roles distribute work among separately configured agents.
Source 2Code, review and merge
Tasks run through a Kanban board and separate Git worktrees; different models can write and review.
Source 1Memory with scope
Rules apply globally or by project, role or agent and are injected at startup as appropriate.
Source 5Background routines
A service holds working state. Schedules, webhooks and workflows enable recurring assignments.
Source 1Browser and multiple chats
An integrated browser and side-by-side conversations support the agents’ work.
Source 2Models and fallbacks
Existing CLI access and additional compatible endpoints can be combined; fallbacks respond to quota limits.
Source 4
Usable AI models
Open choice
Timon combines existing agent CLIs and supports additional Anthropic- or OpenAI-Responses-compatible endpoints, including personal keys, local servers and LiteLLM. Models and fallbacks are configurable; protocol support and quotas depend on the backend. The technical documentation qualifies the README’s blanket subscription framing.
Model families named
- Anthropic (Claude)
- OpenAI (GPT)
- xAI (Grok)
- DeepSeek
- Moonshot (Kimi)
- Other models can be connected freely
- Model choice
- Automatic or your choice
- Your own API key
- Yes
- Router or custom endpoint
- Yes
- Local models
- Yes
- Depends on
- Plan, Admin approval
The rating covers the generally available main access. Documented · Sources accessed on
Does it fit my task?
2 practical tasks · 4 requirements and limits
A good fit if …
- you want to coordinate several existing coding agents
- you want to manage roles, memory and tasks on your own host
- you want to assign coding and review to different models
Less suitable if …
- you want a fully managed service without operating your own host
- you expect fully automatic recovery after every failure
Editorial assessment based on provider documentation. Not a product test.
Practical tasks
Editorial examples based on documented features. No product tests performed.
Implement a scoped development goal
- Your input
- Repository, acceptance criteria and permissions for the participating roles.
- Possible result
- Decomposed tasks with changes and a separate review.
- What to check
- Check tests, diffs and consent before pushing or publishing.
Recurring project maintenance
- Your input
- A clear inspection task, schedule and scoped access.
- Possible result
- Repeatable runs with findings and updated working rules.
- What to check
- Review new rules for accuracy and appropriate scope.
Implement a scoped development goal
Your possible prompt
Read the project rules. Investigate [error], propose a small change, and run the relevant checks. Show me the diff and any remaining uncertainties.
Adjust the task, data and permissions.
Requirements and limits
Requirement
Provide host and backends
The background service requires a running computer or server and available agent access.
Source 10Limitation
Check continuation after restart
A conversation turn interrupted by a restart is not automatically replayed. Check prior actions, then continue with a message.
Source 4Not yet confirmed
Plan scope is still changing
The website and repository differ on plugin and plan details. Pro and Cloud prices are not yet specified on the pricing page.
Source 8Limitation
Network logging is observation
Optional connection logging records only traffic passing through its proxy and blocks no connections.
Source 11
Can I use it?
With requirements
Europe & regional availability
Local operation and external model processing are assessed separately.
Reviewed scope: Your own Timon host and chosen model providers
Reviewed on:
With requirements
Determine data region through the backend
Timon can run on your computer or server. The host location does not determine processing by connected model providers; check their country access and data region separately.
Region, reason and source
Region covered: EU/EEA, United Kingdom and Switzerland
Documented reason: Custom compatible endpoints are supported; the selected provider determines external processing.
Official source · docs.timon-ai.com · Official source · docs.timon-ai.com
Accounts & permissions
Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use.
Configuration covered: Timon account, backend access and agent permissions
Sources reviewed:
Show all 3 points
Documented
Admin approval
Agents have approval modes and allowed or blocked tools. Orchestration permissions determine who may assign work to whom.
EvidenceDocumented
Data access & team sharing
Keys can be scoped to a backend and specific projects or agents. The chosen CLI access imposes further boundaries.
Evidence
Memory and conversation continuity
6 of 6 criteria documented
Local memories with four scopes, visible rules and backend-dependent conversation continuation.
Agent and project memory, rules and mission history
Sources accessed:
Documentation by criterion
StorageDocumented
Storage and scope
Timon keeps agent and project files plus rules and extracted facts in a local database. The service manages working state.
SelectionDocumented
Selection and timing
Facts are captured after completed or failed missions. A nightly curation pass condenses them into rules; rules can also be added explicitly.
Edit & deleteDocumented
Inspect, edit and delete
Files and rules can be edited or deleted. Deleted agents remain in trash for 30 days by default; project facts and backups are managed separately. Rule deletions leave audit entries.
Access boundariesDocumented
Agent and channel boundaries
Rules apply globally, to a project, to a role or to an agent. A duplicated agent starts with empty memory.
RetrievalDocumented
Retrieval
Startup injects a digest, applicable rules and recent pitfalls. Memory search combines full-text search for rules and text search for facts.
New conversationsDocumented
Session reset and compaction
Compaction uses the same conversation or a new one with a summary, depending on the backend. After a service restart, an interrupted turn remains for inspection; a new message continues it where supported by the backend.
Cost and effort
1 plan · Prices as of 6 November 2026
Prices and included usage
Pricing checked
The Free plan is intended for one person on one machine. Model access and hosting are supplied separately.
| Plan | Price | Included |
|---|---|---|
| Free | USD 0 for Timon | Agents, Kanban, memory, routines and browser according to the pricing page. |
- Pro and Cloud are announced; specific prices are pending. The listed Cloud plan runs on a server of your choice.
- The repository and website differ on plugin scope. Check current license and plan terms before procurement.
Setup
Install Timon, sign in to an agent CLI and configure models, working folders and approvals for each role.
Operation & oversight
Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.
Deployment covered: Your own Timon service with external agent backends
Sources reviewed:
Editorial assessment
Editorial assessment: suitable for supervised agent teams with clear assignments; runtime, approvals and actual recovery should be tested in your own workflow.
Show all 6 points
Documented
Files and working state
The service holds local state; backups and trash have their own retention rules.
EvidenceDocumented with conditions
Sign-ins
CLI sign-ins and additional provider keys must remain valid.
EvidenceDocumented
Starting further runs
Schedules and webhooks can start new tasks on the running host.
EvidenceDocumented with conditions
Human intervention
Approval mode and tool rules determine when a question is required.
EvidenceDocumented
Detecting errors
The mission view and conversation history show interrupted steps and errors.
EvidenceDocumented with conditions
Resuming after failures
Conversation turns after service restarts require a new message; quota failures in Kanban tasks have separate retry rules.
Evidence
Evidence and open questions
15 sources · 1 open point
Open points
The reviewed sources contain no reliable information on these points. A gap says nothing about the product.
Requirements and limits: not yet confirmed
Sources and evidence
Official product documentation reviewed. Workflows and assessments are editorial; hands-on product tests are outside the scope of this directory.
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
Provider
Timon is developed by PUBLIKO in France. The code is published under AGPL-3.0; the SDK and plugin templates have separate license terms.
- Operator
- PUBLIKO
- Organization
- Software provider
- Website
- timon-ai.com
- Repository
- ai-timon/timon
- GitHub stars
- 50 · Reviewed
- License
- AGPL-3.0
Changes to this profile 1
Dedicated profile with orchestration, local memory, open model access and documented operating boundaries.
These notes describe editorial changes. Source and pricing review dates appear in their respective sections.