sanil-23andClaude Opus 4.6
d1c577d25a
Completes the half-built migration from a hardcoded ARCHETYPE_TOOLS table
+ orphan skill_delegation.rs to a TOML-driven delegation surface where
each agent declares its subagents and the tool list is synthesised from
the registry at agent-build time.
Rewrites `collect_orchestrator_tools` to take the orchestrator's
AgentDefinition, the global AgentDefinitionRegistry, and the slice of
connected Composio integrations, then iterates the definition's
`subagents` field:
* `SubagentEntry::AgentId` → one ArchetypeDelegationTool. The tool's
`name()` comes from the target agent's `delegate_name` override (or
`delegate_{id}` fallback) and its `description()` is the target's
`when_to_use`. Editing an agent's TOML when_to_use now immediately
updates the tool schema the orchestrator LLM sees — zero drift, no
hardcoded description strings to keep in sync.
* `SubagentEntry::Skills { skills = "*" }` → one SkillDelegationTool
per connected Composio toolkit. Each routes to the generic
skills_agent with `skill_filter` pre-populated. Empty integrations
list (CLI path, or user not yet connected) produces zero tools
rather than phantom `delegate_*` entries for unconnected toolkits.
Also in this commit:
- Wire the orphan `skill_delegation.rs` into `impl/agent/mod.rs` via
`mod skill_delegation;` + `pub use SkillDelegationTool;`. The file has
existed since earlier work but was never declared in the module tree,
so it compiled as dead code.
- Delete the legacy `MAIN_AGENT_TOOL_ALLOWLIST` constant and the
`main_agent_tools` filter in `tools/ops.rs`. They were documented as
"no longer the primary source of truth" since the from_config builder
switched to `collect_orchestrator_tools`, and grep confirms no
external callers remain. Clean deletion.
- Delete the hardcoded `ARCHETYPE_TOOLS` const in
`tools/impl/agent/mod.rs`. The 4-entry table has been replaced by the
orchestrator TOML's `subagents` list (which covers those 4 plus
archivist plus the skills wildcard), and the re-export in
`tools/mod.rs` is removed accordingly.
- Update `agents/orchestrator/agent.toml`: add the `subagents` field
listing researcher / planner / code_executor / critic / archivist /
{ skills = "*" }. Keep `spawn_subagent` in `[tools] named` as an
advanced fallback so power users can still spawn custom workspace-
override agent ids that aren't in the declarative subagents list.
- Add `delegate_name = "..."` to the 5 archetype TOMLs so the
orchestrator LLM sees natural tool names (`research`, `plan`,
`run_code`, `review_code`, `archive_session`) rather than the
`delegate_<agent_id>` fallback.
- Update `agent/harness/session/builder.rs` (line ~461) to call the new
`collect_orchestrator_tools` signature. Looks up the orchestrator
definition from the global registry; passes an empty integrations
slice because the builder is synchronous and cannot await Composio's
async fetch. The channel-dispatch path will populate integrations in
a later commit — the CLI/REPL path ships without per-toolkit delegation
tools, which is acceptable regression since CLI users still reach
Composio via `composio_execute` and the retained `spawn_subagent`
fallback.
Tests:
* 5 new unit tests in `orchestrator_tools.rs` cover the baseline
AgentId + Skills wildcard expansion, empty-integrations edge case,
unknown-id graceful skip, non-delegating agent with empty subagents,
and the slug sanitiser for tool-name-safe Composio toolkit names.
* Runs clean alongside all existing agent-module tests (323 pass;
one pre-existing Windows-path failure in `self_healing::tests::
tool_maker_prompt_includes_command` is unrelated to this PR and
fails identically on the upstream baseline).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
OpenHuman
The age of super intelligence is here. OpenHuman is your Personal AI super intelligence. Private, Simple and extremely powerful.
Discord • Reddit • X/Twitter • Docs
"The Tet. What a brilliant machine" — Morgan Freeman as he reminisces about alien superintelligence in the movie Oblivion
Early Beta — Under active development. Expect rough edges.
To install or get started, either download from the website over at tinyhumans.ai/openhuman or run
# For MacOS/Linux
curl -fsSL https://raw.githubusercontent.com/tinyhumansai/openhuman/main/scripts/install.sh | bash
# For Windows
irm https://raw.githubusercontent.com/tinyhumansai/openhuman/main/scripts/install.ps1 | iex
What is OpenHuman?
OpenHuman is an open-source agentic assistant that is designed to integrate with you in your daily life. Here's what makes OpenHuman special:
-
Simple, UI-first — A clean desktop experience and short onboarding paths so you can go from install to a working agent in a few clicks, without a config-first setup. You don't need a terminal to run OpenHuman.
-
One subscription, many providers — You only need one account to get access to many agentic APIs (AI Models, Search, Webhooks/Tunnels and other 3rd party APIs etc..), simplifying the experience to get a powerful agent going.
-
Rich Skills — Plug into Gmail, Slack, Notion, and the rest of your stack via rich, feature-backed skills. Connections are typically one click through setup wizards instead of wiring APIs by hand. Workflow data is kept on device, encrypted locally, and treated as yours: encryption and sensitive context stay on your machine. Webhooks give instant feedback into the agent when external systems or skills emit events, so the loop stays tight without constant polling.
-
Local knowledge base — Built from your data and your activity. How you work across tools, sessions, and connected services—so the agent gets rich, workflow-aware context, not a one-off chat transcript. Everything is stored on your machine and compounding over time without becoming a cloud dossier. Channels, skills and ongoing conversations feed the same loop so day-to-day context does not reset every session.
-
Local AI model — The Rust core exposes local AI paths (and the desktop bundle can ship local/bundled runners where applicable) for the workloads above—vision snippets, speech helpers, summarization, tooling—so sensitive steps can stay off the cloud when you choose.
-
Deep desktop integrations — OpenHuman is a native desktop assistant, not a web-only chat: memory-aware keyboard autocomplete, voice (STT listening and TTS replies), screen intelligence that understands what is on screen and feeds your local context, plus windowing and OS-level permissions—so the agent meets you on the machine, not trapped in a browser tab.
Architecture: docs/ARCHITECTURE.md. Contributor orientation: CONTRIBUTING.md.
OpenHuman vs other agents
High-level comparison (products evolve—verify against each vendor). OpenHuman is built to minimize vendor sprawl, keep workflow knowledge on-device, and ship deep desktop features—not only chat.
| Claude Code/Cowork | OpenClaw | Hermes Agent | OpenHuman | |
|---|---|---|---|---|
| Open-source: Is the codebase open to review? | 🚫 Proprietary client | ✅ MIT License | ✅ MIT License | ✅ GNU License |
| Simple: Is it simple to get started? | ✅ Simple Desktop App + CLI | ⚠️ Terminal first and often complex | ⚠️ Terminal first and often complex | ✅ Simple, Clean UI/UX. Get started within minutes |
| Cost: How expensive is to run? | ⚠️ Subscription + add-on tool/API costs | ⚠️ Tied to models & hosting you choose | ⚠️ Tied to models & hosting you choose | ✅ Cost optimized with the option to run many things locally for free |
| Memory & Knowledge Base (KB): Does the agent know you and your world? | ✅ Built-in memory; mostly chat/session scoped | ⚠️ Has a local memory but often needs plugins for richer behavior | ✅ Self-learning / task loops (typical) | 🚀 Local KB + Self-learning from your activity & data (GMail, Notion etc... via skills) & prompts |
| API spagetti: How complex is it to hook mulitple features together? | 🚫 Claude bill + often extra keys for MCP/tools | 🚫 BYOK / multi-vendor common | 🚫 Multiple providers common | ✅ One account get access to many bundled platform APIs |
| Extensibility: Can you add rich features into it? | ✅ MCP (different model than sandboxed skills) | ✅ Plugin Architecture (SKILL.md) | ✅ Plugin Architecture (SKILL.md) | 🚀 Rich Skills with ability to have realtime updates, local DB & more |
| Desktop integrations: Can it integrate into your desktop completely? | ⚠️ Desktop app & access to folders | ⚠️ Often lighter native surface | ⚠️ Often lighter native surface | ✅ STT, TTS, screen intelligence, memory-aware autocomplete and a whole lot more |
Contributors Hall of Fame
Show some love and end up in the hall of fame