openclaude

An open-source command-line interface for coding agents that unifies access to various cloud and local LLM providers and tools.

runs anywhere. uses anything

34k stars9.1kLicense: No licenseUpdated 13 days ago0 opens

Preview

▍

What you can do with it

Use the same CLI workflow to interact with OpenAI, Gemini, or local Ollama models.
Manage coding agent tasks, file operations, and web tools from a single terminal interface.
Switch between different LLM providers and configurations seamlessly using saved profiles.

Try asking your agent

“Use `openclaude` to switch to my `gemini-pro` profile, then summarize the `README.md` file.”
“With `openclaude`, list all `.js` files in the current directory and use `ollama` to explain what the main `index.js` file does.”
“Using `openclaude`, configure a new provider for `anthropic-api` with my API key, then ask it to draft a unit test for `src/utils.py`.”

Safety check

Caution

Usable, but read the notes first.

●No clear license: check with the author before using it in a commercial product.

Automated scan of the repo files. Always review code you run.

From the README

OpenClaude is an open-source coding-agent CLI for cloud and local model providers.

Use OpenAI-compatible APIs, Gemini, GitHub Models, Codex OAuth, Codex, Ollama, Atomic Chat, and other supported backends while keeping one terminal-first workflow: prompts, tools, agents, MCP, slash commands, and streaming output.

OpenClaude is also mirrored to GitLawb: gitlawb.com/node/repos/z6MkqDnb/openclaude

Partners

<strong>GitLawb</strong>
<strong>Bankr.bot</strong>
<strong>Atomic Chat</strong>
<strong>Xiaomi MiMo</strong>
<strong>Atlas Cloud</strong>



  
    
      
      
    
  


  
    
      
      
    
  


  
    
      
      
    
  


  
    
      
      
    
  


  
    
      
      
    
  



<strong>AI/ML API</strong>
<strong>Novita AI</strong>
<strong>ApiSmart</strong>
<strong>Concentrate</strong>
<strong>Exa</strong>

Why OpenClaude

One CLI across cloud APIs and local model backends — no per-provider tooling
Guided provider setup and saved profiles with /provider
Coding-agent workflows in one place: bash, file tools, grep, glob, agents, tasks, MCP, and web tools
A bundled VS Code extension for launch integration and theme support
A pixel-art hero companion who fires an arrow every time you press Enter (really — see Meet your buddy)

Quick Start

Install

OpenClaude requires Node.js >=22.0.0 for npm installs and runtime. Bun is only needed for source builds and local development.

npm install -g @gitlawb/openclaude@latest

If you're on Arch Linux, you can install OpenClaude from the community-maintained AUR package:

paru -S openclaude

If the install later reports ripgrep not found, install ripgrep system-wide and confirm rg --version works in the same terminal before starting OpenClaude.

Verify / troubleshoot installed version:

openclaude --version
npm view @gitlawb/openclaude dist-tags
npm install -g @gitlawb/openclaude@latest

Start

openclaude

Inside OpenClaude:

run /provider for guided provider setup and saved profiles
run /onboard-github for GitHub Models onboarding
run /search to choose the web search backend (Exa by default) or add a search API key

Note: OpenClaude does not automatically load project .env files. We recommend using the /provider command for setup, which saves provider profiles and credentials in .openclaude-profile.json. If you prefer environment variables, export them explicitly or run openclaude --provider-env-file .env for provider/setup variables. Export runtime/debug knobs from your shell or launcher.

Resume or fork a conversation

Resume an existing conversation by session ID, or continue the most recent conversation in the current directory:

openclaude --resume <session-id>
openclaude --continue

Add --fork-session to branch the conversation history into a new session ID instead of reusing the original transcript:

openclaude --resume <session-id> --fork-session
openclaude --continue --fork-session

Forking is conversation branching only. It does not create filesystem isolation, copy your working tree, or create a git worktree branch.

Background sessions

Run long non-interactive prompts detached from the current terminal:

openclaude --bg "fix failing tests"
openclaude --bg --name auth-refactor "refactor auth middleware"
openclaude ps
openclaude logs auth-refactor
openclaude logs auth-refactor -f
openclaude kill auth-refactor

Background sessions are local child processes. OpenClaude does not start a daemon or network service, and permission/provider/model/settings flags are passed to the child process the same way they are for a foreground --print run. Session metadata and logs are stored under the resolved OpenClaude config directory, usually ~/.openclaude/bg-sessions/; OPENCLAUDE_CONFIG_DIR can point OpenClaude somewhere else. CLAUDE_CONFIG_DIR is ignored for OpenClaude background-session storage. Session names can be reused after older sessions reach a terminal state; use the session ID to inspect older logs with the same name. A naturally finished session is recorded as exited when its process returns zero and failed when it returns nonzero or handles a termination signal. stale remains the conservative result when the process disappears without an observed outcome; an explicit successful openclaude kill is recorded as killed, and killed takes precedence over a natural exited or failed outcome for the same process. Terminal outcomes are stored separately under bg-sessions/terminal/; deleting that directory makes finished sessions fall back to liveness-derived status. OpenClaude does not infer POSIX signal names on Windows. Unobservable force termination, host crashes, and power loss remain stale on every platform.

openclaude attach <id-or-name> currently reports the matching session and points to openclaude logs <id> -f; full terminal reattach is not implemented for local background sessions yet.

OpenClaude config cutover

OpenClaude stores its own config under ~/.openclaude and ~/.openclaude.json by default. It does not read ~/.claude, project .claude/ directories, or CLAUDE_CONFIG_DIR; new users can start with a

View source on GitHub