Always-On Business Operator
Long-running personal and business agents with memory, scheduling, messaging, remote control, and broad integration access.
Comparison held
No “best” claim yet.
This collection needs at least 2 eligible repositories with reviewed canonical results. Candidates remain visible for planning, but they are not ranked and no missing score is estimated.
| Candidate | Evidence | Functional fit | Required authority | Data sensitivity | Operator burden |
|---|---|---|---|---|---|
| Hermes AgentRepository ↗ | No reviewed result | corePopular general agent suited to control-boundary comparison. | Tools, memory, shell, and service credentials | Prompts, memory, files, and connected-service data | medium |
| NanobotRepository ↗ | No reviewed result | conditionalSmaller candidate for testing reduced-complexity boundaries. | Tools, local files, and configured services | Task content and service data | medium |
| OpenClawRepository ↗ | No reviewed result | coreFlagship high-complexity agent and stress-audit anchor. | Gateway, device, messaging, shell, and scheduled actions | Messages, memory, credentials, and business data | high |
Campaign rationale
Persistent agents concentrate credentials and authority, creating an urgent operator decision.
What this page does not claim
Membership, stars, forks, discussion volume, and functional fit do not change a repository’s static score or assurance level.
Workflow boundary
A complete stack earns no workflow label until its exact components, permissions, prompts, tools, environment, and scenarios have been assessed together.