whatisgithub

What is claude_opencode_settings?

arthur-albuquerque/claude_opencode_settings — explained in plain English

Analysis updated 2026-05-18

0PythonAudience · developerComplexity · 3/5Setup · moderate

In one sentence

A settings package that turns Claude Code into a coordinator directing cheaper OpenCode Go models to write code, so long sessions use less of Claude's usage limit.

Mindmap

mindmap
  root((claude opencode settings))
    What it does
      Claude as coordinator
      OpenCode as worker
      Saves Claude usage
    Included files
      Global CLAUDE.md
      Budget probe script
      Worker agent config
    Workflow
      Delegate code writing
      Review every diff
      Escalate on failure
    Tech Stack
      Python
      Claude Code
      OpenCode CLI

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Run long Claude Code sessions without burning through Claude's usage limits by offloading code writing to cheaper worker models.

USE CASE 2

Set up a clear split where Claude handles diagnosis and review while OpenCode Go models handle the actual code edits.

USE CASE 3

Track two separate usage budgets, one for Claude and one for the OpenCode Go worker plan, so you never get surprised by a block.

What is it built with?

PythonClaude CodeOpenCode CLINode.js

How does it compare?

arthur-albuquerque/claude_opencode_settings0xhassaan/nn-from-scratch3ks/embedoc
Stars00
LanguagePythonPythonPython
Last pushed2023-06-08
MaintenanceDormant
Setup difficultymoderatemoderatehard
Complexity3/54/51/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires an active OpenCode Go subscription plus manually merging JSON config into ~/.config/opencode/opencode.json.

No license information is stated in the README.

So what is it?

claude_opencode_settings is a configuration setup for people who use Claude Code alongside a separate OpenCode Go subscription. Instead of using Claude for every step of writing code, it turns Claude into a coordinator that handles the thinking work, diagnosing problems, breaking tasks down, reviewing code, and checking that things actually work, while handing off the actual typing of code to cheaper OpenCode Go models through the opencode command line tool, all from within the same Claude session. The point of this setup is to let long coding sessions run without running out of Claude's usage limits, because the bulk of token spending, the part where code actually gets written, happens on a flat rate worker plan instead of on Claude itself. The repository contains three files that install into your existing Claude Code and OpenCode setup. A CLAUDE.md file becomes the global system prompt and covers delegation rules, a table ranking which worker model to use for which kind of task, how to pace usage across two separate budgets, and a way to automatically resume long jobs later. A Python script checks how much budget remains on the OpenCode Go worker plan by sending a very small test request that does not use up any of the paid quota. A JSON file provides an example worker agent configuration that must be merged into your OpenCode settings, since without it OpenCode will silently refuse to let the worker model edit files. Setup involves installing the opencode command line tool with an active OpenCode Go subscription, having Node and Python 3 available, copying the CLAUDE.md and script files into the right folders, and merging in the worker agent configuration. Once that is done, every Claude Code session on the machine automatically follows the coordinator and worker split. The author notes a few limits to be aware of. The list of recommended worker models and their pricing reflects OpenCode Go's lineup as of July 2026 and will need updating as that catalog changes. The budget numbers assume a specific twelve dollar per five hour plan, so anyone on a different plan needs to adjust the figures themselves. The automatic resume feature only works while the Claude Code session and the machine it runs on stay awake, and the budget checking script can only tell you whether the worker plan is currently blocked, since OpenCode Go does not offer a way to check an exact percentage of usage remaining.

Copy-paste prompts

Prompt 1
Help me copy the CLAUDE.md and opencode-go-usage.py files from claude_opencode_settings into my ~/.claude folder.
Prompt 2
Explain how the worker agent config in opencode.worker-agent.example.json needs to be merged into my ~/.config/opencode/opencode.json.
Prompt 3
Walk me through how claude_opencode_settings decides which OpenCode Go model to delegate a coding task to.
Prompt 4
How does the budget probe script in claude_opencode_settings check whether my OpenCode Go plan is blocked without using up my quota?

Frequently asked questions

What is claude_opencode_settings?

A settings package that turns Claude Code into a coordinator directing cheaper OpenCode Go models to write code, so long sessions use less of Claude's usage limit.

What language is claude_opencode_settings written in?

Mainly Python. The stack also includes Python, Claude Code, OpenCode CLI.

What license does claude_opencode_settings use?

No license information is stated in the README.

How hard is claude_opencode_settings to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is claude_opencode_settings for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.