Torus

Torus

Stock research memory for Claude Code, Claude Desktop and Codex. Torus gives Claude a memory for your equity research. Before it answers, Claude sees what you already know about a company: your theses, the sourced facts behind them, its suppliers, customers and competitors, and the ideas you ruled out. New research builds on the old, and every new fact is saved with its source. When a new SEC filing or news story threatens a thesis, Torus warns you: on your desktop as it happens, and in a daily or weekly digest by email, Slack, Discord or ntfy.

Ask Claude *"Is NVIDIA still supply-bound?"* and it starts from what you already concluded, not from scratch. Torus keeps:

• the companies you cover and how they connect: suppliers, customers, competitors
• claims about them, each tied to its source (a 10-K, an earnings call, an article)
• your investment theses: bullish or bearish, the claims they rest on, and what would break them
• ideas you ruled out, so you don't research them again

When a 10-K, 10-Q, 8-K or news item lands, Torus works out which of your theses it touches, through which supplier or customer link, and how much it matters. It also keeps the research honest (what's gone stale, what rests on one source, what a skeptic would say) and tracks how your calls did against the market.

Built for analysts, portfolio managers and serious individual investors.

• Your model, your subscription. Torus never calls an LLM itself. Claude does the reasoning, and cheaper Haiku subagents do the bookkeeping.
• Local-first. Your research stays in one SQLite file under ~/.torus (override with TORUS_HOME).
• Time-aware. Every fact records when it was true and when you believed it, so you can ask what you thought on any past date. Nothing is deleted: corrections are new versions.

*Torus is a research memory, not financial advice.* See CHANGELOG.md for what's in each release.

Pick your app

Torus works in three apps. All of them share one graph on your machine, so you can research in one and pick up in another.

Claude Desktop

pip install torus-kg

torus setup

The package is called torus-kg on PyPI; the command it installs is torus. torus setup asks for the email the SEC requires, downloads the SEC ticker list, adds Torus to Claude Desktop's settings (it keeps a .bak copy and leaves your other servers alone), and schedules the filing watchers. Restart Claude Desktop, then try the Onboard companies prompt from the "+" menu with a few tickers.

Codex

The same two commands. torus setup adds [mcp_servers.torus] to ~/.codex/config.toml (or $CODEX_HOME) and installs the Torus skills (torus-research, torus-onboard, torus-review and so on) under ~/.codex/skills. If you already wrote a [mcp_servers.torus] entry yourself, setup leaves it as it is. Restart Codex, then ask it to onboard your tickers.

Claude Code

See Getting started below. torus setup also prints the two /plugin commands.

torus setup configures the apps it finds; pass --claude-desktop or --codex to configure one anyway, or --no-codex / --no-claude-desktop to skip one. torus doctor checks each app's entry and that the server starts, and torus doctor --fix repairs what it can.

Just looking? torus demo builds a small sample graph (NVIDIA, TSMC, Micron and AMD theses, an alert from a TSMC filing, the semis starter pack) in its own folder, TORUS_HOME/demo, and opens it in the explorer. Your own graph is untouched, and every piece of sample research is marked [demo].

How it works

Why this helps. Research done in chat is usually thrown away: the next session starts from scratch, and nothing connects new information to what you already concluded. Torus keeps the working parts of the research, not just the final report:

Getting started (about 5 minutes)

You need Python 3.11+ and Claude Code.

1. Install the `torus` command. The plugin's hooks and MCP server run it, so this step is required:

pip install torus-kg

2. Set it up:

torus init --refresh-reference --contact you@example.com   # SEC ticker list (the SEC asks for an email)

torus config set sec_contact you@example.com # used when reading and watching filings torus doctor # check that everything is in order

3. Add the plugin in Claude Code:

/plugin marketplace add sekhar14/torus

/plugin install torus@torus

You'll be asked for a capture mode:

4. Tell Torus what you cover (recommended). In Claude Code:

/torus:onboard NVDA AMD TSM AVGO

or from a portfolio or watchlist export: torus onboard --file portfolio.csv (any CSV with a ticker or symbol column), then /torus:onboard to finish the mapping. Torus adds the companies, watches their SEC filings, suggests matching starter packs, and a Haiku subagent maps each company's suppliers, customers, competitors and customer concentration from its latest annual report, citing the filing.

5. Keep the watchers running:

torus schedule install    # checks filings, news and prices every hour

This uses Task Scheduler on Windows, launchd on macOS and cron on Linux.

6. Research as usual, e.g. *"Is NVIDIA still supply-bound? Check TSMC's CoWoS plans."* The next time you mention NVIDIA, Claude sees the earlier thesis, claims and ruled-out ideas before it starts. After each turn Torus tells you what it recorded (*"Torus recorded 1 thesis, 3 claims and 2 sources this turn"*), and /torus:undo reverts anything you don't want.

What you can ask

You don't need to remember commands; ask in plain words and Claude uses the right Torus tools.

Commands in Claude Code

Behind them, the MCP server gives Claude 45 tools, from brief, recall and record_claim to filing_diff, whatif, digest and scorecard. Claude Desktop and Codex see 33 of them by default (the analyst toolset): the queue and low-level graph tools are hidden. Se