Repository navigation
BoundedCode v0.1.0-alpha.2 (Public Alpha, pre-release)
Pre-releaseInstall once, then run bcode in any repository.
This alpha adds an interactive way to use BoundedCode, in the style of Claude
Code, Codex or OpenCode. It is a one-command install, a chat for the
repository you are in, and guided set-up of the local prerequisites. The
engine is the same as in
v0.1.0-alpha.1: local inference, sandboxed agent,
deterministic and behavioural verification. Its validation results are
unchanged and still apply. The interface is experimental.
Highlights
-
One-command install:
curl -fsSL https://raw.githubusercontent.com/akynte/boundedcode/main/scripts/install.sh | bashThis installs
boundedcodeand the short namebcodeinto~/.local/bin.
It uses the checksum-verified release binary attached to this release, and
otherwise builds from source with Go. -
Chat (
bcode): run it with no arguments in a git repository. The
repository is registered and indexed on first use. Each message becomes a
task that runs in an isolated worktree inside the sandbox, with its actions
and verification streamed into the conversation. Messages typed during a run
are queued, andescinterrupts. If a task stops on an ambiguous request,
your reply is the answer. After a task completes, the next message starts a
follow-up from its branch. Slash commands:/diff,/apply,/verify,
/review,/new,/open,/status,/model,/setupand more. -
Guided set-up (
bcode setup): checks the configuration, the pinned
tools (codebase-memory-mcp, gitleaks), llama.cpp, the default model weights
and the Docker sandbox image, and installs what is missing. It asks before
every download or build. The installers and the sandbox build context are
embedded in the binary, so no source checkout is needed. -
task apply: brings a completed task's changes into your checkout,
staged for review or committed with--commit. It refuses a checkout with
uncommitted changes, or changes that do not apply cleanly. -
Follow-ups:
task create --from TASKstarts a task from a previous
task's branch. -
Full-screen interface: besides the chat, there are views for tasks
(live activity, diff, verification, escalations), workspaces and indexing,
repository intelligence, the runtime and models, frontier escalations,
stats,doctorand Serena set-up, and a console for any other command.
Actions run the CLI commands in-process, so policy, sandboxing and audit
records are identical to the CLI. Frontier approvals appear as dialogs. -
Audit detail:
agent.eventrecords include a short, redacted summary
of each agent action and its stated reason, which feeds the live activity
view.
Upgrade notes
boundedcodewith no arguments in a terminal now opens the interface. In
scripts (no terminal) it prints help as before.- New Go dependencies: Charm Bubble Tea, Bubbles and Lip Gloss, and their
runtime. All are MIT or BSD-3-Clause and are listed in
THIRD_PARTY_NOTICES.md. - No configuration changes are required.
setupwrites a configuration only
when none exists.
Known limitations
- The interface and chat are experimental. They are tested with model-level
and backend tests and in a pseudo-terminal, not yet on a long real-model
session from the chat. setupbuilds llama.cpp from source, which needs git, cmake and a C++
compiler, plus the CUDA toolkit for GPU inference. To use a server you
already run, setinference.mode: external.- The model download is large (about 22 GB for the default profile).
- Linux x86-64 only.
- The validation limitations of
v0.1.0-alpha.1 still apply.
Assets
boundedcode-linux-amd64: static binary (CGO disabled).SHA256SUMS: checksums, verified by the installer.SBOM.spdx.json: SPDX 2.3 software bill of materials of the binary.boundedcode-v0.1.0-alpha.2-licenses.tar.gz:LICENSE,NOTICE,
THIRD_PARTY_NOTICES.mdand the license texts of every Go module compiled
into the binary (LICENSES/go) and of the upstream components
(LICENSES/upstream).
Model weights are not distributed. Download them with bcode setup, from
their publisher at a pinned revision, and review their license.