Model or dataset
composio-community/open-claude-cowork avatar
composio-community/open-claude-cowork

Open Claude Cowork puts a Composio tool layer behind an Electron chat window

Open Source version of Claude Cowork with 500+ SaaS app integrations

4,321 stars703 forksJavaScriptMIT

At a glance

What is it?
Open Claude Cowork is an Electron desktop client that drives the Claude Agent SDK and routes tool calls to 500+ SaaS apps through Composio Tool Router. Its README also describes a second product, Secure Clawdbot, though the top-level tree has no clawd/ directory.
Who is it for?
Adopt it if you want a local Electron client that pairs the Claude Agent SDK with the Composio tool layer and you are willing to supply your own Anthropic and Composio keys. Stay away if you want a phone or browser client, or if a provenance conflict between the root LICENSE file and the ISC field in package.json blocks your procurement process.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Activity is slowing. The repository last received commits 6 months ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • composio-community/open-claude-cowork4,321 ★ · -31
Star history
Repository2026-09-242026-11-21
composio-community/open-claude-cowork4.4k4.3k

-31 Stars in the last 58 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two products share one repository, and the split happens at the directory level

The README describes Open Claude Cowork and Secure Clawdbot side by side, and the difference is not branding. The README places Clawd in its own clawd/ directory with its own cli.js, adapters folder and README, but the repository's top level has no clawd/ directory. The desktop app lives in main.js, renderer/, server/ and preload.js.

For the reader deciding whether to install anything, that matters. The Quick Start gives the desktop app a three-line clone and setup.sh, then asks for two terminals. Clawd gets three different commands and a prompt to choose Terminal chat or Start gateway. Two entry points, two deployment shapes, one git clone.

Tool calls leave the Electron window and resolve against Composio Tool Router

The architecture is thin enough to describe in one pass. main.js is the Electron main process, preload.js bridges it to the renderer, and server/server.js is an Express backend. Inside that backend, providers/ holds separate Claude and Opencode implementations, and responses stream back over Server-Sent Events.

The tool layer is where Composio enters. Rather than shipping 500+ integrations as local code, the app depends on Composio Tool Router and MCP, and the README frames the integrations as Gmail, Slack, GitHub, Google Drive and more. The sidebar shows tool inputs and outputs as they happen, so you can watch a Gmail or Slack call execute rather than trust that it did. Two providers ship in one box: the Claude Agent SDK for Anthropic models, and the Opencode SDK pinned to latest for everything else.

Why the backend and the Electron shell need separate terminals on port 3001

Installation is a shell script the repository ships at the root:

bash
git clone https://github.com/ComposioHQ/open-claude-cowork.git
cd open-claude-cowork
./setup.sh

The script is the only automated step. After it finishes, nothing runs in one window. The backend and the Electron shell are separate processes and the README is explicit that you need two terminals open:

bash
# Terminal 1
cd server && npm start
bash
# Terminal 2
npm start

The first block starts Express from the server directory; the second starts Electron from the root, where package.json maps start to electron .. If the desktop client shows no connection, the troubleshooting table names the reason directly: ensure the server is running on port 3001. That single fixed port is also the first thing to check when the UI loads but stays empty.

Three API keys before anything works, and one of them is optional

Keys come from a .env file, and the shipped template defines only two variables:

bash
cp .env.example .env

ANTHROPIC_API_KEY is required, and the troubleshooting table adds a concrete check: Anthropic keys start with sk-ant-. COMPOSIO_API_KEY is equally required in practice, because it is what authenticates the Tool Router that resolves the 500+ integrations. The third key, the Opencode API key, is the optional one, and note that it has no placeholder in .env.example even though package.json already pulls in @opencode-ai/sdk at latest. Anyone switching to the Opencode provider has to add that variable themselves.

Two failure modes follow from this layout. A missing or mistyped Anthropic key surfaces as an API key error. And because .env.example ships two placeholders while the README describes three keys, a reader setting up the Opencode path will not find the variable name waiting for them.

Custom behaviour arrives as SKILL.md files, not as a plugin system

