Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion src/pages/docs/release-notes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ description: "Latest Future AGI release notes covering new features, improvement

- **Environment Chat Continues From Your Build:** A new environment's build now runs in the environment's own chat session, so the session that built the environment is the one that answers your chat, and messages you send during a build are taken up as it runs. Saving scenario changes from chat keeps the environment's scenario count in step, and a run keeps the scenarios it ran with.

- **Observability for Code Agents in Simulations:** When you create an environment from a repository or an upload, you can now tick "Turn on observability" to collect the traces your agent's own code sends during simulated runs. It is off by default, and the agent must already be instrumented with traceAI or OpenTelemetry. The environment always builds; if observability cannot be turned on, the environment page shows why. A code agent's Definition tab also has an observability switch, which view-only members cannot change. Each run of a code agent now has a Traces tab that lists the traces from that run, 20 per page, and opens each one in a read-only trace view; when observability is off, the tab says so and links to Enable observability. These simulated traces stay out of your Observe projects, and the MCP `get_trace` and `get_span` tools accept a `test_execution_id` or `call_execution_id` to open them.

<div class="mt-6 mb-3 text-lg font-semibold">Bugs/Improvements</div>

- **Gateway Tokens-Per-Minute Limits:** A tokens-per-minute limit set on a Gateway key or organization is now enforced, independently of the requests-per-minute limit, with the key's own limit taking precedence over the organization's. When it is reached the gateway answers 429 with an error code of its own, so a client can tell which budget it hit. A request's tokens are counted once the provider answers, so one request can cross the limit before the next is refused, and the limit is counted per gateway instance, so with several instances the effective ceiling is the configured value times the instance count.
Expand All @@ -35,6 +37,8 @@ description: "Latest Future AGI release notes covering new features, improvement

- **More Resilient Gateway Under Load:** A provider taken out of rotation by its circuit breaker is tried again after the cooldown, requests waiting on a Vertex token share one refresh attempt when Google's token service is failing, and a running gateway keeps an organization's last working configuration if an updated one cannot be built.

- **Realtime WebSocket Connections Through the Gateway:** Clients can open a WebSocket to `/v1/realtime` through the Gateway. The gateway sends your client a WebSocket ping every 30 seconds, so a client that answers pings (as standard WebSocket libraries do) stays connected while busy or idle, and the final messages a provider sends as it closes the connection are delivered to your client before the session ends.

- **Gateway Credential Handling:** The Gateway sends Gemini API keys in a request header rather than the URL, strips credentials from error messages and masks the Gemini key header in Request Logs, and never forwards the Gemini API key to a redirect target outside the configured origin.

- **Tool Calls in Chat Run Order:** In an environment run's chat call drawer, tool calls appear where they happened in the conversation, between the customer's turn and the agent's reply.
Expand All @@ -61,7 +65,7 @@ description: "Latest Future AGI release notes covering new features, improvement

</div>

{/* SKIPPED: internal-only changes with no customer-visible effect (speech routing for the simulated caller, internal settings, contributor tooling, eval definition consolidation, tests, CI and release bookkeeping). Held for confirmation: agent observability for code agents, live in one region only so far (see PR description). */}
{/* SKIPPED: internal-only changes with no customer-visible effect (speech routing for the simulated caller, internal settings, contributor tooling, eval definition consolidation, tests, CI and release bookkeeping). */}

## Week of 2026-10-12

Expand Down
Loading