BETOPIA CODER

Code with confidence.

A terminal-first AI coding assistant for understanding a codebase, making focused changes, and validating the result—without giving up control of your project.

Terminal-firstWorks in your repositoryApproval-based actions

01Install CoderSet up the CLI in one command.02Start a projectOpen a repo and give Coder context.03Choose a modePlan first or let Coder implement.

GET STARTED

Install Betopia Coder

Use the installer for your operating system. It downloads the matching CLI and adds the betopia command to your path.

macOS & Linux

bash

curl -fsSL https://betopia.ai/install.sh | sh

Windows PowerShell

powershell

irm https://betopia.ai/install.ps1 | iex

Other installation methods

Method	Command	When to use it
npm	`npm install -g @betopia/betopia-cli@latest`	Node.js 18+ environments.
Go	`go install github.com/betopia/betopia-coder@latest`	Go-based workflows.
Source	`go build -o betopia .`	Contributing to Coder itself.

bash

betopia --version

FIRST PROJECT

Give Coder useful context

Open a terminal at the root of the repository you want to work on, then start a session.

bash

cd my-project\nbetopia

Connect a providerOpen Ctrl+Shift+O or type /api to add your API key.

Describe the outcomeName the relevant files, desired behaviour, and a test command when you have one.

Generate project contextRun /init once to create BETOPIA.md for future sessions.

Run one task non-interactively

bash

betopia run "Explain the architecture of this project"

WORKFLOW

Pick the right operating mode

Modes make the level of autonomy explicit. Switch modes with Shift+Tab or use /mode.

Planning

Read, inspect, and produce a reviewable plan. File writes and shell commands are unavailable.

Agentic

Implement a reviewed plan with the complete Coder toolset. This is the default mode.

Auto

Lets the backend select Planning or Agentic based on the task and current plan state.

Orchestration

Runs larger work through focused stages, from discovery to QA.

DAILY WORK

Work in small, verifiable steps

Inspect firstAsk Coder to trace a flow, explain the codebase, or identify likely causes before editing.

Make a scoped changeGive an expected outcome instead of a vague request. Coder proposes the files and commands it needs.

Validate and reviewRun the focused test or build, then review the Git diff before merging.

Good first prompt

text

Trace the login validation path. Identify the timeout cause, propose the smallest fix, and tell me which test validates it.

REFERENCE

Keyboard shortcuts

Shortcut	Action
`Ctrl+C`	Quit Coder.
`Ctrl+L`	Switch provider or model.
`Shift+Tab`	Cycle operating mode.
`Ctrl+Shift+O`	Open API keys and configuration.
`Ctrl+S`	Browse saved sessions.
`Ctrl+N`	Start a new session.
`/`	Open slash commands.
`@`	Mention a file in the prompt.

REFERENCE

Commands that matter most

Command	Use it for
`/api`	Manage provider credentials and configuration.
`/model`	Switch the active model.
`/review`	Review current Git changes for concrete bugs.
`/sessions`	Browse and resume prior work.
`/init`	Generate project context.
`/status`	View workspace, LSP, and MCP status.
`betopia run "task"`	Run a single non-interactive task.