Extension happens through a folder, not a registry. Dropping a SKILL.md into .claude/skills/ at the project root is the whole interface:

markdown
---
description: Use this skill when the user asks about [topic]
---

# My Skill

Instructions for Claude...

The frontmatter carries a single description line, and Claude decides when to load the skill from that description. There is no manifest, which makes the mechanism easy to extend and easy to get wrong: a vague description means the skill may not be picked up.

The dependency ranges around that system are loose. @opencode-ai/sdk sits at latest with no version floor, @anthropic-ai/claude-agent-sdk is pinned to ^0.2.7, and electron-reload sits at ^2.0.0-alpha.1. An alpha loader in the dev dependencies means a fresh install can behave differently from the setup the documentation describes. The other ranges are caret ranges too: electron ^39.2.7, express ^5.2.1, dotenv ^16.4.5.

Sessions live in the Express process, which is why the two-terminal split matters

Persistent sessions are claimed for the desktop app, and the troubleshooting table shows where that state actually lives: check server logs for session ID.

Streaming has the same shape. Responses arrive token by token over Server-Sent Events, and the troubleshooting entry for slow streaming points at the firewall rather than at the code, because SSE is a long-lived HTTP connection that proxies often buffer or drop. Anyone running the backend on a remote box or behind nginx should expect to fight that first. Clawd solves the opposite problem: its memory is described as persistent across WhatsApp, Telegram, Signal and iMessage, but it is a different program with a different lifecycle, not a mode of this one.

What you give up against a browser or phone client

The desktop app runs on macOS, Windows and Linux through Electron, and nowhere else. There is no web build in the project structure and no mobile entry point, so the recurring question of opening this on a phone or in a browser has no answer inside this repository. Clawd reaches messaging apps, but it is a gateway bot, not a chat client you open and drive.

The alternative to weigh here is building the same thing yourself against the Claude Agent SDK and Composio's docs directly. That path gives you a backend you own, a session store you choose, and deployment to whatever platform you like, at the cost of assembling the tool routing, the streaming layer and the UI yourself. This repository is the shortcut: the pieces are wired, the two providers are prebuilt, and the 500+ integrations come from a hosted router rather than local adapters. What you trade for that is licence clarity (LICENSE is MIT while package.json says ISC) and the loose version ranges noted above, plus a Composio account and API key as a runtime dependency you cannot audit locally.

Editorial conclusion

Adopt it if you want a local Electron client that pairs the Claude Agent SDK with the Composio tool layer and you are willing to supply your own Anthropic and Composio keys. Stay away if you want a phone or browser client, or if a provenance conflict between the root LICENSE file and the ISC field in package.json blocks your procurement process. Verify first that npm start launches Electron and that the Express server answers on port 3001, because every tool call, every streamed reply and every persisted session depends on that handshake.

Frequently asked questions

what is open claude cowork

It is an open-source Electron desktop chat application built on the Claude Agent SDK and Composio Tool Router, with 500+ SaaS app integrations including Gmail, Slack, GitHub and Google Drive. The README also describes Secure Clawdbot, a messaging assistant for WhatsApp, Telegram, Signal and iMessage, though the top-level tree has no clawd/ directory.

how to install open claude cowork

Clone the repository, cd into open-claude-cowork and run ./setup.sh. You also need an Anthropic API key and a Composio API key copied from .env.example into .env; the Opencode API key is optional.

how to use open claude cowork

After setup.sh finishes, start the Express backend and Electron separately, using cd server && npm start in one terminal and npm start in another. If the client cannot reach the backend, the server must be listening on port 3001.

how to open claude cowork

Open Claude Cowork has no separate window or mode to enable. It is a desktop application you launch from the terminal with npm start, which maps to electron . in package.json. There is no browser or phone build in the repository.

Official sources

  1. composio-community/open-claude-cowork on GitHub
  2. Issues
  3. License: MIT
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/composio-community-open-claude-cowork.svg)](https://hysenlabs.com/projects/composio-community-open-claude-cowork)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/composio-community-open-claude-cowork.svg)](https://hysenlabs.com/projects/composio-community-open-claude-cowork)

Was this useful?