Simulate your agents in an Environment: up to 1,000 realistic scenarios from one chat, then debug failures goal by goal
Build a simulation environment for your voice or chat agent from its GitHub repository, from uploaded code, or from a Vapi or Retell AI agent, then run it all from one chat: up to 1,000 scenarios with simulated users who sound like real people, scoring against each conversation's sub-goals and as many system or custom evals as you need, and a Debug failures view that shows which goals your agent broke and how. Also this fortnight: a deeper Error Feed that groups failures by their real defect, Claude-format requests routed to Gemini on Google Vertex AI, a lighter self-hosted setup with a signed Helm chart, and more.
Simulate your agents in an Environment
Build a simulation environment for your voice or chat agent from its GitHub repository, from uploaded code, or from an agent hosted on Vapi or Retell AI, then run the whole simulation from a single chat. Future AGI generates up to 1,000 scenarios with simulated users who sound and act like real people, and scores every conversation against its sub-goals and as many system or custom evals as you need. When conversations fail, click Debug failures: Future AGI reads every call in the run and shows which goals your agent broke, the different ways each goal broke, and the exact calls behind each one, so you know what to fix next.
A deeper Error Feed that finds the real defect
The Error Feed, which surfaces recurring problems in your deployed agents, now investigates each problem in depth instead of scanning each trace only once. It compares what the user asked for with what the agent actually did, backs every finding with evidence from the trace, and double-checks its conclusions before showing them. Related failures are grouped by their underlying defect, and each issue shows how often it happens, what it affects, how severe it is, and where to look for a fix.
Interruption counts and stop latency on every call
Call lists and run summaries now show how many times each call was interrupted and its stop latency, so you can compare conversation quality across calls without opening each one.
A more useful run page
You can stop a simulation run while it's in progress, from the runs table or the run page, and builds and runs show accurate in-between states such as Finalizing and Cancelling. A run's calls table can show each call's Situation, Sub-goals and Ideal outcome in their own columns (turn them on from Columns), and you can step to the previous or next call straight from the call drawer, for both voice and chat. The Runs tab lists every run of an environment, 10 per page, and the graph can plot your latest 1 to 5 runs.
An environment chat that keeps going
The environment chat now recovers on its own from brief platform interruptions, and stops with a clear error if a run's saved files are missing. Scenarios, contracts and sub-goals you add or edit in chat show up in the Scenarios tab and are used in the next calls.
Scenario edits carry into the next run
Editing or deleting a scenario in the Scenarios tab leaves every other scenario untouched, and your changes are used in the next run.
Call recording and transcript improvements
Transcript highlighting now stays in sync with the audio during playback, the agent's last words are kept when a call ends, outbound calls wait for someone to answer, and the simulated caller waits for a reply after asking a question.
Route Claude-format requests to Gemini on Google Vertex AI
The Gateway can now serve Claude-format requests, including those from the Claude Agent SDK, using Google's Gemini models on Vertex AI. Keep your Anthropic-style request code and run it against Gemini on Vertex AI through the Gateway.
Google Vertex AI as a Gateway provider
You can now add Google Vertex AI as a provider on the Gateway, with a deployment guide to help you set it up.
Gateway logs and analytics by application and service
Filter Request Logs, and group usage, cost and error analytics, by application and service as well as by provider and model. These values come from the metadata you attach to each request, for example an `x-agentcc-metadata` header with `application` and `service` fields.
Private model servers for self-hosted Gateways
On self-hosted installs, you can point the Gateway at local or private model servers such as Ollama or vLLM by turning on an explicit opt-in setting.
Provider keys stay with your organization's endpoint
On every Gateway, cloud or self-hosted, an organization's provider keys and requests are sent only to that organization's own configured endpoint. Gateway API keys created in the UI now also survive Gateway restarts.
OpenAI-compatible providers without a /v1 path
Providers whose endpoints don't use a `/v1` path, such as Perplexity, now work through the Gateway, because provider endpoint paths are now configurable and resolved consistently.
Gateway analytics and request handling refinements
Requests from an application labeled "Other" now keep their own group in grouped analytics, request schema properties are preserved, and resolved model aliases are passed on to the provider.
MCP server tools that always match the API
The Future AGI MCP server's tools for datasets, evaluations and observability are now generated directly from the platform's API, so their inputs and behavior always match what the API supports.
Falcon AI saves the dashboards you build in chat
Ask Falcon AI to build a dashboard in the general chat, and it now saves the dashboard for you.
Observe keeps up with large projects
On large projects, filtered lists of spans, traces, sessions and users, as well as dashboard graphs, now show the results found so far with an option to load more. Observe also recovers smoothly from brief connection drops, and the Voice calls list loads reliably in voice projects.
Consistent Users filters and latency charts
Filtering the Users list by fields such as status or model now returns the right users, latency charts show the same statistic with or without a filter, and the Users grid stays visible while it refreshes.
Error Feed stays responsive on large error clusters
The Error Feed stays responsive when you investigate very large clusters of related errors.
A lighter self-hosted Future AGI, plus a signed Helm chart
Self-hosting is now lightweight by default. A Standalone setup runs in 3 containers and uses about 1 GB of RAM when idle, a Distributed setup scales out for larger teams, and a signed Helm chart published to an OCI registry is available for Kubernetes, with production and enterprise options such as autoscaling, external secrets and air-gapped installs. Third-party integrations stay off until you add their keys.
Smoother self-hosted install and first-run setup
A fresh self-hosted install now takes you straight to creating the first account. If a first-run check fails, such as object storage or TLS, the setup screen explains why and how to fix it, and lets you continue in a test-flight mode or contact support. The backend also finishes in-progress requests before it shuts down during restarts and deploys.
A stable object storage build for self-hosting
Self-hosted deployments now use a fixed build of the last community release of MinIO, so object storage stays on a known, stable version.