Open Source · AI Agent · October 2026
Cindy: The Open-Source AI Agent That Switches Harnesses Mid-Task
Cindy (makecindy/cindy) is an open-source AI agent that refuses to make you pick a side. Instead of locking one task to one tool, it lets you mix Claude Code, Codex, and Pi — switching harnesses or models mid-task while your workspace, memory, skills, and tools stay continuous. The pitch, in the project's own words: “Think it. Consider it done.” It trended on GitHub in late October 2026, and the one idea worth understanding is the harness layer.
Last updated: October 25, 2026. Star count and project status checked against github.com/makecindy/cindy and cindy.app on that date.
At a Glance
| Project | makecindy/cindy — “Consider it done. The open-source AI agent that works out of the box.” |
|---|---|
| Official site | cindy.app (service details, pricing, downloads) |
| Harnesses | Claude Code, Codex, Pi — more on the way; a Cindy-native harness is in development (roadmap, not a current capability) |
| Core claim | Switch harnesses or models mid-task; workspace, memory, skills, and tools stay continuous |
| Runs on | Your own machine, your real files and logged-in apps; Electron desktop app + Expo/React Native mobile client |
| License / stack | Client open under Apache-2.0; pnpm monorepo, Node.js 22.x, pnpm 10; backend service is a separate repository |
| Traction | GitHub Trending in late October 2026; about 4,100 stars at last check — a fast-moving project that started in July 2026 |
| Model access | Official Cindy service, your existing Claude Code/Codex plan, your own API keys, or local models |
The Idea That Matters: The Harness Layer
A model produces tokens. Getting useful work out of one takes a lot of machinery around it: something that holds context across many turns, decides which tools to expose, runs them in a sandbox, streams progress, catches failures, and pauses to ask a human before anything irreversible. That surrounding execution system is the harness. Claude Code is one harness. Codex is another. Each has blind spots — good at some things, stubborn about others — and until now you could not just swap in a different one when you hit a wall without losing the thread.
Cindy's answer is to hold the task state above the harness boundary. Cindy keeps the workspace, the memory, the skills, the tools, and the acceptance criteria; the harness underneath becomes replaceable. One task can be planned, executed in parallel, and reviewed by agents on different harness-and-model combinations, and everything switches mid-task without losing context. If that layer works, the question stops being “which agent do I use?” and becomes “which combination fits this step of the task?”
One Task, Three Roles: The Showcase Crew
Cindy's own example makes the idea concrete. A single task is split into three roles, each on a different combination: Claude Code plans first (architecture, work breakdown, acceptance criteria); three workers execute in parallel — one on Codex, one on Claude Code, one on Codex again, each with a different model — covering implementation, regression tests, and docs; then Codex performs an independent review as a quality gate (diff review, edge cases, pass or rework). Harnesses and models pass the baton while Cindy holds the task together. Treat this as the project's demonstration, not an independently measured benchmark — the honest test is running your own task through it.
Local-First, and More Than Code
Cindy runs locally on your own machine, using your real files and logged-in apps — the local-first premise is part of the appeal for developers who do not want their work routed through someone else's cloud by default. And the ambition goes past code: the project says Cindy can drive your browser, computer, and phone, and take work from instant messages and schedules. That makes it closer to a general-purpose agent that does real work on your computer than to a coding assistant with a chat box.
For model access, Cindy avoids the double-billing trap: if you already pay for a Claude Code or Codex coding plan, you authorize that plan inside Cindy and keep using it there. Otherwise you can sign in to the official Cindy service, connect your own API keys, or use local models. The client itself is free. Service pricing lives on cindy.app and is not restated here, so check the official page before committing to the hosted route.
The Honest Caveats
Three things to keep straight. First, only the client is open source: the backend service lives in a separate repository and is not part of the monorepo, so “open-source agent” describes the apps and shared packages, not the whole hosted stack. Second, the Cindy-native harness is in development — a roadmap item, not something you can use today. Third, this is a young, fast-moving project: it started in July 2026, and its issue tracker is busy. That is normal for a trending open-source agent, but it means you should read the README on github.com/makecindy/cindy before installing and expect rough edges rather than a polished product.
If you follow the proactive-agent wave, Cindy sits next to Anthropic's Claude Duet — but where Duet is a hosted, approval-gated product for professionals, Cindy is the open, local-first counterpart for developers who want to hold the harness layer themselves. For the model side of the same stack, see our Voxtral 3 guide. And if you want to turn agent output into video, start with HAILUOAI text-to-video.
FAQ
What is Cindy?
Cindy is an open-source AI agent that works out of the box. It runs locally on your own machine, using your real files and logged-in apps, and it brings multiple agent harnesses, models, and tools into one agent that finishes real work in your projects and apps. The project lives at github.com/makecindy/cindy and the official site is cindy.app.
What makes Cindy different from Claude Code or Codex?
The harness, not the model. Claude Code and Codex are harnesses — the machinery around a model that holds context, runs tools, and manages a task. Cindy sits above that layer: it supports Claude Code, Codex, and Pi as interchangeable harnesses, and every supported model runs across every supported harness. You switch harnesses or models mid-task while your workspace, memory, skills, and tools stay continuous, instead of starting over in a new tool.
Can Cindy really switch harnesses mid-task without losing context?
That is the project's core claim: Cindy holds the task, context, and acceptance criteria above the harness boundary, so a handoff does not reset the work. Its showcase example splits one task three ways — Claude Code plans, three workers execute in parallel on different harness and model combinations, and Codex independently reviews — while Cindy keeps the workspace and acceptance criteria together. Treat this as a product claim rather than an independently measured benchmark until you try it on your own task.
What can Cindy do besides coding?
According to the project, Cindy can drive your browser, computer, and phone, and take work from instant messages and schedules — positioning it closer to a general-purpose agent than a code-only assistant. The first supported harnesses are Claude Code and Codex, with more on the way and a Cindy-native harness in development.
Is Cindy free? How do models work inside it?
The client is free to use and its source code is open under Apache-2.0. For models, you bring your own access: sign in to the official Cindy service (usage deducted transparently), authorize the Claude Code or Codex coding plan you already pay for and keep using it inside Cindy with no duplicate bill, connect your own API keys, or use local models. Check cindy.app for current service details and pricing.
What is actually open source in Cindy?
The repository is the open-source client: an Electron desktop app, an Expo/React Native mobile client, and shared packages covering auth, device-link, agent orchestration, and model providers, organized as a pnpm monorepo (Node.js 22.x, pnpm 10). The backend service lives in a separate repository and is not part of this monorepo — so the client is open, but the hosted service behind it is not.
Who should try Cindy, and who should wait?
Try it if you already juggle Claude Code and Codex and lose work switching between them, or if you want one agent that keeps a task's context across harnesses. Wait if you need a stable, settled tool: the project started in July 2026, is moving fast, and its native harness is still in development. Read the README on github.com/makecindy/cindy before installing, and expect rough edges.
Turn ideas into AI video with HAILUOAI
Explore HAILUOAI's text-to-video and image-to-video tools to create your own AI-generated videos.