Skip to content
Open
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
2 changes: 1 addition & 1 deletion src/pages/docs/release-notes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ 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.
- **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. If observability cannot be turned on, the environment still builds without it, and when it could not be turned on during the build, the environment page shows why. A code agent's Definition tab also has an observability switch, which view-only members cannot change. Open any call in a run, and its Traces tab lists the traces your agent sent during that call and opens each one in a read-only trace view; a call with no traces shows "No trace for this call". 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` alongside the trace or span ID to open them.

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

Expand Down
Loading