New updates and improvements about V7 Go

PDFs open faster, which shows most on the long ones. Resources can be downloaded or opened full screen from the viewer, and any email alias linked to your account will sign you in to it.

Documents

• Faster PDFs: PDFs load and render more quickly. The difference is largest on long documents.

• Resource viewer controls: Download a resource or open it full screen from the viewer.

• Hub files open on click: Click a row in a hub to open the file.

Access and interface

• Sign in with an email alias: Any email alias linked to your account signs you in to the right account, which helps where people carry more than one work address.

• Report filters as pills: Report filters use pill controls and region selection is a single choice.

• Consistent controls: Segmented controls, tabs, and navigation lists share one visual treatment across the product.

Reporting timeframes resolve in a timezone you choose, which matters once a team is spread across regions. Property groups stay with a workflow when you move it somewhere else, and sampling a collection is much faster than it was.

Reporting and cost

• Timezone-aware reports: Pick a timezone in the report filters and see timeframes resolved in it. Reports line up with local dates and business hours.

• More accurate chat costs: Chat cost is summed from actual token usage, so the number you review is the number you are charged for.

Workflows and collections

• Portable property groups: Property groups stay intact when you move or share a workflow between environments, so there is less to rebuild after an import.

• Faster collection previews: Sampling a collection loads much faster, which shows most on large ones.

• Stuck uploads fail cleanly: An upload that gets stuck fails clearly rather than hanging while the project waits on it.

Administration

• Delete unused organizations: Admins can remove an organization they no longer need without a support request.

• Workspace ownership stays visible: A mapped workspace still shows the organization that owns it.

Chat and documents

• File previews from chat: Click a file reference in chat to preview it in place, without losing the conversation.

• Expandable JSON lists: A truncated list expands from its "and N more" summary, and large previews stay capped at a readable size.

• Favorites in a collapsed sidebar: Favorites stay reachable when the sidebar is collapsed.

• Clearer model errors: When a provider rejects a model, the error names the model instead of leaving you to work it out.

Ask user question is on for everyone now, so a workflow can stop and collect input without any setup first. Documents open in readable JSON by default, and the citations inside them point where they should.

Workflows

• Questions available to everyone: Ask user question no longer needs enabling. Any workflow can pause and collect human input where it needs it.

Reading and evidence

• Readable JSON by default: Documents open in a readable JSON view, and citation links inside them render and resolve correctly.

• Citations in the right place: JSON output places citations on the fields they belong to instead of repeating them across nested keys.

• Grounding survives dotted field names: Source grounding stays intact when your data contains dotted field names, and searches referencing those fields run correctly.

Reporting

• Reporting respects permissions: Reporting analytics honour workspace and report permissions, including when a filter names a workspace outside your scope.

• Chats report summary: The Chats report opens with summary cards carrying the key numbers.

• Budgets scoped to the workspace: The overview budget card shows the budget for the workspace you are actually in.

Terra is the model workflows use now unless you pick another one. Source deletion finishes cleanly even when something interrupts it, and a bad property schema tells you what is wrong instead of failing quietly.

Models and extraction

• Terra by default: AI workflows use Terra unless you choose otherwise. You get the current model without changing any settings.

• More consistent date extraction: Dates pulled from documents and inputs resolve more consistently, so fewer extracted periods come back incomplete or wrongly normalised.

Sources and citations

• Reliable source deletion: Deleting a source completes cleanly, even if something interrupts it. You can retry safely without duplicate work or broken references left behind.

• Citations that land on the right file: A citation from a collection file opens the source it belongs to, in the right subproject.

• Grounding stays with the project: An uploaded input keeps its link to the right project even when its name is adjusted behind the scenes.

Properties and interface

• Property schema errors you can act on: An invalid property schema returns a clear error naming what is wrong.

• Number properties lose the New badge: The number property type is treated as a standard part of the workspace.

• Cleaner Mission Control cards: Metrics sit in more consistent cards, so the numbers are easier to read at a glance.

• Favorites sidebar: The favorites scrollbar lines up with the sidebar edge.

Case responses can now be rated, and a rating you regret can be changed. Model usage has moved into Mission Control, workspace reports keep their history, and there is a new icon set across the app.

Feedback on cases

• Case response ratings: Rate a case response directly in the product. There is an API for rating case messages too, so scores can feed whatever you already use to track quality.

• Ratings you can change: Change a rating after you have submitted it. A misclick or a second look no longer means the score is stuck.

Usage and reporting

• Model usage in Mission Control: Model usage appears in Mission Control, next to the rest of your workspace activity. One fewer page to open to answer which model is doing the work.

• Workspace report snapshots: Workspace reports keep historical snapshots of their dimension breakdowns. You can see how a number moved rather than only what it is today.

• Updated Luna and Terra pricing: Pricing for the OpenAI Luna and Terra models now reflects current rates, so cost estimates and usage reporting line up with what you are actually charged.

Interface

• A refreshed icon set: A bespoke duotone icon set runs across the app. The interface reads more consistently, and the common actions are easier to pick out.

