composio-community/open-claude-cowork

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

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 18 minutes ago
Added to GitGenius on September 15th, 2026
Created on January 13th, 2026
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 735
Total Stargazers: 4,360 (+0)
Total Subscribers: 40 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.8 days
Mean response time: 3.8 days
90th percentile: 3.8 days
Tracked items: 1

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 189 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Open Claude Cowork is a workflow automation tool that brings Claude's agentic capabilities to desktop environments with integrations across hundreds of SaaS applications.

The tool solves the problem of connecting Claude AI agents to external services and automating multi-step workflows. It provides a desktop application that allows Claude to interact with over 500 SaaS integrations, enabling agents to take actions across different platforms without manual intervention. The approach centers on making these integrations accessible through a unified interface where Claude can orchestrate tasks that span multiple applications.

Developers should consider this tool if they need to build AI-driven automation workflows that touch multiple SaaS platforms. It suits projects where Claude agents need to perform actions beyond conversation—such as creating tickets, updating spreadsheets, sending messages, or managing data across connected services. The open-source nature means teams can self-host and customize integrations for their specific needs rather than relying on a proprietary service.

The project shows active development with regular commits and ongoing work to expand and maintain the integration ecosystem. The codebase receives consistent updates addressing functionality and user-reported issues. Community contributions are being integrated into the project, indicating engagement beyond the core team.