Skip to content
SynthBoard

What’s new

Changelog

What changed in SynthBoard, newest first — the app, the REST API and the MCP server. API versioning rules live in API versioning. Subscribe via RSS

major

Your Chief of Staff is the front door

  • One thread, with her. Home is now a single thread with your Chief of Staff. She keeps what you tell her on file — work and personal in separate contexts, each fact yours to correct or wipe — answers the everyday herself, and knows when a call needs an expert. Talking to her costs nothing.
  • Priced rooms. When a call needs judgment she hands you a card: one named expert for a consult, or a board for the biggest calls, with the time and the price on the card. Nothing runs until you tap it. When the room lands she brings it back in a few sentences — the call, the one caution, the first move — and the first move becomes a commitment with a date.
  • Asks inside a room. A follow-up for a consult you already have goes to the same expert, inside that consult, as a small priced card you confirm. No new room, and she will not open one to explain a room that already ran.
  • The Notion errand. Ask her to go over your Notion: she reads what changed, says what she read, prices only the part that needs an expert, brings the answer back, and prepares a new Notion page marked “Needs your review” that lands only when you confirm. Writes into your tools are on Pro and above.
  • Fresh start and setup. Clear what is on file in one step, with a 24-hour undo (a tool you disconnect stays disconnected). Then a short setup panel: who you are, what to keep apart, what you are in the middle of, where your work lives.
  • Many experts in one consult. Bring a second expert into a consult and they read the conversation so far. Ask one or several at once; they work in parallel.
  • Expand. A room opens beside the thread, expands in place to full size, and closes back to where you were.
  • The new site. synthboard.ai is rebuilt around one claim — one place for your business, your life, and every hard call — with a product tour, pricing that shows what each plan changes, and these docs rewritten for the Chief of Staff.
major

API sessions run the full board engine

  • Sessions started over the REST API and MCP now run the same engine as the web app: an express intake turns your question into a decision brief, the brief staffs the board, the board researches and debates, and the run terminates in a decision memo (verdict, confidence, conditions, dissent) or a shaped artifact. New response fields on session reads: session_type, v4_phase, decision_brief, memo, board_artifact.
  • The Consult over the API. Create a 1-on-1 session with a named expert via session_type: "consult" + synth_id; drive turns with the MCP tool synthboard.consult.message — each turn returns the expert's reply and any composed document, billed per turn.
  • Reconvene. New MCP tool synthboard.session.reconvene — reconvene a completed board as Round N+1 when something changed. Opens from the delivered verdict plus whats_changed, re-briefs, and runs. session.continue on a current board returns invalid_session_state pointing here.
  • 13 new REST endpoints: session archive, fork, metadata PATCH, mid-session update, live-summary, cross-round, assistant, bookmarks, decisions, action execute + undo, share revoke, and share password verification — plus webhook subscription CRUD and delivery logs. Spec bumped to 2.0.0 at /api/v1/openapi.json.
  • Webhook events now cover the full lifecycle: session.complete, session.failed, session.cancelled, session.continued, outcomes.ready — fired natively by the engine for API-started sessions.
  • Resilience. Model calls now run on provider fallback chains with circuit breakers — a session completes even when an upstream model provider degrades mid-run. Failed runs auto-refund undelivered work.
  • MCP surface: new resource synthboard://session/{id}/memo (the terminal deliverable alone), a /synthboard-consult prompt, and account/recent resources now report the engine and available session types.