> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcore.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent

> The orchestrator — triggers, memory, tools, and execution

## What is the Agent?

The Agent is CORE's brain. It sits between you and everything CORE knows and can do: memory, toolkit, connected apps, and the gateway. When you send a message or a trigger fires, it figures out what's needed, pulls the right context, takes the right actions, and responds. Every conversation gets ingested back into memory, so CORE gets sharper the more you use it.

You can reach it via voice, scratchpad, WhatsApp, Slack, the web dashboard, or through any MCP-compatible agent like Claude Code or Cursor. Same brain, same memory, regardless of where you start.

***

## How It Works

Two paths into CORE — messages from you, and triggers that fire automatically. Both converge on the same intelligence.

```mermaid theme={null}
flowchart TD
    MSG["💬 Your message\nWhatsApp · Slack · Email · Web · API"]
    TRG["⏰ Automated trigger\nReminder · Webhook · Scheduled job"]

    CASE["① CASE — Decision Agent\nAnalyses trigger · builds ActionPlan\nwhat to do · tone · whether to message"]

    AGENT["② Agent\nReads ActionPlan · loads Persona\ndecides which tools to call"]

    subgraph orch["Orchestrator — routes & coordinates all tool calls"]
        MEMR["③ memory_explorer\nSearch knowledge graph for\nrelevant context · past decisions · relationships"]
        TOOLS["④ Toolkit\nExecute the specific actions\nsearch_emails · get_calendar · create_issue · …"]
        GW["④ Gateways  (if needed)\nClaude Code · Browser · Custom agents"]
    end

    MEM[("🧠 Memory\nKnowledge Graph")]

    SYNTH["⑤ Agent synthesizes\nCombines memory context + tool results"]
    RESP["Response delivered\nvia your preferred channel"]

    INGEST["⑥ memory_ingest\nSummarised conversation stored\nback to knowledge graph"]

    MSG --> AGENT
    TRG --> CASE
    CASE -->|"ActionPlan"| AGENT

    AGENT --> orch
    MEMR <-->|"read"| MEM

    orch --> SYNTH
    SYNTH --> RESP
    SYNTH --> INGEST
    INGEST -->|"write"| MEM
```

### Step by step

When you send a message, here's what happens:

<Steps>
  <Step title="Load Context">
    The agent loads your conversation history and persona document - a living summary of your preferences, directives, expertise, and decisions generated from your memory.
  </Step>

  <Step title="Understand Intent">
    It analyzes your message and decides what's needed: information from memory, live data from apps, web search, or an action to execute.
  </Step>

  <Step title="Gather or Act">
    The agent has two core tools:

    * **gather\_context** (READ) — routes to 3 specialized explorers:
      * *Memory Explorer* — searches your knowledge graph for past conversations, decisions, preferences
      * *Integration Explorer* — queries live data from connected apps (emails, calendar, issues)
      * *Web Explorer* — searches the web for real-time information

    * **take\_action** (WRITE) — executes actions in your connected apps via the Integration Explorer
  </Step>

  <Step title="Respond and Remember">
    The agent synthesizes results into a response. After responding, the conversation is automatically ingested into your memory graph - building context for future interactions.
  </Step>
</Steps>

***

## It Can Spawn Other Agents

The Agent isn't limited to its own capabilities. It can spin up other agents on your behalf — a Claude Code or Codex session to write code, a browser session to research something — all triggered from whatever channel you're on.

You're outside, a production bug comes in. You message CORE on WhatsApp: "Fix the auth timeout issue in the API." CORE spins up a Claude Code session via the gateway, pulls the relevant context from memory, and starts working on the fix — while you're still on your phone.

***

## Reminders and Scheduled Actions

The agent can execute actions at scheduled times - one-time or recurring. This isn't just "send me a notification." The agent runs the full workflow: searches memory for your rules and preferences, gathers context from connected apps, and takes actions.

**Daily email triage:** Every morning at 10am, the agent wakes up, goes through your inbox, and handles emails based on your email management skills stored in memory - drafting responses, flagging priorities, archiving noise.

**Overnight monitoring:** You tell the agent to watch Sentry while you sleep. A critical error comes in at 3am. The agent evaluates it, spins up a Claude Code session to investigate and fix the issue, then sends you a summary when you wake up.

**Weekly lead research:** Every Monday, the agent researches LinkedIn for leads matching your ICP, compiles them into a Google Sheet with notes, and sends it to your sales channel on Slack - ready for your team's morning standup.

All of this from a single message on WhatsApp: "Every Monday at 9am, find 10 new leads matching our ICP on LinkedIn, add them to the Leads sheet, and share it on #sales in Slack."

***

## How to Access

<CardGroup cols={3}>
  <Card title="Web Dashboard" icon="browser" href="/access-core/channels/web-dashboard" />

  <Card title="WhatsApp" icon="whatsapp" href="/access-core/channels/whatsapp" />

  <Card title="All Channels" icon="grid" href="/access-core/overview">
    Email, Slack, Telegram, Discord, and more
  </Card>
</CardGroup>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Memory" icon="database" href="/memory/overview">
    How the knowledge graph stores and organizes your information
  </Card>

  <Card title="Toolkit" icon="wrench" href="/concepts/toolkit">
    How actions work across your connected apps
  </Card>
</CardGroup>