Omacharts on Omarchy

Omacharts on Omarchy

Omacharts is a fast, native, keyboard-first stock charting app for Omarchy — Rust + GTK4, themes itself to your desktop, charts free Yahoo Finance data out of the box or streams your Charles Schwab thinkorswim account, and ships a full CLI and agent skill so terminals and AI agents can drive every chart.

TL;DR

omarchy pkg add omacharts

Takes ~1 minute — the package is in Omarchy's own repo (v0.1.13-1 on the app-store page, Oct 2026), MIT licensed, and the launcher, man page, shell completions, and agent skill come along automatically. It works with zero setup: Yahoo Finance is the default data feed and needs no account.

Getting started (5 minutes)

1. Install and launch.

Run the command above. The binary lands at /usr/bin/omacharts; a desktop entry (com.jorgemanrubia.Omacharts.desktop) puts it in Super + Space.

2. First launch — no account, no onboarding.

Open it and you're looking at a chartbook immediately — no account, no onboarding wizard, no API key. First thing to try: type a letter to search symbols, a number to change resolution (1D, 1W, 1M…), and press ? to see every hotkey. The maintainer (Jorge Manrubia, 37signals) designed it keyboard-first, so learning ? is the single highest-leverage 30 seconds.

3. The 3 things you need to know:

• Chartbooks, not single charts — Split a chart horizontally or vertically (mouse or keyboard), as deep as you like; each chart keeps its own symbol, resolution, indicators and settings. Save arrangements as chartbooks, each with its own watchlist, and switch from the strip along the bottom. Link charts into one of nine groups and they move together — a pointer on one draws a crosshair on the rest (omacharts chart crosshair off to disable).
• Indicators and drawings are keystroke-fast — SMA, EMA, VWAP with bands, Bollinger bands, volume, volume profile, RSI, MACD, ATR, stochastic — each in its own resizable strip. Drawings: trendlines, levels, arrows, zig-zags, boxes, circles, text — one keystroke each. Colors are theme roles, so drawings stay readable when you switch Omarchy themes; palette names (Amber, Teal…) re-resolve on theme change, #rrggbb stays fixed.
• Everything the window does, the CLI does — omacharts watchlist create Semis && omacharts watchlist add Semis NVDA AMD AVGO TSM MU builds a watchlist without touching the GUI; commands hit the running window live or, with nothing open, work against the stored database (even over ssh). omacharts surface --json emits the whole command surface for scripting, and omacharts skill install installs a skill so your AI agent (Claude Code, Codex) can chart for you. The Omarchy bar plugin installs itself on first run — your watchlist lives in the bar with sparklines, surviving the window closing; omacharts plugin manages it.

4. Data feeds.

Yahoo Finance default: nothing to configure. thinkorswim (Charles Schwab): pick it in Preferences → Market data → Provider, or omacharts config set provider tos, then omacharts provider login. That opens a real Chrome/Chromium/Brave/Edge window where you sign in yourself — Omacharts never sees your password or OTP, types nothing into the page, and keeps only the browser session (stored in ~/.config/omacharts/tos.env and ~/.config/omacharts/tos-browser/). It has no order-entry code at all; it only asks for charts. Coverage limits: thinkorswim charts US stocks/ETFs, futures, class shares and major indexes; Taipei (2330.TW) and Madrid listings have no thinkorswim names — those charts fall back to Yahoo.

5. Config location.

~/.config/omacharts/ (including tos.env and tos-browser/ for the thinkorswim session). Watchlist export/import (omacharts watchlist export / import) carries setups between machines.

Practical notes: The app follows your Omarchy theme and generates an indicator palette per active theme, with a dedicated Omarchy bar plugin plus an agent skill — a first-class Omarchy citizen, not a ported web app. Binaries ship for x86_64 and aarch64 (covers Asahi).

Common issues & fixes

In fullscreen (Super + F), right-clicks on the top ~26px of the window do nothing

