Answer: In Cline's hub-spoke architecture, the hub is a singleton daemon per machine that coordinates sessions, routes events and approvals, manages schedules, and brokers capabilities between clients without running the agent loop; the spoke is a worker process running `@cline/core` that executes the agent loop, calls tools, and streams output, reporting events back to the hub and owned by the daemon; the client is a CLI, VS Code, JetBrains, or custom app that discovers the hub, registers over WebSocket, attaches to sessions, sends user input, and receives streamed events. Status: Confirmed Entry: tool/cline/agents-and-automation/hub-spoke-roles Revision: 1 Digest: sha256:b5be389f1f9c452e (changes whenever the content changes) Timeline: Created: 2026-11-13T03:07:30Z Last changed: 2026-11-13T03:07:30Z Last verified: 2026-11-20T12:30:15Z Next check: 2026-11-21T12:30:15Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of hub role | Singleton daemon per machine | [1] | 2026-11-20 spoke role | Worker process running `@cline/core` | [1] | 2026-11-20 client role | CLI, VS Code, JetBrains, or any custom app | [1] | 2026-11-20 governing rule | clients participate, spokes execute, the hub coordinates | [1] | 2026-11-20 Sources: [1] Cline. "Hub-Spoke Architecture". https://docs.cline.bot/sdk/architecture/hub-spoke.md Role: primary. Accessed: 2026-11-20T12:30:15Z Quote: "Singleton daemon per machine. Coordinates sessions, routes events and approvals, manages schedules, brokers capabilities between clients. Does not run the agent loop." (Supports: hub role) Quote: "Worker process running `@cline/core`. Executes the agent loop, calls tools, streams output. Reports events back to the hub. Owned by the daemon, not by any client." (Supports: spoke role) Quote: "CLI, VS Code, JetBrains, or any custom app. Discovers the hub, registers over WebSocket, attaches to sessions, sends user input, receives streamed events." (Supports: client role) Quote: "clients participate, spokes execute, the hub coordinates" (Supports: governing rule) Published: 2026-11-20T00:16:31Z Snapshot SHA-256: 80417c34e4f74db1ca3fe22d948ed90566a6749590a5d0c575036011d9ab4cd7 (captured 2026-11-13T03:07:30Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:07:30Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:30:15Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:30:15Z Last attempt: 2026-11-20T12:30:15Z Notes and limitations: Extracted automatically from a single official source (section "Three Roles"). Related: https://latestn.com/tool/cline/agents-and-automation/link-tasks-dependency-chain How do I link tasks together in Cline Kanban so the next task starts automatically? https://latestn.com/tool/cline/agents-and-automation/manage-schedules How do I manage, pause, or delete existing Cline schedules? https://latestn.com/tool/cline/agents-and-automation/parallel-agents-worktrees How does Cline Kanban run multiple agents in parallel without conflicts? https://latestn.com/tool/cline/agents-and-automation/event-streaming How do I stream events from a Cline SDK agent run? https://latestn.com/tool/cline/agents-and-automation/handle-tool-errors How do I handle tool errors in Cline agents so the agent can recover? https://latestn.com/tool/cline/agents-and-automation/how-github-actions-integration-works How does the Cline GitHub Actions integration work under the hood? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:07:30Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/agents-and-automation/hub-spoke-roles/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cline/agents-and-automation/hub-spoke-roles POST: https://latestn.com/dispute/tool/cline/agents-and-automation/hub-spoke-roles with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/agents-and-automation/hub-spoke-roles?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the hub, spoke, and client roles in Cline's hub-spoke architecture? Revision 1, last verified 2026-11-20T12:30:15Z. https://latestn.com/tool/cline/agents-and-automation/hub-spoke-roles (accessed 2026-11-21T10:05:31Z). @misc{LatestN_tool_cline_agents_and_automation_hub_spoke_roles_r1, title = {What are the hub, spoke, and client roles in Cline's hub-spoke architecture?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/agents-and-automation/hub-spoke-roles}}, note = {Revision 1; digest sha256:b5be389f1f9c452e; last verified 2026-11-20T12:30:15Z; accessed 2026-11-21T10:05:31Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cline/agents-and-automation/hub-spoke-roles