Skip to content

Core

Agent runtime efficiency and conversation progress

0.6.9

Reuses runtime calls and makes Agent response state and completion timing visible.

Added

  • Completed Agent replies show their local completion time beside elapsed duration. Correlated saved history restores timing from the existing task records; legacy or unresolved turns do not invent a completion time.
  • Active replies keep the current tool or execution stage visible outside the collapsed tool list, alongside elapsed time and signal freshness. Questions and approvals show input waiting instead of running activity.

Fixed

  • Saved Core and App forms acknowledge their persisted values before navigation, preventing a false unsaved-changes prompt. Subsequent edits still prompt.
  • Agent tables have individual copy controls that paste rows and columns into spreadsheets. Stopped replies preserve already received text when a saved checkpoint is shorter, and stale task updates no longer restart the stopped reply's progress display. Offline Stop still cannot guarantee server cancellation until its request reaches the server.

Upgrade required

  • Saved-form handling requires React SDK 0.6.5 and Core 0.6.9 together; Laravel SDK remains 0.6.4. The candidate adopts People 0.5.4, Payroll 0.4.5, Receivables 0.5.3, Time Absence 0.5.6, Assets 0.4.0-beta.6, Grants, Inventory, and Warehouse 0.4.0-beta.5, Product Engineering and Recruiting 0.4.0-beta.6, Procurement 0.4.0-beta.6, and Demand Planning 0.4.0-beta.9. Run the Central migration to add the missing billing foreign-key indexes.
  • Gateway callbacks reuse the lifespan HTTP client, and delegated requests reuse a transport without sharing per-user headers or cookies. Usage start uses one INSERT/RETURNING round trip while preserving duplicate-executor refusal. Effective tool policies use a bounded tenant/actor/scope/revision cache; server authorization and credit admission remain unchanged. Deploy matching Core/Gateway revision contracts together for policy-cache reuse. No new infrastructure or App adapters are required; production latency improvements still require measurement.