gitlawb/openclaude

runs anywhere. uses anything

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 8 minutes ago
Added to GitGenius on September 1st, 2026
Created on April 1st, 2026
Open Issues & Pull Requests: 79 (+0)
GitHub issues: Enabled
Number of forks: 9,062
Total Stargazers: 32,909 (+8)
Total Subscribers: 227 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.1 hours
Mean response time: 2.5 days
90th percentile: 5.8 days
Tracked items: 605

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 82% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 11% of tracked open issues have had no activity in three months. Only 11% of issues opened in the past year have been closed. Three people close 79% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 45
New in 7 days: 7
Closed in 7 days: 4
Avg open age: 47 days
Stale 30+ days: 21
Stale 90+ days: 4

Recent activity

Opened in 7 days: 7
Closed in 7 days: 3
Comments in 7 days: 4
Events in 7 days: 12

Top labels

  • bug (73)
  • enhancement (39)
  • opengateway (27)
  • information needed (15)
  • Gitlawb (9)
  • help wanted (5)
  • question (5)
  • wont do (5)

Detailed Description

OpenClaude is a coding-agent CLI that works with any LLM provider through a unified terminal interface.

The tool solves the problem of managing multiple LLM providers and workflows by offering a single command-line entry point that supports OpenAI-compatible APIs, Gemini, GitHub Models, Codex OAuth, Codex, Ollama, Atomic Chat, and other backends. It maintains a consistent terminal-first workflow across all providers, enabling users to work with prompts, tools, agents, MCP, slash commands, and streaming output without switching between different interfaces or learning provider-specific syntax.

Developers should choose this tool if they work with multiple LLM providers or want flexibility in switching between cloud and local models without changing their workflow. It suits projects where provider independence matters—whether for cost optimization, avoiding vendor lock-in, or testing across different models. The tool is particularly valuable for teams that need a consistent CLI experience regardless of which backend they deploy against.

The project shows active development with regular commits addressing bug fixes and feature improvements. The codebase demonstrates ongoing refinement of core functionality and user experience. There is consistent attention to maintaining compatibility across the supported provider ecosystem. The project maintains documentation and setup guides that receive updates alongside feature work.