Open Trading SurfaceOpen Trading SurfaceOpen Trading Surface is being shaped by the people who use it. Report a bug, request a feature, share an idea, or just tell us how you work — all in the open.
Something wrong? Open a bug report with steps to reproduce and your version (from check_for_updates).
Rough ideas welcome — no full spec needed. Help steer where Open Trading Surface goes next.
Share an ideaAsk questions, swap workflows, and talk with other users in Discussions.
Open DiscussionsSee what's open, in progress, and resolved — every issue and its disposition is public.
View the issue trackerThe plugin ships capabilities; schedules are host-level — installing OTS does not by itself install recurring jobs. Run /ots:automate after installing: it reads the plugin's automation registry (the canonical list of every scheduled job OTS ships — currently the Opportunity Surface daily batch and the daily ledger & register recording) and walks your agent through creating the ones you choose as scheduled tasks on your machine. Registry-driven means future automations appear in /ots:automate automatically after an update. Every entry also carries a CLI/cron alternative for headless setups, and all automations are read-only over your configuration — they record and observe, never modify.
Every release ships a SHA-256 checksum so you can confirm your ots.plugin downloaded intact. Compare it against the published checksum:
# compare against download/ots.plugin.sha256
shasum -a 256 ots.pluginThis release is not GPG-signed — the checksum above is the only verification available for it. Signature verification applies to releases up to 5.61.3, which ship a detached .asc beside the package; every release after it ships a checksum only, because the signing key has not been present on the build machine since. A page that told you to check a signature that was never produced would be worse than one that admits the gap, so it is stated here rather than left to be discovered at the command line.
For a release that does carry a .asc, import the Open Trading Surface release signing key (fingerprint 4703 B1C3 57AD E3DA B29E D4F4 8EAF A2ED 2005 8E4B) or, for packages from the rebrand transition, the legacy Orrery key (fingerprint 7FB3 00D8 4247 9AF6 41C8 EEF9 911D 3894 8CBC 401B) — either key verifies a dual-signed package — and check the detached signature with GPG's verify command. When signing resumes, this section returns and the release pipeline says so on its own summary line.
This snapshot is illustrative; the live tracker is the source of truth.
| # | Title | Type | Status |
|---|---|---|---|
| — | Track the live tracker on GitHub for current items | info | open |
Ask the agent "check for updates" and it compares your installed build against this channel. Full history is on the changelog.
CLAUDE.md opens with it — six spec files carried SPEC ONLY for betweenSYSTEM-BROWSER-SPEC said "NOTHING BUILT" while 5.175.0 was shipping thetwo_statements. Two statements inside one class can disagree:panel_may_lag. The run already follows the class;panel_follows. The panel is read LIVE from the class, so async_back. The only kind that can be read back, becauseCategories above are derived from each note's wording, not hand-curated — read the note itself for the detail.
Open the terminal and click the ⚙ Settings tab. Paste your FMP key (and optionally a free FRED key) and hit Test. Keys are stored locally in ~/.ots/config.json (mode 600) and never transmitted anywhere but the data providers.
No. Open Trading Surface is an informational research tool. Nothing it produces is advice or a recommendation. Data and computations may be inaccurate — you must verify everything and you bear full responsibility for your decisions. See the disclaimer.
Ask the agent to check_for_updates, or watch the workspace cockpit — it flags new versions. Then download the new ots.plugin and add it under Customize → Plugins → Personal plugins, and restart the session. See the guide.
Never. It plans, models, and records — any transaction you enter is a bookkeeping entry only. It has no brokerage integration.
Financial Modeling Prep (markets & fundamentals), FRED (economic data), and SEC EDGAR (filings). You supply your own FMP and FRED keys.
Everything the terminal shows, the agent can read and drive — 230 introspectable tools spanning charting, screening, portfolios, the pricing engine and Model of Models, strategic-initiative books, the divergence ledger and rerating test, the market heat map and repricing scan, alerts/subscriptions/calendar, executive profiles, and the marketplace. It is plan-only: it never places a trade.
The 🛍 Marketplace tab installs images — shareable packs of reference data, authored model books, and configuration (the free OTS Starter Image bootstraps a fresh install). Every install is verified against the catalog's SHA-256 and recorded in a local provenance ledger; imported records carry their origin and never mix silently with your own history. Images contain no keys and no personal data.