• Chat connection dropdown fixed: The chat configuration page stays responsive when you open the connection dropdown. It used to freeze there.

You can now favorite any workflow or chat and get back to it in one click. Hit the star on a card to add it, and it appears in the Favorites section of the left navigation alongside everything else you have starred.

What they are useful for

• Recurring work: star the workflows you run on a cadence, like a weekly reconciliation or a monthly report, so you are not searching for the same one every time.

• Picking up where you left off: star a chat and return to that exact session later. The context is already there, so a similar task continues in the same thread instead of starting cold.

• Bookmarking a working setup: when a workflow is configured the way you want it, star it. It becomes the version you come back to and adapt, rather than one you rebuild.

Favorites are per user, so starring something does not change what your teammates see in their own navigation. Add and remove them as often as you like.

Workflow properties keep a version history now. There is an inspector to compare two versions and preview what a restore will do before you apply it, so rolling back is no longer a guess.

Versions and history

• Workflow property versions: Workflow properties keep a version history. You can see how a property changed over time instead of guessing which edit broke a run.

• Version inspector: Compare two versions side by side and preview what a restore will do before you apply it. Labels in the navigation rail are clearer, so you can tell which version you are looking at.

Reporting and calculations

• Hourly usage reporting: Usage data breaks down by the hour, and transformation progress appears in reporting. This is rolling out to selected organisations first, so it may not be switched on for you yet.

• Calculations that recover: A calculation that hits a database error resumes instead of failing. Long-running work continues rather than restarting from the top.

Stability

• Structured search stability: Searches that use JSON schema validation complete instead of crashing. You can keep narrowing a search without losing your place.

• Property changes apply immediately: A change to a property's JSON configuration is detected properly. No more cached configuration quietly overriding what you just set.

Interface

• Overview columns stay put: Your column choices in Overview survive a page reload. Set the table up once and come back to the same view.

• Refreshed date picker: The date picker matches the current design across the product. Scanning a calendar and choosing a date is a cleaner job than it was.

• Custom MCP connector badges: Status badges in the custom MCP connectors table size correctly, so the table scans evenly.

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.

Two new Gemini models, a better answer to "where did our tokens go", and one fewer reason to email support: organization admins can change their own settings now.

Models

• Gemini 3.6 Flash and Gemini 3.5 Flash Lite: Both are available for extraction and AI work. Flash Lite is the cheaper choice when the task is simple and the volume is high.

Cost and usage

• Token usage by dimension: Group token usage by the dimensions your team cares about instead of reading a single workspace total.

• Cost attribution for extraction and calculation: Usage detail shows which work created which cost, so an expensive extraction is traceable to the thing that ran it.

• Usage stats in Mission Control: Activity and key numbers appear in the Mission Control overview, rather than on a separate page.

• Reports that reflect reality: Reports show live deletion status and budget detail in the results, so you are not cross-checking against something else.

Administration

• Organization settings, self-serve: Organization admins manage their own settings without a support request. Workspace mappings and reporting access stay consistent across regions.

• Property history and restore: View a property's previous configurations and restore one when a change turns out to be a mistake.

• Email replies per workspace: Set how email replies behave for each workspace instead of applying one rule everywhere.

Fixes

• Citation highlights on scans: Citation highlights line up correctly on scanned PDFs and image-only documents, where there is no text layer to anchor to.

• Delete property dialog: The dialog shows its full warning and buttons. You can read what you are about to delete before you confirm it.

Reports have a dedicated overview, admins have finer control over who can see them, and runs now stop themselves before they get expensive.

Reporting

• Reports Overview: A dedicated section for reporting, so there is a place to start rather than a set of separate pages to hunt through.

• One report across workspaces: Generate a single consolidated report covering several workspaces in the same region, instead of pulling exports and joining them by hand.

• Sortable workflow reports: Sort, filter, and page through workflow detail reports. This matters once a report runs to thousands of rows.

• Report access at organization level: Admins can grant reporting visibility to specific people rather than opening it to everyone.

Cost and limits

• Run limits: A run stops before it runs too long or consumes too much. A misconfigured loop now costs you minutes.

• Chats stop at the billing limit: Once a workspace reaches its billing limit, chats stop. The limit is now actually a limit.

• Calculations that finish under load: Calculated fields complete when many updates land at once, instead of sticking half-done.

Reading and review

• PDF citations out of the way: Citation markers on a PDF no longer cover the text underneath.

• One source's markers at a time: Select a source and only that source's citation markers stay visible. Everything else steps back.

• Code blocks left alone: A code block in chat stays exactly as written. No more "Unknown item" pills appearing inside a snippet.

A case can now stop and ask you a question mid-run rather than guessing at the answer. GPT-5.6 joins the model picker, favorites move into the sidebar, and citations point at the right text.

Models

• GPT-5.6: Pick GPT-5.6 from the model picker when you set up a chat or a task. Prompt caching works correctly with it, so responses come back without the loading stalls the first builds had.

Cases and workflows

• Questions inside cases: A case can pause and ask you for input before it continues. Required questions stay in front of you until they are answered, so a run does not proceed on a guess.

