yottacode
Local-first terminal coding agent that turns issues into tested pull requests with approval gates.
Tested on Linux
Use it
Linux x86_64
You need first
- Keys or accounts: OPENAI_API_KEY
download install script from https://yottacode.ai/cli/install.sh
curl -fsSL https://yottacode.ai/cli/install.sh -o /tmp/install.shrun install script with --no-modify-rc, installs 0.5.0 to ~/.yottacode/bin
bash /tmp/install.sh --no-modify-rc
Check that it works
export PATH="$HOME/.yottacode/bin:$PATH" && yottacode --version
The output should contain “yottacode version 0.5.0”.
What it does
- Turn issues into tested pull requestsNot tested
- Manage branches, commits and pull requestsNot tested
- Approve file writes and shell commandsNot tested
How far pickfit got
Linux x86_64
- Installs
- Starts
- 0 of 3 features work
- Works offline
macOS: the project says it runs there; pickfit hasn’t tried it.
Good for
- review a PR diff, check CI and draft follow-up comment
- reproduce failing test, patch code and rerun checks
- update YAML, Helm, Terraform or deployment config
- turn an issue into branch, commits and pull request
- map an unfamiliar codebase in plan mode before editing
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Installs and starts
- Replayed from scratch
- Works offline
- Checked on 31 Oct 2026
- Version 0.5.0
Differences the test machine hit
- README: curl -fsSL https://yottacode.ai/cli/install.sh | bash installs yottacode ready to run
In the test: installer puts binary in $HOME/.yottacode/bin which is not on default PATH (~/.local/bin); needed manual ln -sf ~/.yottacode/bin/yottacode ~/.local/bin/yottacode or export PATH - README: yottacode setup then yottacode
In the test: both require a provider/API key (OPENAI_API_KEY etc) or Ollama; doctor exits 1 with 'no model set: pass --model <name>, export YOTTACODE_MODEL, or run yottacode setup'