From 601b8b1419b3f930ac649d47cd60be8936d923ad Mon Sep 17 00:00:00 2001 From: Kishore Kumar Date: Mon, 26 Oct 2026 16:39:33 +0530 Subject: [PATCH 1/2] docs: explain saved fleet models and chat controls --- changelog.mdx | 19 +++++++++++++++++++ fleets/authoring.mdx | 4 ++-- fleets/running.mdx | 10 +++++++++- 3 files changed, 30 insertions(+), 3 deletions(-) diff --git a/changelog.mdx b/changelog.mdx index a8524aa..d01bd40 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -7,6 +7,25 @@ description: "Product changes and upgrade notes." agentsfleet is in **stealth-mode testing** and pre-production. APIs and agent behavior may change between releases without long deprecation windows. Email [agentsfleet@agentmail.to](mailto:agentsfleet@agentmail.to) if you want a hand calibrating an agent or to join as a design partner. + + ## Choose the model for future fleet runs + + Choose a model in fleet chat to save it for future chat, webhook and scheduled runs. + + ## What's new + + - **Models** — confirmed changes appear in **Chat** and **Activity**. Saving keeps unsent messages and private setup edits. + + ## API reference + + - **Fleet responses** — `needs_re_review` is removed. Current readiness checks remain; catalogue changes no longer require another review. + + ## Bug fixes + + - **Chat** — replies finish without replacing their text. **Run details** opens compact usage and duration details. + - **Setup** — **Save changes** appears in the fleet header while you edit setup. + + ## Continue long conversations and review your spending diff --git a/fleets/authoring.mdx b/fleets/authoring.mdx index 080adb1..12fc3ab 100644 --- a/fleets/authoring.mdx +++ b/fleets/authoring.mdx @@ -3,7 +3,7 @@ title: Author a fleet description: Describe a fleet in a private chat, check its setup, and save it. type: how-to audience: user -verified: 2026-10-23 +verified: 2026-10-26 product_version: 0.65.0 executable: false --- @@ -54,7 +54,7 @@ Keep unfinished setup steps and schedule registration warnings in view. Use the To change a saved fleet, choose **Edit setup** in its header. A private chat opens beside the fleet conversation, based on its saved setup revision. On a phone, the editor fills the page. -Describe the change, review it through **Edit instructions manually**, then choose **Save changes** in the setup footer. +Describe the change, review it through **Edit instructions manually**, then choose **Save changes** in the fleet header. Your unsent message in the fleet conversation stays in place. New work uses the updated instructions; work already running keeps its current version. diff --git a/fleets/running.mdx b/fleets/running.mdx index 4c09735..b116fbb 100644 --- a/fleets/running.mdx +++ b/fleets/running.mdx @@ -3,7 +3,7 @@ title: Run and control a fleet description: Inspect, message, stop, resume, kill, and delete a fleet. type: how-to audience: user -verified: 2026-10-23 +verified: 2026-10-26 product_version: 0.65.0 executable: false --- @@ -67,6 +67,12 @@ Install a fleet. Copy its identifier from `agentsfleet list`. If you scroll back, a turn someone else sends does not move you. Click **Jump to latest** to follow it. + To change the fleet's model, choose a model in the chat composer. The saved choice applies to future chat, webhook and scheduled runs. + + Saving keeps your unsent message and private setup edits. **Model changed** appears in **Chat** and **Activity** after the save. + + Choose **Run details** to open usage and duration details. Press **Escape** or click outside the details to close them. + 4. Stop new work while keeping the fleet resumable. In the dashboard, open the fleet header’s **… → Stop** and confirm. ```bash @@ -119,6 +125,8 @@ For API lifecycle updates, send the strong entity tag (ETag) from the fleet body `UZ-AGT-012` means the fleet cannot accept a message in its current state. Resolve the cause or resume a stopped fleet. +If a model save fails, the composer keeps the last saved choice. Choose **Retry** for an unconfirmed save, **Reload choices** to refresh available models, or **Reload fleet** when another save changed the setup. + A run with no reply may be waiting for approval. Run `agentsfleet approvals list` to review the request. A message with no answer after 30 seconds reads **Couldn't confirm this message was sent.** Click **Resend**. It carries the same `operation_id`, so the fleet runs the message once. From f7cf33c8f115773198193ce017d409f663ea0b81 Mon Sep 17 00:00:00 2001 From: Kishore Kumar Date: Mon, 26 Oct 2026 16:57:42 +0530 Subject: [PATCH 2/2] docs: correct setup save locations and API upgrade guidance --- changelog.mdx | 6 +++++- fleets/approvals.mdx | 2 +- fleets/slack.mdx | 2 +- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/changelog.mdx b/changelog.mdx index d01bd40..092e012 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -12,13 +12,17 @@ description: "Product changes and upgrade notes." Choose a model in fleet chat to save it for future chat, webhook and scheduled runs. + ## Upgrading + + Fleet responses no longer include `needs_re_review`. Remove checks for that field from API clients. The CLI and server can upgrade separately. + ## What's new - **Models** — confirmed changes appear in **Chat** and **Activity**. Saving keeps unsent messages and private setup edits. ## API reference - - **Fleet responses** — `needs_re_review` is removed. Current readiness checks remain; catalogue changes no longer require another review. + - **Fleet responses** — current readiness checks remain; catalogue changes no longer require another review. ## Bug fixes diff --git a/fleets/approvals.mdx b/fleets/approvals.mdx index 1e5c9bb..7a9ab61 100644 --- a/fleets/approvals.mdx +++ b/fleets/approvals.mdx @@ -124,7 +124,7 @@ To change which repositories a fleet may reach, or to drop it to read-only, change `repositories` or `repository_access` in a private improvement chat. Choose **Edit setup** in the fleet header, then ask for the change. -Open **Edit instructions manually** below the setup conversation to review the change. Choose **Save changes** in the setup footer. +Open **Edit instructions manually** below the setup conversation to review the change. Choose **Save changes** in the fleet header. The next service credential uses the updated repository access. The grant stays approved, and the fleet keeps running. diff --git a/fleets/slack.mdx b/fleets/slack.mdx index fdc7663..b10c3a3 100644 --- a/fleets/slack.mdx +++ b/fleets/slack.mdx @@ -143,7 +143,7 @@ To detach a fleet from the channel, remove its `mention` trigger and apply the c 1. Open the fleet in the dashboard and choose **Edit setup** in its header. 2. Ask the chat to remove the Slack mention trigger. -3. Open **Edit instructions manually** below the setup conversation and check that the trigger is gone. Choose **Save changes** in the setup footer. +3. Open **Edit instructions manually** below the setup conversation and check that the trigger is gone. Choose **Save changes** in the fleet header. In the terminal, start the same chat with `agentsfleet chat --fleet --setup-revision --model `. `` is the `setup_revision` field that `agentsfleet --json fleet show ` prints. Ask for the change, then run `/review` and `/apply`.