• Field recovery: A project with recalculation switched off can recover fields that never finished computing. No manual repair, no blank column.

• Folder sync controls: Turn sync on or off for one folder at a time instead of all or nothing.

• Required integrations, connected in place: When a workflow needs an integration you have not connected yet, you can connect it without leaving what you were doing.

Evidence and citations

• More accurate citations: Citations match the source text more precisely, including text inside web pages. The stray anchor text, extra blank lines, and misplaced highlights are gone.

• Citations in generated artifacts: A generated page carries its citations in the content, so you can check a figure without reopening the source pile.

Reporting and scripts

• Favorites sidebar: Favorites live in the sidebar, persist across sessions, and can be added from context menus. There is a documented API for them too.

• Python scripts that take input: A Python run can accept input while it runs, so scripts that prompt for a value or read pasted data work as written.

• Workspace usage reports: Token usage reports name the workspace on every row. Admins stop stitching per-workspace exports together.

Documents you keep in Google Drive no longer need a round trip through your downloads folder. There is a native picker now. Extraction got faster too, and every run reports what it cost.

Getting documents in

• Google Drive picker: Pick files straight from Drive with a native picker. No downloading and re-uploading to get a document into Go.

• Faster extraction: Documents process faster during extraction. The difference shows most on large batches.

• Extraction that matches your structure: Extraction results follow the data structure you defined more closely, which makes outputs easier to compare and review.

Models and runs

• Claude Sonnet 5: Available in the model picker for chats and ad-hoc tasks where you want stronger reasoning.

• Token and cost tracking per run: Every run reports its token usage and cost. You can see which work is expensive before the invoice tells you.

• Warnings when an answer is cut short: If a response hits the output limit, you are told. A truncated answer used to look like a finished one.

• Long runs that finish: Runs no longer crash when a model reaches its token limit mid-action. Long tasks fail cleanly instead of dropping everything.

Review and status

• Live queue status: Queue state updates as work starts moving, with no page refresh.

• Cleaner evidence highlights: Source highlights no longer stack duplicate boxes around the same passage.

• Python results render: Output from a Python run displays correctly when the run returns files.

Budgets are now available to every workspace. Set spend limits on AI activity, watch consumption in real time, and stop runaway costs before they happen — all from Settings → Budgets.

Two levels of control

Workspace budgets cap total spend across all Go activity. Agent budgets set per-agent limits scoped to a specific workflow, each with its own live tracking — so one heavy agent can have a tighter leash than the rest.

Dollars or tokens

Every limit and progress bar can be viewed in dollars or in tokens. Dollars is usually the easier number to reason about — you set a cap of $5,000, not a count of tokens — but the token view is there when model consumption is what you care about.

Periods and overrides

Choose a reset cadence of daily, weekly, or monthly. Each period must be unique per policy, but you can stack several on the same agent — a daily and a weekly cap together, for layered protection. A default limit refreshes automatically each period; a current-period override adjusts spend just once, without changing the standing default.

Tracking and alerts

A live progress and a widget in each agent view show current spend, the limit, and the reset date at a glance. Email alerts fire automatically at 75%, 90%, and 100% of a budget, and full spend reporting lives in Reports.

Reports now go down to the level of a single chat. Alongside the existing agent and user views, you can see exactly what each conversation cost — in tokens and in dollars.

For any chat, you get its token spend and dollar value, a breakdown of which models were used, and whether any Go agents were triggered during the conversation. An expensive chat is no longer buried inside a workspace total — you can see which conversations are driving cost, and why.

Open Reports in the left navigation and select the Chats view. The functionality is available to workspace administrators.

Agent memory lets you teach V7 Go how you like to work. Write your standing instructions once and Go carries them into every chat, so you stop re-explaining the same preferences at the top of each conversation.

It works like a set of house rules that sit behind your prompts. Anything that is true for most of your work belongs here: the register you write in, the way you want answers structured, the checks Go should run before it commits to an output, or the details it should always ask for.

Keep it short and specific. A handful of clear rules works better than a long wish list. Open Settings → Agent memory, write your guidance, and save.

V7 Go is now available as an MCP server. Connect it to Claude, ChatGPT, or any MCP-compatible assistant, and you can run Go straight from the chat window without switching back to the Go UI. This is the reverse of connecting tools into Go: here your assistant becomes a front end to Go itself.

What you can do from chat

• Inspect and query workflows: pull rows and entities, run queries over workflow data, and read definitions to answer questions like “what did this run output?”

• Run workflows: kick off Go runs from chat, including ones that take file inputs.

• Build and edit workflows: add and update properties, including computed and agentic ones, configure views with filters and sorts, and set up triggers, all conversationally.

• Query a Context Graph: ingest documents into a Context Graph and ask questions in natural language.

Connecting

You authenticate with your V7 Go login over OAuth when you connect. Each assistant configures MCP servers a little differently. In Claude, open Settings → Connectors → Add custom connector.

Endpoints

Pick the one that matches your account’s region:

• EU / standard: https://mcp.go.v7labs.com

• US: https://mcp.go.us.v7labs.com