Kent

Your personal AI agent that runs on your Mac. Kent syncs your data — iMessage, Gmail, GitHub, Chrome, Granola, Apple Notes — indexes it locally, and runs scheduled workflows powered by Claude.

Ask it what to focus on today. Get a daily brief of your meetings, emails, and PRs. Let it draft follow-ups from meetings. All your data stays on your machine.

Install

# requires macOS and Bun (https://bun.sh)
bun install -g meet-kent
kent init

kent init walks you through connecting sources, adding your API keys, runs your first sync, starts the daemon, and opens the web dashboard.

Quick start

kent init                     # setup wizard — connect sources, add API keys
kent run                      # start daemon + web dashboard (persistent)

After kent run, the daemon and web dashboard run as macOS system services. They'll stay running through sleep, reboot, and terminal closes. Check on them anytime:

kent status                   # check if everything is running
kent logs -f                  # stream daemon logs

What it does

Syncs your data from local and cloud sources every few minutes. Everything is stored in a local SQLite database at ~/.kent/kent.db.

Answers questions with your context. The agent has tools to search across all your synced data, so it can answer things like "what did Sarah say about the launch?" or "summarize my unread GitHub notifications."

Runs workflows on a schedule. Workflows are prompts that run on a cron schedule. Kent ships with defaults (morning briefing, evening recap, memory curator) and you can create your own from the CLI or web dashboard.

Remembers things. The agent maintains a persistent knowledge base — people, projects, preferences, events — that it references across conversations.

Runs as a system service. The daemon and web dashboard run as macOS launchd services that auto-restart on sleep, reboot, or crash. Once started, Kent is always on.

Architecture

┌──────────────────────────────────────────┐
│  CLI / Web Dashboard                     │
├──────────────────────────────────────────┤
│  Daemon (launchd service)                │
│  ├─ Sync loop → sources every N min      │
│  ├─ Cron loop → run due workflows        │
│  └─ Backfill  → catch up missed runs     │
├──────────────────────────────────────────┤
│  Agent (subprocess per run)              │
│  ├─ LLM (Anthropic, OpenAI, Google, …)  │
│  └─ Tools: data, memory, workflow,       │
│     filesystem, skills                   │
├──────────────────────────────────────────┤
│  SQLite (~/.kent/kent.db)                │
│  items · threads · workflows · memories  │
└──────────────────────────────────────────┘

Sources

| Source | Notes | |--------|-------| | iMessage | Reads chat.db. Requires Full Disk Access. | | Gmail | Via gws CLI. Also syncs Google Calendar and Google Tasks. | | GitHub | Via gh CLI. Notifications, PRs, issues. | | Chrome | History, bookmarks, downloads, search terms. | | Granola | Meeting transcripts from local JSON files. | | Apple Notes | Reads NoteStore.sqlite. Requires Full Disk Access. | | Signal | Reads encrypted DB. Needs brew install sqlcipher and Signal Desktop. | | AI Coding | Claude Code and Codex conversation history from local session files. |

Workflows

Workflows are prompts that run on a cron schedule. They live in the database and are managed via the CLI or web dashboard — no config files needed.

Default workflows

| Workflow | Schedule | What it does | |----------|----------|--------------| | Morning briefing | 8am daily | Calendar, emails, to-dos, action items | | Evening recap | 7pm daily | Today's summary, highlights, tomorrow preview | | Memory curator | 10am daily | Reviews data, updates knowledge base, archives stale memories | | Workflow suggestor | 9:30am daily | Analyzes patterns, suggests new automations |

Managing workflows

kent workflow list                   # list all workflows
kent workflow create <name>          # create a new workflow
kent workflow run <name>             # manually trigger a workflow
kent workflow enable <name>          # enable a workflow
kent workflow disable <name>         # disable a workflow
kent workflow delete <name>          # delete a workflow
kent workflow history <name>         # show recent runs

You can also create, edit, enable/disable, and run workflows from the web dashboard.

Web dashboard

kent web

Opens a local React dashboard at http://localhost:5173 with pages for:

• Home — feed of recent workflow runs and briefs
• Chat — multi-turn conversations with the agent
• Activity — live stream of workflow runs with output previews
• Workflows — manage, enable/disable, run, view history
• Sources — sync status, item counts
• Memories — browse and search the knowledge base
• Identity — set your name, role, goals for better agent context
• Settings — configure sources, API keys, daemon interval

CLI reference

kent                              # interactive REPL
kent init                         # setup wizard (first sync + daemon + web)
kent run                          # start daemon + web as persistent services
kent status                       # check if all services are running
kent logs [source] [-f]           # view logs (daemon|api|vite|web)
kent daemon start                 # start background daemon via launchd
kent daemon stop                  # stop daemon + web services
kent daemon status                # live daemon status dashboard
kent sync                         # sync all sources now
kent sync --source imessage       # sync one source
kent sync --full                  # full re-sync (not incremental)
kent workflow list                # list workflows
kent workflow create <name>       # create a workflow
kent workflow run <name>          # manually run a workflow
kent workflow enable <name>       # enable a disabled workflow
kent workflow disable <name>      # disable a workflow
kent workflow delete <name>       # delete a workflow
kent workflow history <name>      # show recent runs for a workflow
kent web                          # start web dashboard supervisor
kent --version                    # print version
kent --help                       # show help

Data and security

All data stays on your machine. Kent stores everything locally:

• ~/.kent/kent.db — SQLite database (synced items, threads, workflows, memories)
• ~/.kent/config.json — API keys, source toggles, daemon settings
• ~/.kent/daemon.log — daemon activity log
• ~/.kent/prompts/ — agent system prompt files

API keys and model providers:

Kent supports multiple LLM providers. Configure your preferred provider during kent init or in ~/.kent/config.json.

| Provider | Key required | Notes | |----------|-------------|-------| | Anthropic | Yes (default) | Claude models. Default: claude-sonnet-4-6 | | OpenAI | Optional | GPT models | | Google | Optional | Gemini models | | OpenRouter | Optional | Access multiple models via OpenRouter | | Local (Ollama) | No | Local models via Ollama | | Custom | Optional | Any OpenAI-compatible endpoint via base_url |

Project structure

cli/          CLI entry point and commands
daemon/       Background sync daemon and source adapters
agent/        Agent subprocess, tools, prompts
shared/       Database, config, shared types
web/          React web dashboard (Vite + React)
tests/        Test suite

License

MIT