Answer: Use ClineCore when you need sessions, persistence, message history, built-in tools for files, shell, search, web fetch, hub/remote runtime, scheduling or event automation, or multi-agent teams. Use the Agent class instead for a browser-compatible or lightweight in-process agent, custom tools only with no built-ins, or full control over persistence and lifecycle. Status: Confirmed Entry: tool/cline/agents-and-automation/clinecore-vs-agent Revision: 1 Digest: sha256:cbb726c521358798 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:07:33Z Last changed: 2026-11-13T03:07:33Z Last verified: 2026-11-20T12:30:21Z Next check: 2026-11-21T12:30:21Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Sessions, persistence, message history | ClineCore | [1] | 2026-11-20 Built-in tools | ClineCore | [1] | 2026-11-20 Hub/remote runtime | ClineCore | [1] | 2026-11-20 Scheduling or event automation | ClineCore | [1] | 2026-11-20 Multi-agent teams | ClineCore | [1] | 2026-11-20 Browser-compatible or lightweight in-process agent | Agent | [1] | 2026-11-20 Custom tools only, no built-ins | Agent | [1] | 2026-11-20 Full control over persistence and lifecycle | Agent | [1] | 2026-11-20 Sources: [1] Cline. "ClineCore". https://docs.cline.bot/sdk/clinecore.md Role: primary. Accessed: 2026-11-20T12:30:21Z Quote: "| Sessions, persistence, message history | `ClineCore` |" (Supports: Sessions, persistence, message history) Quote: "| Built-in tools for files, shell, search, web fetch | `ClineCore` |" (Supports: Built-in tools) Quote: "| Hub/remote runtime | `ClineCore` |" (Supports: Hub/remote runtime) Quote: "| Scheduling or event automation | `ClineCore` |" (Supports: Scheduling or event automation) Quote: "| Multi-agent teams | `ClineCore` |" (Supports: Multi-agent teams) Quote: "| Browser-compatible or lightweight in-process agent | `Agent` |" (Supports: Browser-compatible or lightweight in-process agent) Quote: "| Custom tools only, no built-ins | `Agent` |" (Supports: Custom tools only, no built-ins) Quote: "| Full control over persistence and lifecycle | `Agent` |" (Supports: Full control over persistence and lifecycle) Published: 2026-11-20T00:16:31Z Snapshot SHA-256: f740b4a5ddcca087d35a91045f5ebc131b2d957a893dc55cc9db1d6fe3b9a2a9 (captured 2026-11-13T03:07:33Z) 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:33Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:30:21Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:30:21Z Last attempt: 2026-11-20T12:30:21Z Notes and limitations: Extracted automatically from a single official source (section "When to use which"). Related: https://latestn.com/tool/cline/agents-and-automation/create-cron-schedule How do I create a recurring schedule for a Cline agent using cron? https://latestn.com/tool/cline/agents-and-automation/create-custom-tool How do I create a custom tool with createTool in Cline? https://latestn.com/tool/cline/agents-and-automation/create-custom-tool-2 How do I create a custom tool in Cline with createTool? https://latestn.com/tool/cline/agents-and-automation/backend-modes What backend modes does ClineCore support? https://latestn.com/tool/cline/agents-and-automation/built-in-tools-list What built-in tools does Cline's ClineCore enable? https://latestn.com/tool/cline/agents-and-automation/bundle-skills-in-plugin How do I bundle skills into a Cline plugin? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:07:33Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/agents-and-automation/clinecore-vs-agent/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/clinecore-vs-agent POST: https://latestn.com/dispute/tool/cline/agents-and-automation/clinecore-vs-agent with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/agents-and-automation/clinecore-vs-agent?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). When should I use ClineCore instead of the Agent class in Cline? Revision 1, last verified 2026-11-20T12:30:21Z. https://latestn.com/tool/cline/agents-and-automation/clinecore-vs-agent (accessed 2026-11-21T10:08:18Z). @misc{LatestN_tool_cline_agents_and_automation_clinecore_vs_agent_r1, title = {When should I use ClineCore instead of the Agent class in Cline?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/agents-and-automation/clinecore-vs-agent}}, note = {Revision 1; digest sha256:cbb726c521358798; last verified 2026-11-20T12:30:21Z; accessed 2026-11-21T10:08:18Z} } 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/clinecore-vs-agent