Only the bottom fifth of the resolution-strip buttons responds. This is not an omacharts bug (issue jorgemanrubia/omacharts#55, opened Oct 12 2026): Omarchy's bar hides behind the fullscreen window but stays on Hyprland's top layer, stealing pointer input (upstream omacom/omarchy#14079).

Fix: A fix exists in omacom/omarchy#14162 (moves the bar to the bottom layer while a workspace is fullscreen) but it was unreviewed and conflicting as of the issue date. Workaround until it merges: right-click lower on the buttons, or leave fullscreen.

omacharts provider login says it needs a Chromium-family browser

And you only have Omarchy's default. The thinkorswim sign-in opens a real Chrome/Chromium/Brave/Edge window by design — the app never handles your credentials directly.

Fix: Install one (omarchy pkg add chromium or your pick) first; the app keeps the session in a dedicated profile beside it so the next sign-in is a trusted device. Yahoo Finance needs no browser and no sign-in at all.

A Taipei (2330.TW) or Madrid listing charts nothing on thinkorswim, or shows "no name"

This is a documented limitation, not a bug: thinkorswim's name lookup only covers US listings. Those symbols need Yahoo — switch the provider (omacharts config set provider yahoo, or per-window from the command line with omacharts --provider yahoo).

Fix: Taiwan exchanges are searchable by ticker, English name, or Chinese name (台積電) and chart on Taipei's own trading hours via Yahoo.

omarchy pkg add omacharts reports the package is missing

New Omarchy packages land on the edge channel first and reach stable with the next Omarchy release train (the maintainer's README itself noted the package was "waiting to be merged" shortly before it landed).

Fix: If you're on stable and it's missing, either switch to edge temporarily or use the release tarball route from the GitHub releases page and sudo pacman -U the file.

A CLI command fails with exit code 6: "no window is open, so there is no focused chart to act on"

Expected behavior, not a bug: chart/chartbook commands that don't name a chart default to the focused one, which only exists while a window is open.

Fix: With nothing running, either launch the app or name the chart explicitly (--chart pos:1); pos:N is preferred over raw chart ids, which are reassigned when the layout rebuilds. (Documented in doc/cli.md; exit code 7 means the command hit an internal bug — worth reporting.)

Pairs well with / If you hate this, try

Pairs well with

• omacharts' own Omarchy bar plugin (ships with the app — the sparkline watchlist in your top bar). Your terminal + omacharts watchlist export for backups and machine sync. Anything you watch earnings on — the app charts, it doesn't tell you what to buy.

If you hate this, try

• TradingView in the browser if you need crypto/forex pairs, multi-device web sync, or Pine Script community indicators — it's the reference this app is chasing, minus the native feel. Or raw yfinance in Python if you want data, not charts, in a pipeline.

Comparison: omacharts vs TradingView vs thinkorswim desktop

Verdict: Use omacharts if you want a fast native charting window that lives in your Omarchy theme and doubles as a CLI; use TradingView if you trade crypto/forex or need cloud sync everywhere; use thinkorswim desktop if you actually place orders.

How to switch from TradingView (~10 minutes)

1. Export from TradingView: TradingView doesn't export watchlists as files directly — copy your ticker lists; strip exchange prefixes (NASDAQ: → plain tickers).
2. Import into omacharts: omacharts watchlist create Name && omacharts watchlist add Name $(tr -d '\r"' < export.txt | tr ',;' '\n\n' | grep -v '^[[:space:]]*#' | sed 's/.*://') — the maintainer's own doc/cli.md gives exactly this pipeline; bad tickers are reported and skipped, not silently dropped.
3. What doesn't transfer: Pine Script indicators, multi-timeframe alert scripts, and drawing annotations on specific bars — rebuild the indicators you rely on with omacharts' equivalents (RSI/MACD/Bollinger all present).
4. Time estimate: ~10 minutes to move watchlists; budget an evening to re-create complex indicator stacks.