
Your one-person Wall Street.
OpenAlice turns coding agents into local trading agents by giving them a workspace, files, issues, market tools, and approval-gated trading primitives.

[!CAUTION] OpenAlice is experimental software in active development. Many features and interfaces are incomplete and subject to breaking changes. The trading layer is especially beta. Do not use OpenAlice for live trading with real funds unless you fully understand and accept the risks involved. The authors provide no guarantees of correctness, reliability, profitability, or loss prevention.
OpenAlice is a local trading workspace for coding agents.
The core idea is simple: coding agents became useful quickly because software work already has a collaboration substrate. Code has git, issues, markdown docs, review workflows, linters, terminals, logs, and reproducible project folders. A coding agent can enter that world and immediately understand how to inspect, modify, review, and report work.
Trading usually does not have that shape. A trader may read news, browse charts, hold broker positions, and keep private notes, but the work is rarely organized as a collaborative system that a human and multiple AI agents can share.
OpenAlice tries to make trading agent-operable by mapping trading work onto the tools coding agents already understand:
OpenAlice does not replace Claude Code, Codex, opencode, Pi, or other coding agents. It gives them a trading-shaped place to work.
Start with read-only research. You do not need a broker account to get value from OpenAlice.
[[wikilinks]].![]() |
![]() |
| Issue Board | Tracked Entities |
![]() |
![]() |
| Inbox | Market Tools |
That loop is the main product surface today. A timer does not call a magic trading endpoint. It launches an agent against a self-describing workspace issue, using the same files, tools, memory, and reporting path an attended session uses.
| Surface | What it does |
|---|---|
| Workspaces | Per-task git repositories with a persistent terminal running claude, codex, opencode, pi, or shell. |
| Issue Board | Markdown-backed work items with status, priority, assignee, comments, links, and optional schedule metadata. |
| Tracked Entities | A durable graph for tickers, themes, sectors, people, risks, and theses. |
| Inbox | A delivery surface for reports, scheduled run output, and agent status updates. |
| Market Data | Equities, crypto, macro, fundamentals, symbol search, technical indicators, news, and RSS tools. |
| Unified Trading Account | Optional beta account abstraction for brokers such as Alpaca, IBKR, Longbridge, and CCXT venues. |
| Trading as Git | Stage, commit, review, and push account operations instead of letting an agent fire orders directly. |
Trading involves private notes, account state, credentials, strategy, and real money. OpenAlice runs on your machine by default, stores state as files under ~/.openalice, and keeps broker credentials sealed at rest.
There is no Postgres or Redis to provision. Config, sessions, issues, inbox entries, workspace artifacts, news archives, and trading history are ordinary files and git repositories. That makes the system easier to inspect, back up, debug, patch, and reason about.
Pick the run path that matches your machine:
The source path is still the best early-adopter path because it gives you logs and local code:
git clone https://github.com/TraderAlice/OpenAlice.git
cd OpenAlice
pnpm install
pnpm dev
Open the UI URL printed by the terminal, usually http://localhost:5173.
You also need at least one agent CLI installed and logged in, usually claude or codex. OpenAlice runs the model loop inside that native CLI so you keep its prompt cache, terminal rendering, provider login, and tool behavior.
The README is intentionally short. The real docs live at openalice.ai/docs.
OpenAlice is useful today for research, issue-based work, tracked memory, scheduled reports, and Inbox delivery.
Treat broker execution as beta infrastructure. Start with simulator, paper, demo, or testnet accounts. If you hit UTA errors, broker connection failures, or confusing execution behavior, bring the error to Discord or open a GitHub issue so we can reproduce it.
Stuck? The fastest path is usually:
OpenAlice is sharper for the people who dig into it with us: the bugs they catch, the ideas they push, the UX edges they notice, the designs and reviews they bring. High-signal issues and PR proposals count here. If a report, suggestion, or implementation proposal changes the product, it gets credited.
See the full list and what each person shaped: CONTRIBUTORS.md
$ claude mcp add OpenAlice \
-- python -m otcore.mcp_server <graph>