Jul 30, 2026

API Key Auth for MCP, Budgets in Mission Control, and Automatic Case Files

The last stretch of July leans towards the plumbing that keeps V7 Go connected to everything else. MCP connections can authenticate with an API key, images and PDFs now go through the same vision path, and nothing a run produces gets lost on the way out.

MCP and integrations

  • API key authentication for MCP: MCP connections can authenticate with an API key. This helps where OAuth is impractical, such as a service account or a headless deployment.

  • MCP OAuth discovery to spec: OAuth metadata is discovered in the order the MCP specification requires, so compliant services connect on the first attempt.

Documents and files

  • One vision path for images and PDFs: Image crops and PDF pages run through the same vision processing. Results stay consistent across both, so you do not need to prepare a scan differently from a photo.

  • Automatic case files: Files a run creates are saved as case files when the run finishes. Nothing has to be rescued by hand from a completed run.

  • Artifact links become file cards: An artifact path containing a space or ending in punctuation renders as a file card instead of plain text.

  • Clear out stuck library files: Delete library files that got stuck while processing. A blocked upload is now something you can clear yourself rather than a support ticket.

Budgets and reports

  • Budgets in Mission Control: View and manage budgets from Mission Control, next to the work the spend belongs to. Budgets themselves shipped on 14 July; this is where they now live.

  • Reports across workspaces: Mission Control reporting runs on the multi-workspace API, so a report can cover more than the workspace you happen to be in.

  • Longer report date ranges: Mission Control reports accept extended date ranges. A quarter of activity fits in one report instead of three stitched together.

Sessions

  • Cleaner session expiry: An expired session now ends in a consistent sign-in prompt. You get a way back in rather than an error screen from whichever feature noticed first.

Precision AI for Institutional Workflows

Build once.
Deploy across teams.
Improve over time.

Precision AI for Institutional Workflows

Build once.
Deploy across teams.
Improve over time.

Precision AI for Institutional Workflows

Build once.
Deploy across teams.
Improve over time.