Agent research desk · macOS · private beta
Run a fund the size of one person.
Finexia is a desk of specialist AI agents on your Mac, for independent traders, analysts, family offices, business angels and emerging managers. Ask a question in your own words: Kam hands it to the roles it needs, each works in its own terminal, and the desk returns an argued thesis — with a workbook, a deck and a memo, every figure tied to a dated source.
- Your model subscriptionsFinexia drives the Claude Code, Codex or Gemini CLI you already pay for. It resells no model.
- Your machineKeys stay in the macOS Keychain. Our server never sees your market data, notes or theses.
- Theses, never ordersNo write path to any broker. You adopt a thesis; nothing is ever executed for you.
This is the desk. Not a picture of one.
8 chapters of a run that actually happened, replayed from the files it left behind.
- A real terminal per cardEach card drives a provider CLI, headless, in its own workspace. The raw output stays one click away.
- A trace, never a summaryEvery line is an event from the process — a phase, a tool, a card that settled.
- Budget before workThe run is capped before the first process starts, and sub-agents inherit the cap.
- What can be launched
- And what it may call
- Nothing is wired by default
KamThe CLIs are read from PATH, not declared. Three answer today.
the runquerying
Analyse AAPL sur un an en journalier. Fais travailler News et Execution. Affiche sur le canvas les dépêches sourcées et le chart AAPL avec une SMA 50.
fundamental ← « analyse » · execution ← « execution » · news ← « news »
- Kamquerying
Finexia OS 0.0.30 (c7f1485) · interface captured 2026-09-11 · recorded run replayed with its original provenance (2026-08-26)Finexia-OS/src-tauri/src/providers/fixtures/plan.json · essaim-run.jsonl
Where the desk is going. Nothing moves under your eyes.
The Mission Workspace is the desk’s next surface: Work, Deliverables, Sources and Activity in one panel that scrolls and never pans. In the app today it opens full width — the conversation with Kam still lives on the desk above.
bench chronicle · 0.0.31 lines come from Finexia OS 0.0.31 proof bank · 8d23caa; narration is written by this page. Not a recording of a native session. In the app, the workspace does not carry the conversation yet: it lives on the desk.
Construis un dossier sur les segments d'Apple
idle
- 14:00demandedeskConstruis un dossier sur les segments d'Applefini
Step 1 of 8Ask narration A desk starts with a sentence, in your own words. Nothing runs yet. Opens Activity.← → to step
The desk stays with you.
See who is working, ask Kam a question, follow Bouna and stop the desk — without bringing the whole workspace back.
- A control, not a windowIt rests as a capsule, widens for one event, opens when you click it, and changes shape when the machine is being driven.
- Stop is never buriedWhatever the desk is doing, the control that ends it is one press away — not three screens deep.
- Interactive replayThe bar below is a reconstruction, not a screenshot: no bench asset shows the notch yet. Names and states come from the core registries, and the one figure it shows was measured under a named test rather than produced by an agent run. The deliverables capsule and Bouna’s companion window are drawn from the core’s code; nothing about a piloted session is claimed.
Kam, and up to three agents at work. Nothing else.The resting shape. It says who is working without asking for a glance, and it never carries a sentence — a bar that has to be read is a bar that interrupts.
How the notch works — permissions, a Mac without a cutout, accessibility, privacy14 mandates. One desk.
Named roles with a written remit, not one assistant wearing fifteen hats. Open a face: its mandate, the tools it may call, an example mission, what it hands back, and where it stops.
Tap or focus a face to read its mandate — Kam included. Click one to watch what it actually does.
- AVAILABLEA visual profileA name, a portrait or one of the owls, a hue and your appearance settings. Switching profile switches the screen.
- AVAILABLEA sector, named in the missionSay “biotech” or “semiconductors” in the sentence. The role whose mandate covers it finds the issuers — nothing to configure.
- PLANNEDA saved sector playbookKeeping a sector and a role selection with a profile, and reopening a desk from it, is not built yet.
One main role per mandate, never two of the same. A sub-agent is not a sixteenth face: it runs under its parent’s card, inherits its cap, and reports to it.
From a question to a thesis you can defend.
01
Ask
You write one command. Kam names the roles it needs and caps what the run may spend, before a single process starts.
- Models (7)
- Opus 5
- Opus 5 · 1M
- Sonnet 5
- Sonnet 5 · 1M
- Fable 5
- Fable 5 · 1M
- Haiku 4.5
- Effort
- low · medium · high · xhigh · max
- In the recorded pass
- exercised — a real request went through
fundamental ← « marge » · spend capped before the first process · 12 more providers described, adapter not written
The command bar — switch the provider and watch what the run would answer under. 02
Investigate
Each role opens a real provider CLI in its own isolated workspace and reports every phase as it happens.
LiviaFundamental
- readinganthropic
- readingopenai
- reasoninganthropic
- reasoningopenai
- writingopenai
- writinganthropic
listening · anthropic
The role that actually worked in the recorded pass, phase by phase, and what it spent. 03
Challenge
Risk can hold a card. A question the data cannot answer at that date comes back blocked, not approximated.
VeraRisk
What breaks this, and what have we not measured?
- readingReads the declared limits — it holds no portfolio of its own.
- checkingCounts how many simulated paths breach the limit, and how many were not run.
- reasoningNames the adverse scenario, and what the desk would have to accept.
- writingWrites the veto, or the condition under which it lifts.
- doneSays which reading is missing rather than filling the gap.
BLOCKEDThe refusal: the reading that is missing, and every source already tried for it.
Vera vetoes an adoption. It never reports a P&L, because the desk holds none.
A risk mandate running to its refusal — what is missing, and what was already tried. 04
Adopt
You adopt, or you do not. The thesis and its trail go to a local journal, and no write path to a broker exists.
- Liviaanthropic← « analyse »
- Miloanthropic← « execution »
- Inèsanthropic← « news »
chart · SMA 50
Nothing is adopted until you say so.
The plan the desk sealed, the word that triggered each card, and the two ways out.
INTERACTIVE PRODUCT RECONSTRUCTIONChoreography and timing are reconstructed. The commands, roles, providers and payloads shown come from the imported plans and fixtures. This scene is not proof of a native run. Sealed from Finexia OS 0.0.30 (c7f1485) · recorded 2026-09-11
Every conclusion keeps its trail.
A number without a source does not ship. Neither does a curve that quietly fills its own gaps.
- Point-in-time or blockedA question the data cannot answer at that date comes back blocked, not approximated.
- Gaps are countedWhat an indicator could not measure is left blank and counted in the legend, never interpolated.
- Freshness ages on screenA reading carries its age and crosses into a warning after a session.
Follow a figure to its source
- Level
- TESTED
- Where it came from
- Finexia-OS/docs/reports/RAPPORT-PASSATION-CHATGPT-2026-09-10-0.0.27-SEC-DOSSIER-BUNDLE.md §2 — la preuve SEC
- When it was established
- 2026-09-10
- Which build made it true
- 0.0.27 · source efdeaeb · product aa01163
- What it means
- Counted, not estimated. The figure the commit announced turned out to be exact.
What could not be measured
SMA 50 — 203 points measured, 49 not measured, left blank, never interpolated. A tool that fills its own gaps draws a smooth curve and a false one; this one counts them and writes it in the legend.
Adopt is not execute.
The agents research and argue. You adopt, or you refuse.
- 01 Adopting appends a thesis to your journal. It is reversible, and it is local.
- 02 Finexia sends no order. There is no broker write path in the codebase, and a machine guard keeps it that way.
- 03 A missing input produces BLOCKED — a first-class state that names what is missing, not a number that looks like an answer.
Your subscriptions. Your machine. Your record.
Finexia drives the provider CLIs you already pay for. It does not resell you a model, and it does not hold a key.
The registry, today
- Claude Code
claude - Codex CLI
codex - Gemini CLI
Finexia drives the CLI you installed, with your own subscription. No partnership is implied, and no key of yours ever leaves the keychain.
On your Mac
- Each card drives one CLI headless, in its own isolated workspace.
- Your keys in the macOS keychain — never in a file, a database or a log.
- Your journal, your theses, your deposits: on disk, append-only, replayable.
- Finance tools served to the agents by a local server on the loopback address.
On the server
- Your account, your licence, and app updates. That is the whole list.
- No market data, no journal, no portfolio, no thesis ever transits through it.
- Cut the server off and the app still works — every analysis path is local by construction.
- A machine guard checks the server’s schema, so the list cannot quietly grow.
The providers screen of the app — the CLIs it found on this machine. Sealed capture, replayed with its original provenance.
Roles declare what they may reach. No role holds both your data and open web access — and anything fetched from outside is treated as data, never as an instruction.
Drive the desk from the client you already have open.
A local MCP server exposes the desk over standard input and output. No port, no listener, nothing addressable from outside your machine — and a third-party client has already walked the whole path.
CLIENT-VERIFIEDOn 2026-09-10, Claude Code 2.1.265 connected to the local server, listed the 7 tools, called one, and received the 14 mandates the running application holds. That is a different claim from “our tests pass”.
The surface, today
finexia_agents_listList the specialist roles Finexia can put on a desk, with what each one owns.finexia_desk_startOpen a desk on a financial question.finexia_desk_statusWhere a mission stands: its roles, what each is doing, and whether anything is blocked.finexia_desk_resultWhat the desk concluded, with its sources.finexia_desk_cancelStop a mission and everything it started.finexia_artifacts_listThe files a mission produced — workbook, deck, memo — with their size, SHA-256 and the verdict of Finexia's independent re-read..finexia_artifact_getOne artifact: its structured summary, MIME type, size, SHA-256, sources, and a resource URI to read it.
4 prompts · 4 resources · 4 protocol revisions negotiated · standard input and output, no port, nothing reachable from outside the machine
Research and benchmarks. And what is still blank.
Measurements, evaluations and documentation live here. Where a page is not written yet, it says so and explains what it will carry — no article, no benchmark, and no customer, because there are none to show.
- Latest researchFinance intelligence researchWhat we are trying to find out, and why it is hard.Live on this page
- Tests and evaluationsEvaluations and benchmarksNumbers, with everything needed to argue with them.Live on this page
- Product notesProductWhat shipped, and what it replaces.Live on this page
0 of these are not written yet. Each one has a page that says what it will carry and how it will be established — no article, no author, no benchmark, and no customer, because there are none to show. The 8 families of the site are laid out in the menu above.