<div align="right"> <details> <summary >🌐 Language</summary> <div> <div align="center"> <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=en">English</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=zh-CN">简体中文</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=zh-TW">繁體中文</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=ja">日本語</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=ko">한국어</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=hi">हिन्दी</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=th">ไทย</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=fr">Français</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=de">Deutsch</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=es">Español</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=it">Italiano</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=ru">Русский</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=pt">Português</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=nl">Nederlands</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=pl">Polski</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=ar">العربية</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=fa">فارسی</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=tr">Türkçe</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=vi">Tiếng Việt</a> | <a href="https://openaitx.github.io/view.html?user=RedPlanetHQ&project=core&lang=id">Bahasa Indonesia</a> </div> </div> </details> </div> <div align="center"> <a href="https://getcore.me"> <img width="200px" alt="CORE logo" src="https://github.com/user-attachments/assets/bd4e5e79-05b8-4d40-9aff-f1cf9e5d70de" /> </a>

The first AI butler you actually own.

Open source. Named. Persistent. Yours.

Today you use tools. Soon, you'll describe outcomes and your butler uses the tools.

https://github.com/user-attachments/assets/10197ad0-d7d4-44e3-9ea3-504aef81f65f

Why we're building this

Every AI agent you use today is smart. And every single one forgets you the moment the conversation ends.

We think that's broken. We think your AI should know you deeply, persistently, across every tool and every conversation. And once it knows you, it shouldn't sit there waiting for you to type. It should act.

Not recklessly. Intelligently. Sometimes it suggests and waits for your approval. Sometimes it just handles work because it's learned your patterns over weeks and months.

That's CORE. An AI butler that learns who you are, connects to your apps, and does the work before you ask. Open source, self-hostable, fully yours.

What this actually looks like

Your tasks are everywhere. A bug comes in on GitHub. A feature request lands in Linear. An action item is buried in a Slack thread. Another one hiding in an email you haven't read. Right now, you're the one tracking all of this in your head. CORE watches all of them and funnels everything into one place — tasks created automatically, nothing falls through cracks.

You're the glue between your tools and your coding agents. Before you can even start a Claude Code session, you spend 15 minutes gathering context — find the issue, read the thread, check related PRs, look at the error logs, then paste it all in. CORE does that job for you. Tell it "fix the checkout bug from issue #312" — CORE pulls the issue details from GitHub, searches memory for past decisions about that service, checks Sentry for the error trace, and spins up a Claude Code session with all that context already loaded. You come back to a PR.

You're running multiple agent sessions and losing track. Three Claude Code terminals, each working on something different, and you're context-switching between them trying to remember what's where. CORE is the orchestrator — kick off sessions from WhatsApp, Slack, or the dashboard. Each one gets the right context from memory and toolkit. CORE tracks what's running, reports back when things are done, and you stay focused.

At 2 AM, a Sentry alert fires. CORE has seen you triage these before — you always check the deployment diff first, then the error trace, then assign to whoever last touched that file. It does exactly that. Spins up a Claude Code session, investigates, creates the issue, assigns the right engineer. You wake up to: "Handled. Issue #847, assigned to Harshith." You didn't ask for any of this.

The difference? Every interaction makes CORE smarter. It learns your patterns, your codebase preferences, your team structure. It knows when to ask you for approval and when to just handle it — because it's been watching and learning. That's what a butler with memory does that a tool without memory can't.

CORE is right for you if

✅ You're tired of being the glue between your AI tools — re-explaining context, copying information, manually kicking off workflows
✅ You want an AI that actually remembers your preferences, decisions, and relationships and gets better over time
✅ You want proactive automation, not just reactive chat — an AI that watches your apps and acts on what matters
✅ You want to say "fix the checkout bug" on WhatsApp and it comes back with a PR
✅ You care about owning your AI — self-hosted, open source, your data never leaves your infra
✅ You want one brain across WhatsApp, Slack, email, and your coding tools — not five separate contexts

Without CORE vs. With CORE

| Without CORE | With CORE | |---|---| | ❌ You re-explain your project, stack, and preferences to every AI tool, every session. | ✅ CORE remembers everything — preferences, decisions, relationships, project context — and it gets sharper over time. | | ❌ Your AI tools can take actions, but they can't decide which action to take for you. They don't know you. | ✅ CORE's temporal memory means it understands nuance: who this client is, how you handle Sentry alerts, what your morning priorities look like. | | ❌ You are the bottleneck. Every workflow starts with you typing something. | ✅ CORE watches webhooks, polls your tools, and acts proactively — sends you a morning brief, triages alerts, drafts replies. | | ❌ You have an idea at midnight. You have to find the repo, open a terminal, set up context, babysit the agent. | ✅ Message CORE on WhatsApp: "migrate the auth service to Postgres." Come back to a PR. | | ❌ Your chat history is a graveyard. Decisions, preferences, and context die with every session. | ✅ Every conversation feeds a knowledge graph. Facts are classified (preference, decision, goal, directive) and connected over time. | | ❌ Different AI tools, different contexts, no shared understanding of who you are. | ✅ One brain. WhatsApp, Slack, email, Claude Code, Cursor — same memory, same butler. |

What CORE is not

| | | |---|---| | Not a chatbot. | Your butler has a name, a memory, and a job. It's not waiting for your prompt — it's watching your apps and acting on what matters. | | Not a RAG wrapper. | Memory isn't "embed chunks and search." It's a temporal knowledge graph where facts are classified, connected, and updated over time. It knows when you decided something and why. | | Not a copilot plugin. | Copilots assist when you're working. CORE works when you're not. It's proactive, not reactive. | | Not a workflow builder. | No drag-and-drop. You talk to CORE in natural language. It figures out the workflow. |

What your butler can do

🗂️ Task management that actually works

Your tasks are scattered — GitHub issues, Linear tickets, email action items, Slack requests. CORE watches all of them and funnels everything into one place (Todoist, Google Tasks). A GitHub issue gets assigned to you? Task created. An email has an action item buried in paragraph three? Task created. No manual entry, no things falling through cracks.

📋 Plan your day from one source of truth

Once your tasks are in one place, CORE helps you plan. It knows your calendar, your deadlines, your priorities. Ask it to plan your day and it builds a schedule from actual data — not a generic to-do list.

🚀 Hand off tasks to your butler — it does the work

This is where it gets powerful. CORE doesn't just track tasks — it can do them. A user reports a bug over email → CORE alerts you, creates a Todoist task, and when you say "handle it" → it spins up a Claude Code session, investigates the issue, writes the fix, opens a PR. You come

Core

Install / Use

README