core

://www.youtube.com/watch?v=PFk4RJvQg1Y CORE removes you from that loop. The interface is a shared scratchpad, think a page you and a colleague both have open. You write what's on your mind. When you write a checkbox line like `[ ] Fix the search bug`, CORE converts it into a task and starts working on it after a short delay (long enough for you to add context if you want to). No prompt template. No workflow to configure. The reason it can do this without you re-explaining everything: CORE keeps a persistent memory built from your tasks, conversations, and connected apps (Linear, Gmail, GitHub, Slack etc.). When it spins up a Claude Code session, it arrives with your codebase and project context already loaded. A real example: we wrote `[ ] Create a widget in Linear integration`, about 14 minutes later, CORE had opened a PR . What CORE is _not_: it's not Devin (no autonomous web browsing or shell loops you can't see), and it's not "Claude Code with memory bolted on." It's the layer above it that decides what should run, gathers the context, hands it to the right agent, and keeps the receipts in one place. Today the agent backend it spins up most often is Claude Code; the orchestration, scratchpad, memory, and integrations are CORE. Open source, self-hostable with `docker compose up` and it supports multiple models. GitHub: https://github.com/RedPlanetHQ/core Website: https://getcore.me (you can chat with Harshith's butler there) Demo: https://www.youtube.com/watch?v=PFk4RJvQg1Y

lly? Should users explicitly choose which spaces are active, or should AI auto-select based on context? What personal context do you find yourself repeatedly explaining to AI assistants? And how would you want to manage and be notified about which of your knowledge spaces the AI is actually using? Looking for insights from people who deal with AI consistency challenges daily.

ee tier (HN launch): https://core.heysol.ai - Local: docker compose up from https://github.com/RedPlanetHQ/core

tion, document, meetings etc.) - Enable seamless context recall in any AI app you use - No more vendor lock-in, you own your personal memory Do you think your AI memory should be owned by you, or should it remain vendor-locked with each platform? Disclaimer - I am building one of such 3rd party memory layer called CORE (https://github.com/RedPlanetHQ/core) hence it is important for me to understand how you folks see about memory ownership.

ame persistent context. - Temporal + relational: Every fact gets a full version history (who, when, why), and nothing is wiped out when you change it—just timestamped and retired. - Local-first or hosted: Run it offline in Docker, or use our hosted instance. You choose which memories sync and which stay private. Try it - Hosted free tier (HN launch): https://core.heysol.ai - Docs: https://docs.heysol.ai/core/overview

y the same persistent context. - Temporal + relational: Every fact gets a full version history (who, when, why), and nothing is wiped out when you change it—just timestamped and retired. - Local-first or hosted: Run it offline in Docker, or use our hosted instance. You choose which memories sync and which stay private. Why this matters - Ask “What’s our roadmap now?” and “What was it last quarter?” — timeline and authorship are always preserved. - Change a preference (e.g. “I no longer use shadcn”) — assistants see both old and new memory, so no more stale facts or embarrassing hallucinations. - Every answer is traceable: hover a fact to see who/when/why it got there. Try it - Hosted free tier (HN launch): https://core.heysol.ai - Docs: https://docs.heysol.ai/core/overview