Roadmap and Future Work

🗺️ Roadmap & Future Work

This page tracks what's actually shipped versus what's genuinely still open, cross-checked directly against the codebase rather than against any older marketing/presentation material — a couple of items that were once "planned" have since shipped and are listed here as done, not repeated as upcoming.

✅ Shipped

• Streaming chat responses. The agent renders LLM output token-by-token as it arrives, across all supported LLM backends — including while tool calls are happening mid-stream — rather than waiting for a complete response before showing anything.
• Two cascading market data providers (FMP primary, EODHD secondary) with automatic fallback, plus a fully synthetic simulation mode requiring no API keys at all.
• Six LLM backends: Ollama (local), Google Gemini, Anthropic Claude, OpenAI, MiniMax, and any OpenAI-compatible endpoint.
• Five asset classes: stocks, ETFs, futures, forex, and crypto.
• Portfolio management: FIFO lot tracking across six transaction types, realised/unrealised P&L, concentration analysis (HHI), rebalancing suggestions against a user-defined target allocation, benchmark comparison (alpha/beta), tax P&L (short/long-term gains), watchlists, and JSON/CSV export.
• 58 agent tools across calculation, portfolio, market data, technical indicators, time, news, and currency conversion.
• Encryption: credentials always, portfolios and chat sessions optionally (on by default for new setups) — see Security & Privacy.

🔜 Genuinely open (not started, or partially scaffolded)

• Price alerts. Threshold-based alerts per symbol, evaluated on demand when you open the app or a portfolio view — not a background daemon or cron job (see the deliberate non-goal below).
• CSV import from broker statements. Today, adding a position is manual — either through the portfolio TUI wizard or by asking the agent (see Using the Agent). Planned support is a generic symbol/quantity/price/date CSV format with per-broker column mappings, not a live brokerage API integration.
• Consolidated multi-portfolio view. A single dashboard summarising metrics across all of a user's portfolios at once, rather than viewing one at a time.
• Simple backtesting. Running a strategy or allocation against historical data to see how it would have performed.
• On-demand news digest. The underlying data structures already exist in pkg/news, but there's no UI to trigger or display a digest yet.
• Scrollable long lists in the portfolio and instrument screens, for portfolios or watchlists that outgrow a single screen.

💭 Aspirational (mentioned, no code exists yet)

• Live order execution via a broker API. The driver pattern that makes adding a new market-data provider straightforward would extend naturally to a broker's trading API, but this is currently just an architectural observation, not planned work — there's no driver package, stub, or interface for it anywhere in the codebase. Worth distinguishing clearly from CSV import above: importing a statement to record trades you already made is on the near-term list; placing live trades through Auris is not.

🚫 Deliberate non-goals

• No background processes. Everything in Auris — including future alerts — evaluates on demand, when you open the app or a specific view. There's no daemon, no cron job, nothing running when the app isn't. This is a stated design constraint, not a limitation waiting to be lifted.

---

Have a feature request that isn't listed here? Open an issue — see Contributing if you'd like to build it yourself.