Contributing to Caroline — An open project only stays interesting if people actually build on it.

Build with her

This is AI for everyone. Stop waiting — build it.

Caroline ships with a default tool roster, but nothing about that roster is special or closed. Every capability she has is a standard MCP server, registered the same way any other Claude Code tool would be.

Ways to contribute

Three ways in

Add an MCP server

Write a standard MCP server for a capability she's missing, then register it with claude mcp add — the same mechanism Claude Code itself uses. No custom config format to learn.

Write a skill

Skills live under the workspace's Skills/ folder as plain SKILL.md files — a name, a description, and instructions Caroline loads on demand. Package up a workflow once, reuse it forever.

Port her to a new platform

Caroline is Windows-only today — the WPF shell and the native automation helpers are both win32-specific. The Node/TypeScript backend and the MCP servers underneath it are not. A macOS or Linux shell is exactly the kind of contribution this project needs.

Where things live

Windows/Caroline/	WPF shell — tray icon, hotkey, chat window, Settings
backend/	Node/TypeScript sidecar wrapping the Claude Agent SDK
backend/mcp-servers-src/	Source for every bundled MCP server
backend/skills-src/	Default skills, seeded into every workspace
Windows/CarolineInstaller/	The no-admin-rights installer

Browse the source Open on GitHub

Ground rules

What "open" means here

Apache 2.0. Fork it, run it, sell it, change it — the license doesn't ask permission. Pull requests are welcome for fixes, new MCP servers, new skills, and platform ports. For anything larger, opening an issue first to talk through the approach saves everyone time.