Plan. Edit. Test. Review. Ship. Control your desktop.
A fast, lightweight, open-source AI coding agent built in Rust with 40+ tools.
My.Video.mp4
Why AlphaCode Β· Install Β· Quick Start Β· Desktop Control Β· Browser Bridge Β· Features Β· Configuration Β· Troubleshooting Β· Docs
AlphaCode is a terminal-native AI coding agent. Give it a goal in natural language and it can inspect your project, plan the work, edit files, execute commands, run tests, use browser tooling, coordinate multiple agents, and review the result.
It's built around a simple operating principle:
Make the smallest change that solves the problem β then verify it.
Think of AlphaCode as the execution layer between you and your AI models: instead of only discussing code, the agent works directly against the repository you opened.
flowchart LR
A["You<br/>Describe the goal"] --> B["Inspect<br/>Understand the repo"]
B --> C["Plan<br/>Choose the approach"]
C --> D["Execute<br/>Edit + run tools"]
D --> E["Verify<br/>Tests + self-review"]
E --> F["Report<br/>Changes + evidence"]
| Capability | What it means |
|---|---|
| Model-agnostic | Connect Claude, GPT, Gemini, GitHub Copilot, Cursor, OpenRouter, Bedrock, Azure, or any other OpenAI-compatible service. |
| Swarm Mode | Break large tasks into parallel sub-tasks, execute them concurrently, then review the combined result. |
| 40+ tools | Editing, search, shell execution, web access, browser control, desktop control, memory, sessions, scheduling, rendering, and more. |
| Desktop Control | Cross-platform native desktop automation via accessibility APIs (Windows UIA, macOS AX, Linux AT-SPI2). |
| MCP support | Model Context Protocol integration for extending tools via external servers. |
| Rust-native | Small runtime footprint, fast startup, and efficient long-running sessions. |
| Persistent sessions | Resume work after interruptions, crashes, dropped connections, or terminal restarts. |
| Safety controls | Destructive operations are blocked and risky actions pass through the permission layer. |
| Terminal-first UX | Rich TUI, syntax highlighting, Mermaid diagrams, LaTeX math, image previews, progress, and live agent activity. |
The figures below are historical benchmark snapshots retained for reproducibility and comparison. Treat them as directional rather than as current, universal measurements β see Reproducing these benchmarks for the full methodology.
One active session
| Tool | RAM | Relative to AlphaCode |
|---|---|---|
| AlphaCode | 27.8 MB | 1.0Γ |
| Codex CLI | 140.0 MB | 5.0Γ |
| pi | 144.4 MB | 5.2Γ |
| Cursor Agent | 214.9 MB | 7.7Γ |
| Antigravity CLI | 243.7 MB | 8.8Γ |
| GitHub Copilot CLI | 333.3 MB | 12.0Γ |
| OpenCode | 371.5 MB | 13.4Γ |
| Claude Code | 386.6 MB | 13.9Γ |
Ten concurrent sessions
| Tool | RAM | Relative to AlphaCode |
|---|---|---|
| AlphaCode | 117.0 MB | 1.0Γ |
| Codex CLI | 334.8 MB | 2.9Γ |
| pi | 833.0 MB | 7.1Γ |
| Antigravity CLI | 1,021.2 MB | 8.7Γ |
| Cursor Agent | 1,632.4 MB | 14.0Γ |
| GitHub Copilot CLI | 1,756.5 MB | 15.0Γ |
| Claude Code | 2,300.6 MB | 19.7Γ |
| OpenCode | 3,237.2 MB | 27.7Γ |
Reproducing these benchmarks
For a meaningful benchmark, record:
- AlphaCode version or commit
- OS and hardware
- Release/debug build profile
- Enabled optional features
- Number of active sessions
- Measurement method
- Warm vs. cold state
- Exact workload
See the benchmark methodology in the repository documentation for the full reproducibility process.
AlphaCode ships installers for Windows, macOS, and Linux, or you can build it from source.
Run in PowerShell:
iwr -useb https://raw.githubusercontent.com/dragonked2/alphacode/main/scripts/install.ps1 | iexThe installer:
- Detects your CPU architecture
- Downloads the latest release
- Verifies the SHA-256 checksum
- Installs
alphacode.exe - Can add AlphaCode to your user
PATH - Requires no administrator privileges
Pin a version
iwr -useb ... | iex -Version vX.Y.ZBuild from source
iwr -useb ... | iex -FromSourcecurl -fsSL https://raw.githubusercontent.com/dragonked2/alphacode/main/scripts/install.sh | bashThe installer downloads the platform archive, verifies its SHA-256 checksum, and installs the binary under ~/.local/bin/ by default.
Pin a version
curl -fsSL https://raw.githubusercontent.com/dragonked2/alphacode/main/scripts/install.sh \
| bash -s -- --version vX.Y.ZCustom install location
export ALPHACODE_PREFIX="$HOME/.local"
curl -fsSL https://raw.githubusercontent.com/dragonked2/alphacode/main/scripts/install.sh | bashEnvironment variables
| Variable | Default | Purpose |
|---|---|---|
ALPHACODE_PREFIX |
~/.local |
Installation prefix |
ALPHACODE_BIN_DIR |
$PREFIX/bin |
Binary directory |
ALPHACODE_VERSION |
latest |
Pin a release |
ALPHACODE_REPO |
dragonked2/alphacode |
Use a fork or mirror |
ALPHACODE_FROM_SOURCE=1 |
off | Build instead of downloading |
ALPHACODE_SOURCE_ONLY=1 |
off | Never fall back to source build |
ALPHACODE_SOURCE_REF |
HEAD |
Branch, tag, or commit to build |
git clone https://github.com/dragonked2/alphacode.git
cd alphacode
cargo build --release
./target/release/alphacode --versionRequirements
- Rust 1.91+ / edition 2024
git- A platform C toolchain:
- Linux β
build-essential,pkg-config,libssl-dev,libxkbcommon-dev(the Linux accessibility backend linkslibxkbcommon; without the-devpackage the link step fails withunable to find library -lxkbcommon) - macOS β Xcode Command Line Tools
- Windows β MSVC Build Tools + Windows SDK
- Linux β
Optional features
cargo build --release --features bedrock
cargo build --release --features embeddings
cargo build --release --features pdf
cargo build --release --features mermaid-rendererEnable multiple features together:
cargo build --release --features bedrock,embeddings,pdf,mermaid-renderermacOS / Linux
which alphacode
alphacode --versionWindows (PowerShell)
Get-Command alphacode
alphacode --versionalphacode --version reports the version of AlphaCode itself, along with your terminal, providers, browser integration, and optional dependencies.
Start with the built-in free AI lane, or connect your own provider.
1. Launch
alphacode2. Give it a real task
explain this project and identify the main entry points
find the failing test and fix the root cause
add authentication to this API and write tests for it
review this code for security issues and explain the findings
3. Useful keyboard shortcuts
| Key | Action |
|---|---|
F1 |
Open the keyboard shortcut reference |
Ctrl+T |
Switch models |
Ctrl+Y |
Inspect agent activity |
Ctrl+C |
Pause the active response while preserving the session |
Esc |
Close the current dialog / go back |
Cross-platform native desktop automation through accessibility APIs. AlphaCode can observe and interact with native desktop applications on Windows, macOS, and Linux.
flowchart TD
LLM["LLM Agent"] --> DT["Desktop Tools"]
DT --> DA["Desktop Abstraction Layer"]
DA --> XA11y["xa11y"]
XA11y --> W["Windows UIA"]
XA11y --> M["macOS AX"]
XA11y --> L["Linux AT-SPI2"]
How it works
The agent uses semantic accessibility APIs to understand and interact with desktop applications β not coordinates. It discovers applications, reads the UI tree, locates elements by role/name, and performs actions like clicking, typing, and pressing keys.
Key actions
| Action | What it does |
|---|---|
list_windows |
Discover running applications and their windows |
snapshot |
See the UI hierarchy of an application |
find |
Locate elements by role, name, or value |
click |
Click an element by ID (or coordinates as fallback) |
type |
Type text into a focused element |
press |
Press keyboard shortcuts (e.g. ctrl+c, enter) |
scroll |
Scroll an element or region |
focus |
Bring an application or element to focus |
screenshot |
Capture a screenshot of an application or full screen |
toggle |
Toggle a checkbox or switch |
expand / collapse |
Expand or collapse tree items, menus, disclosures |
Safety features
- Action timeouts (configurable, max 60s)
- Emergency stop (kills all desktop operations instantly)
- Input state cleanup (releases held keys/buttons on failure)
- Stale element detection (detects when UI changes mid-operation)
- Ambiguity handling (reports all matches when multiple elements match)
- Permission detection (clear errors when accessibility permissions are missing)
- Untrusted input sanitization (UI text is treated as untrusted data)
Platform support
| Platform | Backend | Status |
|---|---|---|
| Windows | UI Automation (UIA) | Supported |
| macOS | Accessibility API (AX) | Supported |
| Linux | AT-SPI2 | Supported |
Example workflow
User: "Open Calculator and calculate 123 * 456"
Agent (one `desktop` tool, dispatched by `action`):
1. desktop action="list_windows" β finds Calculator
2. desktop action="snapshot" β sees the calculator UI tree
3. desktop action="find" role="button" name="1" β gets element_id
4. desktop action="click" element_id=desk_42f91 β clicks "1"
5. desktop action="click" element_id=desk_42f92 β clicks "2"
6. desktop action="click" element_id=desk_42f93 β clicks "3"
7. desktop action="click" element_id=desk_42f94 β clicks "*"
8. desktop action="click" element_id=desk_42f95 β clicks "4"
9. desktop action="click" element_id=desk_42f96 β clicks "5"
10. desktop action="click" element_id=desk_42f97 β clicks "6"
11. desktop action="click" element_id=desk_42f98 β clicks "="
12. desktop action="snapshot" β reads result: 56088
When to use Desktop Control vs. Browser
| Use case | Tool |
|---|---|
| Web page content, DOM interaction | browser |
| Browser chrome, devtools, extensions | desktop |
| Native OS dialogs, file pickers | desktop |
| Desktop applications (Calculator, Notepad, etc.) | desktop |
| Certificate/permission prompts | desktop |
| Login forms in browser | browser |
AlphaCode includes browser automation through a local Browser Agent Bridge.
The bridge lets AlphaCode interact with a real browser session instead of relying only on HTTP requests β useful for pages that require JavaScript execution, authenticated sessions, DOM interaction, scrolling, frames, file uploads, and other browser-native operations.
The repository ships the bridge extension package here: browser-agent-bridge.xpi
Important β AlphaCode's current native browser backend is wired to the Firefox Agent Bridge. The bundled
.xpiis the primary supported path for AlphaCode browser automation. Chromium extension loading is documented below, but installing the package alone does not add Chromium backend support.
How the integration works
flowchart LR
A["AlphaCode"] --> B["Browser Bridge CLI"]
B --> C["Native Messaging Host"]
C --> D["Browser Extension"]
D --> E["Real Browser Session"]
AlphaCode can also manage its local browser bridge assets under its application data directory. For first-time setup:
alphacode browser setupCheck readiness:
alphacode browser statusMethod A β let AlphaCode handle setup
alphacode browser setupThen start Firefox and make sure the Browser Agent Bridge extension is enabled. Verify with:
alphacode browser statusMethod B β install the .xpi manually
- Download
browser-agent-bridge.xpifrom this repository. - Open Firefox and navigate to
about:addons. - Click the gear icon.
- Choose Install Add-on From Fileβ¦
- Select
browser-agent-bridge.xpi. - Enable the extension if Firefox asks.
- Run
alphacode browser statusto confirm.
For development/unsigned-extension workflows, Firefox may restrict direct installation of unsigned add-ons depending on the Firefox channel and configuration. In that case, use a development-compatible Firefox build/profile or a properly signed extension package.
Chrome does not install .xpi files directly. An .xpi is a ZIP-based WebExtension package, so a Chromium browser requires an extracted extension directory.
Windows
- Download
browser-agent-bridge.xpi. - Copy and rename it from
browser-agent-bridge.xpitobrowser-agent-bridge.zip. - Extract the ZIP to a normal directory.
- Open
chrome://extensions. - Enable Developer mode.
- Click Load unpacked.
- Select the extracted extension directory.
Linux / macOS
cp browser-agent-bridge.xpi browser-agent-bridge.zip
unzip browser-agent-bridge.zip -d browser-agent-bridgeThen open chrome://extensions, enable Developer mode β Load unpacked β select the extracted directory.
Compatibility note β loading the package successfully does not automatically mean the current AlphaCode browser backend supports Chrome. The current implementation uses Firefox-specific Browser Agent Bridge identifiers and native messaging paths. Chrome support therefore requires a Chromium-compatible bridge build and corresponding AlphaCode backend support. If Chrome reports manifest/API incompatibilities, the bundled Firefox package should not be treated as a supported Chrome backend.
Brave is Chromium-based, so the extension loading flow is the same as Chrome:
- Download
browser-agent-bridge.xpi. - Rename it from
.xpito.zip, then extract it. - Open
brave://extensions. - Enable Developer mode.
- Click Load unpacked.
- Select the extracted extension directory.
As with Chrome, installing the extension package is separate from AlphaCode backend compatibility β AlphaCode's current native browser integration is Firefox-oriented.
alphacode browser setup
alphacode browser statusA healthy setup reports that the bridge is installed, responding, and compatible with the current AlphaCode build.
If AlphaCode reports an extension mismatch, update the browser extension package and rerun both commands above.
AlphaCode is designed to work with multiple model providers instead of locking the agent to a single vendor.
| Provider | Authentication | Notes |
|---|---|---|
| Anthropic / Claude | Sign-in or API key | First-class support |
| OpenAI / GPT | Sign-in, API key, or browser | Reasoning, vision, tool use |
| Google Gemini | Sign-in or API key | Gemini models |
| GitHub Copilot | Sign-in | Reuses your Copilot session |
| Cursor | Sign-in | Reuses your Cursor session |
| AWS Bedrock | AWS credentials | Optional build feature |
| Azure | Azure AD or API key | Optional auth feature |
| OpenRouter | API key | Many models behind one endpoint |
| OpenAI-compatible APIs | API key | Custom providers |
| GMI Cloud | Built in | Free built-in AI lane |
| Experiential Labs | Platform-funded lane | Additional hosted models where available |
Provider commands
alphacode provider list
alphacode provider current
alphacode provider use openai
alphacode model list
alphacode model use <model>Inside the TUI, press Ctrl+T for the visual model picker.
Swarm Mode splits large objectives into parallel tasks and coordinates multiple AI agents.
flowchart LR
G["Goal"] --> P["Planner"]
P --> A["Agent A"]
P --> B["Agent B"]
P --> C["Agent C"]
P --> D["Agent D"]
A --> M["Merge"]
B --> M
C --> M
D --> M
M --> R["Review"]
R --> X["Verified Result"]
Example:
/swarm "split this feature into 4 independent implementation tasks"
The goal isn't parallelism for its own sake β tasks should be decomposable, independently actionable, and reviewable.
AlphaCode includes 40+ built-in tools, organized by capability area:
File Operations
| Tool | Description |
|---|---|
read |
Read file contents with line ranges |
write |
Create or overwrite files |
edit |
Make targeted edits to existing files |
multiedit |
Apply multiple edits across files |
patch |
Create and apply patches |
apply_patch |
Apply unified diff patches |
ls |
List directory contents |
Search & Analysis
| Tool | Description |
|---|---|
agentgrep |
Code-aware regex search across the project |
session_search |
Search conversation history |
conversation_search |
Search within session transcripts |
Execution
| Tool | Description |
|---|---|
bash |
Execute shell commands with safety controls |
batch |
Execute multiple tool calls in sequence |
bg |
Run commands in the background |
Web & Browser
| Tool | Description |
|---|---|
browser |
Real-browser automation via Firefox bridge |
webfetch |
Fetch and extract web page content |
websearch |
Search the web (DuckDuckGo, Bing, SearXNG) |
scrapling |
Advanced web scraping |
httpflow |
HTTP request/response analysis |
open |
Open files and URLs |
Desktop Control
| Tool | Description |
|---|---|
desktop |
Cross-platform desktop automation via accessibility APIs |
macos_computer_use |
macOS-specific desktop control (macOS only) |
Intelligence & Memory
| Tool | Description |
|---|---|
memory |
Project memory and context retrieval |
initiative |
Goal and initiative tracking |
todo |
Task and todo list management |
plan |
Plan mode for complex tasks |
Communication & Integration
| Tool | Description |
|---|---|
swarm |
Multi-agent coordination and communication |
gmail |
Email reading and sending |
clipboard |
Clipboard access |
skill_manage |
Browse and manage skills |
discover_tools |
Discover third-party tool integrations |
System & Utilities
| Tool | Description |
|---|---|
doctor |
System diagnostics and health checks |
self_improve |
Agent self-improvement capabilities |
selfdev |
Self-development mode |
cron |
Cron-style scheduled tasks |
schedule |
Ambient mode scheduling |
jwt |
JWT token parsing and validation |
side_panel |
Display content in the side panel |
invalid |
Handle invalid tool calls gracefully |
Included examples:
/bugbounty
/meme-coin-audit
/frontend-design
Browse available skills inside AlphaCode:
/skills
AlphaCode is designed to execute real operations while putting destructive actions behind explicit safeguards.
Safety controls
- Catastrophic filesystem/device targets are blocked.
- Risky actions pass through the TUI permission layer.
- Authorized security tooling can run through the normal execution path.
- Network operations apply SSRF and credential-leak heuristics where relevant.
- Interrupted or crashed sessions are marked rather than silently discarded.
- Desktop control includes emergency stop, input state cleanup, and action timeouts.
Session reliability
alphacode --resume
alphacode sessions listSessions are persisted to disk, so work can continue after connection loss, terminal restarts, or interrupted runs.
Review changes before shipping:
/diff
Report security vulnerabilities privately through SECURITY.md.
AlphaCode's agent behavior is centered around four guarantees:
| Principle | Behavior |
|---|---|
| Smallest change | Avoid unrelated edits and unnecessary refactors. |
| No regressions | Preserve passing behavior and validate changes. |
| Self-review | Check coverage, evidence, edge cases, and risk before completion. |
| Clear reporting | Explain what changed, what was verified, and what remains. |
The system prompt and tool implementations enforce these behaviors inside the codebase.
alphacode # Launch the TUI
alphacode login # Authenticate with a provider
alphacode login --provider openai # Authenticate with a specific provider
alphacode provider list # List configured providers
alphacode provider add <name> # Add an OpenAI-compatible provider
alphacode provider use <name> # Select the default provider
alphacode provider current # Show current provider/model
alphacode model list # List models
alphacode model use <name> # Select the default model
alphacode run "fix the failing test" # Execute one task directly
alphacode repl # Text-only mode
alphacode sessions list # List stored sessions
alphacode --resume # Search and resume a session
alphacode --resume <id> # Resume a specific session
alphacode browser setup # Install/repair browser bridge
alphacode browser status # Check browser bridge readiness
alphacode update # Update AlphaCode
alphacode --version # Show version
alphacode --help # Show help| Command | Purpose |
|---|---|
/help |
Show available commands |
/agents |
Work with multiple agents |
/compact |
Compress a long session |
/memory |
Inspect project memory |
/skills |
Browse skills |
/diff |
Review file changes |
/poke |
Auto-follow-up toggle |
/screenshot-mode |
Toggle screenshot capture |
/exit |
Exit while preserving the session |
alphacode updateYou can also run /reload inside the TUI to reload the current application state, when supported by the active session.
For release history, see CHANGELOG.md.
AlphaCode keeps configuration and session data outside your project directory.
| Platform | Settings | Sessions | Logs |
|---|---|---|---|
| Linux | ~/.config/alphacode/ |
~/.local/share/alphacode/sessions/ |
~/.local/share/alphacode/logs/ |
| macOS | ~/Library/Application Support/alphacode/ |
platform app-data location | platform app-data location |
| Windows | %APPDATA%\alphacode\ |
%LOCALAPPDATA%\alphacode\sessions\ |
%LOCALAPPDATA%\alphacode\logs\ |
The initial configuration file is created automatically after provider setup.
Full reference: docs/configuration.md
Key configuration sections
| Section | Purpose |
|---|---|
[provider] |
Default model, reasoning effort, failover |
[features] |
Memory, swarm, mermaid, auto-poke |
[display] |
Theme, reasoning display, diff mode |
[websearch] |
Search engine selection |
[agents] |
Swarm model, memory embedding backend |
[hooks] |
Lifecycle hooks (turn start/end, pre/post tool) |
[safety] |
Notifications (ntfy, email, Telegram, Discord) |
[compaction] |
Context management (reactive, proactive, semantic) |
[power] |
Prevent sleep while streaming |
[gateway] |
WebSocket gateway for remote access |
macOS / Linux
curl -fsSL https://raw.githubusercontent.com/dragonked2/alphacode/main/scripts/uninstall.sh | bashTo also remove configuration, sessions, and logs:
curl -fsSL https://raw.githubusercontent.com/dragonked2/alphacode/main/scripts/uninstall.sh \
| bash -s -- --purgeWindows
iwr -useb https://raw.githubusercontent.com/dragonked2/alphacode/main/scripts/uninstall.ps1 | iexUse the script's purge option when you also want local settings, sessions, and logs removed.
alphacode/
βββ src/
β βββ alphacode_core/ # Shared/provider-agnostic types
β βββ alphacode_base/ # Prompt/config/capability foundations
β βββ alphacode_app_core/ # Agent loop, tools, autonomous layers
β βββ alphacode_tui*/ # Terminal UI and workspace components
β βββ alphacode_tool_core/ # Tool abstractions and shared types
β βββ alphacode_provider_*/ # Provider runtimes
β βββ alphacode_auth_*/ # Provider authentication
β βββ alphacode_swarm_core/ # Multi-agent coordination
β β βββ tool/
β β βββ desktop/ # Cross-platform desktop control (xa11y)
β β βββ computer/ # macOS-specific desktop control
β β βββ browser.rs # Browser automation bridge
β β βββ bash.rs # Shell execution
β β βββ edit.rs # File editing
β β βββ ... # 40+ tools
β βββ alphacode_compaction_core/ # Context compaction
β βββ alphacode_memory_types/ # Memory system
β βββ alphacode_embedding/ # Local ONNX embeddings (optional)
β βββ alphacode_mcp/ # Model Context Protocol
β βββ cli/ # CLI entrypoint
βββ browser-agent-bridge.xpi # Bundled Browser Agent Bridge package
βββ docs/ # Architecture and configuration docs
βββ scripts/ # Installer/uninstaller scripts
βββ CONTRIBUTING.md
βββ SECURITY.md
βββ CHANGELOG.md
βββ Cargo.toml
Architecture reference: docs/architecture.md
git clone https://github.com/dragonked2/alphacode.git
cd alphacode
cargo build --release
cargo test --lib
cargo clippy --lib -- -D warningsBefore opening a pull request:
- Release build passes.
- Relevant tests pass and new behavior has tests where appropriate.
- Clippy is clean.
- Public APIs have documentation.
- New dependencies are justified.
- User-visible changes are documented in
CHANGELOG.md.
Read CONTRIBUTING.md for the full workflow.
alphacode is not found
macOS / Linux (bash)
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
source ~/.bashrcmacOS / Linux (zsh)
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc
source ~/.zshrcWindows
Add the AlphaCode installation directory to your user PATH, then open a new PowerShell session.
Browser bridge is not ready
Run:
alphacode browser statusFor first-time setup or repair:
alphacode browser setupFor Firefox, confirm the Browser Agent Bridge extension is installed, enabled, and running.
Desktop control permissions
- macOS β Grant Accessibility and Screen Recording permissions in System Preferences β Privacy & Security.
- Windows β No special permissions needed for most applications. Some elevated applications may require running AlphaCode as administrator.
- Linux β Ensure AT-SPI2 is available (
at-spi2-corepackage). Some applications may need--force-renderer-accessibilityfor Electron/Chromium apps.
Run the desktop tool with action='list_windows' to check if accessibility APIs are working.
rustc is too old
Only relevant for source builds:
rustup update stableThen rebuild.
Checksum verification failed
The installer intentionally refuses a corrupted or tampered archive. Retry the download first. If it repeatedly fails, preserve the exact error output and open an issue.
Broken terminal symbols or rendering
Use a modern terminal such as Windows Terminal, iTerm2, GNOME Terminal, Kitty, or WezTerm.
A Nerd Font such as JetBrains Mono Nerd Font or Cascadia Code Nerd Font can improve icon rendering.
Browser login opens but does not complete
Authentication callbacks can be affected by VPNs, firewall rules, browser policies, or local networking configuration.
Do I need to know how to code?
AlphaCode is primarily a developer tool. You can describe tasks in plain language, but understanding the project and reviewing the resulting changes remains important.
Is AlphaCode free?
AlphaCode is open source under the MIT License. Provider costs depend on the AI service you connect to. The project also includes a free built-in AI lane.
Which model should I use?
Use the provider and model that best fits the task. You can switch providers and models without changing your project workflow.
Can AlphaCode use my existing provider account?
Yes, where supported by the provider integration. You can authenticate through alphacode login or configure the corresponding API credentials.
Can AlphaCode automate a real browser?
Yes. AlphaCode includes Browser Agent Bridge integration. The currently supported native path is Firefox-based, with the bundled browser-agent-bridge.xpi package available in the repository.
Can AlphaCode control native desktop applications?
Yes. AlphaCode includes cross-platform desktop control via accessibility APIs (Windows UIA, macOS AX, Linux AT-SPI2). Use the desktop tool to discover applications, read UI trees, and interact with native elements.
Can I load the .xpi in Chrome or Brave?
Chromium browsers don't install .xpi files directly. You can rename the package to .zip, extract it, and use Load unpacked from the browser's extensions page. However, extension installation and AlphaCode backend support are separate; the current native AlphaCode browser backend is Firefox-oriented.
How do I update AlphaCode?
Run alphacode update.
docs/β documentation indexdocs/configuration.mdβ configuration referencedocs/architecture.mdβ architecture overviewCHANGELOG.mdβ release historyCONTRIBUTING.mdβ contribution guideSECURITY.mdβ security policy
If AlphaCode is useful to you, the highest-value ways to help are:
Star the repository Β· Report bugs Β· Improve documentation Β· Contribute code Β· Share the project