{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/agent-harnesses.always-on-assistant/",
    "json": "https://www.anchorterminal.com/niches/agent-harnesses.always-on-assistant/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/agent-harnesses.always-on-assistant/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/agent-harnesses.always-on-assistant/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 2 | 10 | 101 | 8 | 4 |\n\n## What counts as done\n\nThe agent answers in the channel only to allowed senders, runs its scheduled tasks without supervision, and every tool call is logged where the owner can read it.\n\nMeasured, for our own tests: the scheduled tasks run unsupervised for a week.\n\nHow agents ask for it: message my agent on Telegram and have it do things on my server; send me a morning digest; watch my notes and act on them; give the agent its own machine\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Letta (Letta)**: `letta server --backend local --channels telegram` serves a bot with `pairing`, `allowlist` or `open` DM policy, `letta cron` runs schedules, and the server example binds to loopback.\n- **Vibe-Trading (HKUDS)**: `vibe-trading serve` runs Telegram and other channels with `allow_from` senders, pairing codes and an operator gate (star \u003e allowlist \u003e pairing \u003e deny), scheduled runs deliver to channels, and an audit ledger records live actions.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Agent Zero (Agent Zero, s.r.o.)**: Telegram, WhatsApp and email with allowed_users lists, a task scheduler, Tool Access policies and chat logs cover the job, but an empty allow list accepts everyone, the UI has no login until set, and Infection Check ships off.\n- **Clawboo (Sanreds)**: A self-hosted server with routines, an access token and an audit log, reached through its own web app rather than Telegram or Slack; connectors reach outward through Composio, and no allowed-sender list exists.\n- **Cline (Cline Bot Inc.)**: cline connect telegram, slack, discord, gchat, whatsapp or linear maps threads to sessions with access control, and cline schedule adds cron jobs, but the hub must stay on 127.0.0.1 or carry a room secret, and sessions run yolo.\n- **dsh-superagent (DeepSeek) (DeepSeek (the LICENSE names the DeepSeek Harness Team; DeepSeek Harness's terms name Hangzhou DeepSeek Artificial Intelligence Co., Ltd.))**: A main Session listens to GitHub and Feishu, the host enforces allowed lists and records Decisions, and a panel shows what needs a person, but Executors run with danger-full-access as the operator and there is no scheduler.\n- **goose (Agentic AI Foundation (Linux Foundation))**: A gateway for chat platforms such as Telegram exists with GOOSE_GATEWAY_MAX_TURNS and a scheduler, but allowed-sender control and tool-call logging were not found in the pages read.\n- **OpenMausBot (Supamaus Software Private Limited)**: Bots, routines, webhooks, approval cards and per-thread NDJSON logs cover the job, but the channel is MausBot's own app rather than Telegram, and access is by pairing token rather than a sender list.\n- **Paperclip (Paperclip Labs, Inc.)**: Experimental Agent Chat with Slack, Discord, Telegram and AgentMail connectors, routines, approvals and an activity log exist, but the default `local_trusted` mode treats every request as the board admin and telemetry is on until opted out.\n- **Unstoppable (Unstoppable Domains, Inc.)**: Scheduled workflows and Remote Control from a phone exist, but the agent answers in the app, not a chat channel, and the desktop must stay on.\n- **Verdent (Verdent AI, Inc.)**: Telegram, Slack and Feishu bots pair to Manager and `/schedule` runs tasks, but only while the desktop app is active and with no sender allowlist beyond pairing.\n- **Warp (Warp Agent CLI and the Oz Agent API) (Denver Technologies, Inc. (d/b/a Warp))**: Factories take work from Slack, Linear, GitHub and schedules and reply in the thread, but on Warp's infrastructure rather than your machine.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Qoder CLI (BRIGHT ZENITH PRIVATE LIMITED)**: docs.qoder.com answered 502 from the fetch proxy on three attempts and a DNS failure through WebFetch, so no page was read.\n- **Qwen Code (Qwen team, Alibaba Group (no legal entity is named in the repository or the docs))**: The docs list WeChat and Scheduled Tasks pages that were not read; the headless and approval pages describe no channel.\n\n- not this job: Aider (Aider AI LLC): No chat channel or scheduler.\n- not this job: Amp (Amp Frontier Corporation): No chat channel, scheduler or allowed-sender list is documented; Amp is a coding agent with a CLI, apps and orbs.\n- not this job: Antigravity CLI (Google LLC): No chat channel, scheduler or allowed-sender list; agy is a terminal and headless coding agent.\n- not this job: Auggie CLI (Augment Computing, Inc.): No chat channel or scheduler; automation means CI pipelines and GitHub Actions.\n- not this job: AXLR (Underpass AI): No chat channel or scheduler is built in; a bot must call --exec or the service itself.\n- not this job: Claude Code (Anthropic, PBC): Channels are a research preview that -p ignores, scheduled work runs as cloud routines, desktop tasks or a session-bound /loop; no chat channel with an allowed-sender list or week-long headless daemon is documented.\n- not this job: CLI Manager (solhun (Jeong Kyeonghun)): No chat channel or scheduler, and the app must be open.\n- not this job: Conductor (Conductor): No chat channel; the Mac app and the closing cloud are the only surfaces.\n- not this job: Crush (Charmbracelet, Inc.): No chat channel or scheduler.\n- not this job: Cursor CLI (Anysphere, Inc.): No chat channel or scheduler in the CLI.\n- not this job: DeepSeek Harness (dsh) (DeepSeek (the LICENSE names DeepSeek, and no legal entity is named in the repository or the docs)): No chat channel or scheduler in dsh itself.\n- not this job: Devin (Cognition AI, Inc.): A hosted coding agent for repositories, not a general assistant on the owner's machine; the Slack integration was not read.\n- not this job: Droid CLI (The San Francisco AI Factory, Inc.): No chat channel or scheduler; Missions orchestrate coding work.\n- not this job: Pi (Earendil Inc.): No chat channel or scheduler.\n- not this job: Emdash (General Action, Inc.): No chat channel; a desktop app.\n- not this job: Gemini CLI (Google LLC): No chat channel or scheduler.\n- not this job: GitHub Copilot CLI (GitHub, Inc.): No chat channel or scheduler for an always-on agent.\n- not this job: Harness (Autonomous, Inc.): No chat channel or scheduler.\n- not this job: Harness² (Google LLC): Not an assistant.\n- not this job: HarnessRouter (Lumentree Corporation): No chat channel or scheduler; a task API.\n- not this job: Jules (Google LLC): Not an assistant, and read-only since 11 November 2026.\n- not this job: Junie CLI (JetBrains s.r.o.): No chat channel or scheduler.\n- not this job: Kilo Code CLI (Kilo Code Inc. (the terms are a contract with Anaconda, Inc. on behalf of itself and its affiliates, including Kilo Code Inc.)): No chat channel or scheduler.\n- not this job: Kimi Code CLI (Moonshot AI (the global Kimi terms name NOVASCENT PRIVATE LIMITED, Singapore)): No chat channel or scheduler is documented; the REST and WebSocket server is a local session API, not a messaging gateway.\n- not this job: Kiro CLI (Amazon Web Services, Inc.): The CLI has no chat channel or scheduler; Kiro Crew and Bots are separate surfaces not covered by this listing.\n- not this job: mini-swe-agent (No legal entity named. The MIT licence names Kilian A. Lieret and Carlos E. Jimenez): No chat channel or scheduler; it is a one-tool coding agent.\n- not this job: MiniMax Code (Nanonoble Pte. Ltd.): The CLI has no chat channel or scheduler; messaging integrations belong to the MiniMax Agent app, not `mcode`.\n- not this job: Mistral Vibe CLI (Mistral AI (RCS Paris 952 418 325)): No chat channel or scheduler in the CLI docs.\n- not this job: Muse Code (Meta Platforms, Inc.): No chat channel or scheduler is documented.\n- not this job: OpenAI Agents API (OpenAI OpCo, LLC): No chat channel or scheduler; it is a session API.\n- not this job: OpenAI Codex (OpenAI OpCo, LLC): No chat channel or scheduler in the CLI; Codex Cloud tasks start from ChatGPT surfaces.\n- not this job: OpenCode (Anomaly Innovations, Inc.): No chat channel or scheduler; `opencode serve` is a session API.\n- not this job: OpenHands (All Hands AI): No Telegram or Slack channel serving is documented; Slack appears only as an MCP target for automations.\n- not this job: Orca (Lovecast Inc.): No chat channel is documented; automations schedule prompts on repositories.\n- not this job: Parallax (Conifer Solutions, Inc.): No chat channel or scheduled tasks.\n- not this job: Paseo (Mohamed Boudra): Mobile and web clients talk to your daemon; there is no Telegram or Slack channel.\n- not this job: Prime Agent (Prime Intellect, Inc.): Slack is an MCP connector for tools, not a channel the agent answers in.\n- not this job: Mirror CLI (Reflection AI): No chat channel or scheduler.\n- not this job: Rovo Dev CLI (Atlassian Pty Ltd): No chat channel or scheduler in the CLI.\n- not this job: Sculptor (Imbue, Inc.): No chat channel or schedules.\n- not this job: T3 Code (T3 Tools Inc.): No chat channel or schedules; phone access is to your own server.\n- not this job: Traycer (Traycer AI): No chat channel or schedules; the mobile app follows your own tasks.\n\n## What stops agents finishing\n\n- gateway listens on all interfaces with no auth by default (acc-30, acc-31)\n- cron jobs stop for two weeks unnoticed (acc-30)\n- a vague instruction deletes host files (acc-30)\n- the agent edits its own config, claims success and breaks startup (acc-29)\n- marketplace skills carrying malware (acc-30)\n\n## Around it\n\nBefore: messaging.receive. After: messaging.send, home-automation.control.\n\n## Where this comes from\n\nWeight 8 of 100 in Agent harnesses: 4 of 33 accounts (acc-11, acc-29, acc-30, acc-31) all on OpenClaw, which is not a listing; Agent Zero and Letta are the listed equivalents\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/agent-harnesses.always-on-assistant.json, or the MCP tool get_use_case with id agent-harnesses.always-on-assistant. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Run an always-on general agent reachable from chat with scheduled tasks",
        "url": ""
      }
    ],
    "description": "Run an always-on general agent reachable from chat with scheduled tasks: 2 companies fully do it, 10 with a limit, 101 carry the tag. Every listing in Agent harnesses with the reason and a source.",
    "facts": null,
    "h1": "Run an always-on general agent reachable from chat with scheduled tasks",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/agent-harnesses.always-on-assistant/",
    "published": "",
    "section": "agents",
    "title": "Run an always-on general agent reachable from chat with scheduled…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/agent-harnesses.always-on-assistant/"
  },
  "tokens": {
    "markdown": 2750,
    "slim": 380
  },
  "version": 1
}
