Announcement on GitHub Trending
The repository
Supported Harnesses and Models
Cindy allows free mixing of harnesses and models during a single task. A workflow can start planning on one combination, execute steps in parallel on another, and finish review on a third while keeping workspace state, memory, and tools consistent. The client handles context switching without resetting the session. This setup reduces the need to maintain separate agent instances for different backends. Developers can switch mid-task when one model handles code generation better and another performs stronger on browser automation steps.
The monorepo structure separates concerns across packages for protocol handling, configuration, and app-specific logic. Commands like pnpm install followed by workspace scripts build the shared components used by both desktop and mobile clients. This organization makes it straightforward to extend support for new harnesses once their APIs stabilize.
Local Execution and Tool Integration
The agent executes on the user's machine rather than a remote sandbox. It can control the browser, interact with the local file system, and operate phone emulators when permissions are granted. Tasks can originate from instant messaging integrations or scheduled triggers instead of requiring manual invocation each time.
Connection options include signing into the official Cindy service with transparent usage tracking, authorizing existing Claude Code or Codex plans, supplying personal API keys, or running local models. The client deducts usage only when the hosted service is selected. No duplicate billing occurs for users who already pay for the underlying harness plans.
Open Source Licensing and Customization
The client code is released under Apache-2.0. This license permits commercial use and modification of the desktop and mobile applications. The repository contains design documents, contribution guidelines, and security policies that outline how external developers can propose changes to the protocol or add new tool integrations.
Customization happens through the packages directory and configuration files. Teams can patch dependencies or add new skills without forking the entire monorepo. The presence of AGENTS.md and CLAUDE.md files indicates built-in support for documenting agent behavior and constraints directly in the source tree.
Limitations Observed So Far
Only two harnesses are implemented at launch. A native harness remains in development, so current users stay tied to Claude Code or Codex until additional options ship. Phone and computer control features depend on platform-specific permissions that vary by operating system. Documentation for extending the tool set is still limited to the initial code comments and design notes.
FAQs
What is the primary license for the Cindy client? The client source is available under Apache-2.0, allowing modification and redistribution with minimal restrictions.
Can Cindy switch models without losing task context? Yes, the architecture keeps workspace, memory, and tools continuous across harness and model changes.
Does Cindy require payment for the hosted service? No. Users can connect their own API keys or local models without using the official service at all.
---
π Related articles
- Agentic Coding: Una Trappola per lo Sviluppo Software?
- File agents.md: utili per gli agenti di coding?
- Lean-ctx: Ottimizzatore Ibrido Riduce Consumo Token LLM del 89-99%
Need a consultation?
I help companies and startups build software, automate workflows, and integrate AI. Let's talk.
Get in touch