The agent for the Bitcoin ecosystem. Work with Bitcoin, Lightning, Liquid, RGB and Cashu — and your code, with the model you choose.
Node.js 22+ Runs on your machine
Demonstration
The same agent in the desktop app and in the terminal. Anything that changes files, runs commands or moves funds waits for you.
Desktop
Recorded in bitcode Desktop on an RGB test network with a local QVAC model. Pointer added; waits shortened where the badge shows it.
In an RGB session on a test node, paste an invoice and say how much to send.
Before anything is signed, a card spells out amount, asset, recipient, network and node.
Approve once and the node sends on the test network. The RGB tab shows the transfer in flight.
CLI
Recorded CLI excerpt. Typing animated; waits shortened. Not live fee estimates.
Type /btc:fees. Follow the tool call. Read the result.
/btc:fees asks for the current fee rates, with a word limit for the answer.
bitcode reads the network in read-only mode: mainnet, five fee tiers in sat/vB.
The model sums up the result in one sentence. Recorded on 2026-09-11: these are not live fees.
See the work happen
Desktop walkthroughs recorded from the real app, with the original terminal walkthroughs one click away.
CLI
Desktop
01 / FIRST RUN
Start the app, choose one of the models Ollama already serves on your computer, with its memory needs in view, and open a project. The first answer comes from that local model.
01 / INSTALL
Follow the source installation, install the core dependencies and run doctor. Check the version before moving on to model setup.
CLI
Desktop
02 / CONFIGURE
Give each Sat its own model, keep everything local, see where cloud keys would go and decide whether a phone may reach the app. Each chat then picks Manual, Assisted or Unattended.
02 / CONFIGURE
Use login to enter a masked API key, select a model at startup and inspect /setting. This walkthrough uses an example key and makes no provider request.
CLI
Desktop
03 / USE
In Manual mode the agent reads the project inside its sandbox, proposes the fix as a diff and asks before running a command. Approve each step, then read the Changes panel.
03 / USE
Type /btc:fees in the real CLI. Watch its command menu, tool output and streamed answer explain a recorded Bitcoin fee snapshot. Fee estimates do not guarantee confirmation times.
04 / RGB
An RGB session on a test node: the agent reads the balances, the receiving node issues an invoice in the app’s terminal, and a payment card waits for your approval before the node sends.
Desktop walkthroughs are screen recordings of the real app, its sandbox and a local model in a disposable setup: input is scripted, the pointer is added and waits play faster where the badge shows it. CLI walkthroughs use animated command entry with captured output and shorter waits; clone commands are instructional, login uses an example key and the Bitcoin response comes from the recorded local-model session. Transcripts include the source and context of each walkthrough.
Built to do the work
One conversation for code, chain data, RGB assets and configured wallets. Use a built-in command, ask in plain language, or bring your own tools.
Inspect fees, blocks, transactions and addresses. Create a wallet, receive bitcoin and confirm a send from your terminal.
/btc:fees /btc:tx /btc:send
/btc:feesExcerpt · original CLI outputDecode invoices, inspect channels and check balances. Send and receive with a configured LND node; connect tapd for assets.
/ln:decode /ln:channels /ln:pay
/ln:decodeCommand catalog · command not executedQuery Liquid fees, transactions, blocks and asset metadata. Read-only tools for understanding activity on the network.
/liquid:tx /liquid:asset
/liquid:assetCommand catalog · command not executedCheck balances, create invoices and send RGB assets through an RGB Lightning Node. The node’s changes wait for your approval. Signet test funds only.
--profile rgb /profile rgb
--profile rgbRGB profile · no node configured in this captureWork with mint quotes, tokens and payment requests. Manage your wallet and local mint with the optional Cashu binaries.
/cashu:mint /cashu:pending
/cashu:mintCommand catalog · command not executedRun inference locally with QVAC, Ollama or LM Studio. Local model examples: qwen3.8:27b · gemma4:26b · gpt-oss:20b · qwen3.6:35b-a3b. Choose a runtime compatible with your model and hardware.
-m qvac/bitcode-local /models
-m ollama/gpt-oss:20bLocal inference · Ollama · read-onlyRead and edit files, inspect Git changes, run tests and manage processes. Plan the work before making changes.
/repo:review /plan /build
/repo:reviewCommand catalog · command not executedConnect MCP tools, resources and prompts. Load local skills, add Markdown commands and delegate bounded tasks to subagents.
/mcp /skills /subagent
/mcpMCP inspection · no servers configured in this captureCapabilities depend on your configuration. RGB needs a running RGB Lightning Node and kaleido-mcp; Wavelength read-only tools need its optional binaries.
Explore all toolsMeet the Sats
Pick a Sat for the job. Each one has its own role, its own tools and limits enforced in code, in the CLI and in the desktop app.
Preview
SAT / 01
Bitcoin infrastructure
Reads Bitcoin, Lightning, Liquid and Taproot Assets data. Keeps the networks apart and never sends funds.
SAT / 02
Code and implementation
Inspects before changing code, implements the requested scope and verifies the result. Commands wait for your approval.
SAT / 03
Verification and security
Reviews changes, evidence and security boundaries. Separates verified findings from assumptions.
SAT / 04
Orchestration
Plans the work and delegates to Node, Script and Hash, one level deep. Delegating never hands over permissions.
The choice applies to your next messages and is saved with the session. /reset returns to bitcode.
/sats /sat merkle /sat info hash
Open the local companion: an animated view of each Sat's state and of Merkle's delegations. Interactive mode only.
node bitcode.mjs --sats
Sat permissions are application limits, not an operating-system sandbox. In the CLI, a shell command you approve runs with your user's rights. In the desktop app, the agent worker runs isolated with bubblewrap.
Visible steps. Deliberate actions.
Color-coded activity makes tool calls easy to follow. See what the agent reads, runs and changes, with results in the same conversation.
Interpret the request and identify the next step.
Execute a command or query the chain.
Gather context from files, tools and network data.
Prepare changes under your active approval policy.
Return results and explain what happened.
Start with --read-only to inspect. Interactive mode asks before changes; built-in financial tools require explicit authorization.
Resume saved sessions, compact long conversations, and use Ctrl+C to cancel supported operations.
Fits the way you work
Start a conversation, return structured output to a script, or use a local model through QVAC or Ollama. The tools stay with you.
OpenAI Responses · provider key required
Anthropic · provider key required
Use the exact ID offered by your deployment
node bitcode.mjs
Talk through a task. Mention files with @path and inspect available commands with /help.
node bitcode.mjs --read-only \ --json -p "review this repo"
Get an answer, tool events and usage as JSON. Use read-only mode for repository reviews.
node bitcode.mjs \ -m ollama/qwen3.8:27b
Use your running Ollama instance with a matching downloaded model tag. Network tools still contact their services.
npm --prefix integrations/qvac start node bitcode.mjs -m qvac/bitcode-local
Start the local QVAC server, then pick its configured aliases with /models. Weights download on first use.
bitcode Desktop
The same agent and the same Sats, in a workspace with projects, an editor, Git and a terminal. It is still in development, with no installable release yet.
In development
Development preview on Linux. The interface and features may change.
Open a folder and keep several chats for each project. Sessions are shared with the CLI.
An editor that warns about changes on disk, Git diff, stage and commit, and your own terminal.
Choose bitcode or a Sat for each chat and a model for each Sat. Approval cards appear in the conversation.
The agent worker runs in a bubblewrap sandbox, without your home folder or direct network access, and never receives provider keys.
One-time approvals tied to the session, a local-only mode, and your consent before a local model hands off to a cloud provider.
A Bitcoin test wallet and RGB wallet sessions, with an RGB node panel read through Tether WDK. Every send waits for your payment approval.
Lightning, Taproot Assets, Liquid and Cashu in view, each environment verified from its genesis block or the node’s API.
Tray icon, notifications without sensitive content, light and dark themes, English and Italian.
Test operations for Lightning, Taproot Assets, Liquid and Cashu, a Liquid wallet, an OS-level network gateway for commands, attaching from the CLI, checkpoints, updates and a tested .deb package.
Start with one command line
Install from source and choose your provider. The coding agent is ready without a JavaScript build step.
Node.js 22+, Git and Bash for shell tools.
Clone the repository and install dependencies.
Use a provider API key or a running local model.
# Get the source git clone https://github.com/faktotum-project/bitcode.git cd bitcode # Install without optional wallet builds npm ci --ignore-scripts # Check your setup and configure a provider node bitcode.mjs doctor node bitcode.mjs login openai node bitcode.mjs -m openai/gpt-6-astra
Use /login to configure another provider, /setting to inspect your setup, and /help to explore commands. Ollama uses a running local model and needs no API key.
node bitcode.mjs -m ollama/gpt-oss:20b
Start Ollama and download a model first. Replace the tag with one installed on your machine. Network tools still contact their services.
npm --prefix integrations/qvac start node bitcode.mjs -m qvac/bitcode-local
Start the QVAC integration after source installation. Weights download on first use. See the QVAC setup guide.
node bitcode.mjs --read-only --json -p "review this repo"
After source installation, configure a provider or select a local model. Read-only mode returns JSON without changing your repository.
Cashu and Wavelength need optional binaries. Run doctor to see what is available, and follow the setup instructions for the tools you need.
Privacy: no analytics, no live chain requests. Fonts are hosted here. Preferences stay in your browser.
