Skip to content
Closed
Show file tree
Hide file tree
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 agent/docs/source/explanations/agentapp-runtime.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Provider credentials and connector implementations remain outside the FAB.
### Model responses

`agent.responses.create(request)` accepts an Open Responses-compatible JSON
object. The Flower 1.34.0 runtime recognizes:
object. The Flower 1.35.0 runtime recognizes:

- `model` and `input`
- `stream`
Expand Down
2 changes: 1 addition & 1 deletion agent/docs/source/how-to-guides/connect-accounts.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The current account connectors are Slack, Notion, GitHub, and Attio. Their
implemented actions are read-only.

```{important}
Flower 1.34.0 supports account connectors only for runs in your personal
Flower 1.35.0 supports account connectors only for runs in your personal
workspace. A run that selects account connectors is rejected in a collaborative
federation. Built-in tools such as `web_search` do not require this connection
flow.
Expand Down
4 changes: 2 additions & 2 deletions agent/docs/source/how-to-guides/create-automations.md
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ requested one and understands how to stop it.

## Understand automation scope

The 1.34.0 runtime builds scheduled runs from the current run request. It keeps
The 1.35.0 runtime builds scheduled runs from the current run request. It keeps
the automation's runs in the current run series and federation and replaces
`agent.input` with the scheduled `input`.

Expand Down Expand Up @@ -151,7 +151,7 @@ already started. Stop that run separately from its run details or with
`flwr stop <run-id> supergrid`.

There is no public CLI command for listing or stopping automations in Flower
1.34.0. Use the automation list in SuperGrid.
1.35.0. Use the automation list in SuperGrid.

## Recover from a failed schedule

Expand Down
8 changes: 4 additions & 4 deletions agent/docs/source/how-to-guides/troubleshoot-agent-runs.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,8 @@ one controlled change makes the cause easier to identify.
For a CLI-started run, record the run ID and inspect its status and logs:

```console
$ uvx --from flwr==1.34.0 flwr list --run-id <run-id> supergrid
$ uvx --from flwr==1.34.0 flwr log <run-id> supergrid --show
$ uvx --from flwr==1.35.0 flwr list --run-id <run-id> supergrid
$ uvx --from flwr==1.35.0 flwr log <run-id> supergrid --show
```

In the browser, keep the conversation open and note the visible federation,
Expand All @@ -36,7 +36,7 @@ Preserve other connections and settings. Add only the missing section, then run
**Symptom:** the CLI fails before opening Flower Chat, or SuperGrid asks you to
sign in again.

1. Complete `uvx --from flwr==1.34.0 flwr login supergrid` again.
1. Complete `uvx --from flwr==1.35.0 flwr login supergrid` again.
1. Ensure the browser flow uses the same Flower account that has Agent access.
1. Retry one deterministic prompt in a new chat.

Expand Down Expand Up @@ -131,7 +131,7 @@ In Flower Chat, {kbd}`Ctrl+C` during a response requests a stop. Wait until the
prompt is idle before submitting again. If the old run remains active, use:

```console
$ uvx --from flwr==1.34.0 flwr stop <run-id> supergrid
$ uvx --from flwr==1.35.0 flwr stop <run-id> supergrid
```

Start a new conversation if the interrupted app left incomplete tool state that
Expand Down
10 changes: 5 additions & 5 deletions agent/docs/source/how-to-guides/use-agents-and-federations.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,8 @@ Authenticate first, then ask SuperGrid for the federations visible to your
account:

```console
$ uvx --from flwr==1.34.0 flwr login supergrid
$ uvx --from flwr==1.34.0 flwr federation list supergrid
$ uvx --from flwr==1.35.0 flwr login supergrid
$ uvx --from flwr==1.35.0 flwr federation list supergrid
```

Use the full federation ID shown by this command, including its leading `@`, in
Expand All @@ -51,7 +51,7 @@ later commands.

The following `uv run` examples use the Flower version installed in your local
project environment. To stay consistent with the rest of this guide, ensure
that environment has `flwr==1.34.0` installed.
that environment has `flwr==1.35.0` installed.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Explain the 1.35 in-chat federation selector

For the newly specified 1.35 environment, lines 89–100 present config editing plus a restart as the only way to change the flwr chat federation and recommend flwr run for frequent switching. Version 1.35 handles /federation directly in framework/py/flwr/cli/chat/chat_app.py:478-509, so this guide now sends users through an obsolete and substantially more disruptive workflow.

Useful? React with 👍 / 👎.


Flower selects the federation in this order:

Expand All @@ -76,7 +76,7 @@ $ uv run flwr run . supergrid \
The app can also be a published app spec:

```console
$ uvx --from flwr==1.34.0 flwr run @publisher/agent supergrid \
$ uvx --from flwr==1.35.0 flwr run @publisher/agent supergrid \
--federation @account/federation-name \
--run-config 'agent.input="Summarize this federation task."'
```
Expand Down Expand Up @@ -147,7 +147,7 @@ series. Use the SuperGrid browser to inspect existing conversations.

Built-in tools such as `web_search` and `web_fetch` are chosen in AgentApp code.
Slack, Notion, GitHub, and Attio are account connectors selected for a browser
run. Flower 1.34.0 rejects account-connector references for a collaborative
run. Flower 1.35.0 rejects account-connector references for a collaborative
federation; run that task in your personal workspace instead.

See [Connect accounts](connect-accounts.md) for setup and the exact read-only
Expand Down
4 changes: 2 additions & 2 deletions agent/docs/source/tutorials/build-a-collaborative-agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,15 +71,15 @@ version = "0.1.0"
description = "A bounded public-web research AgentApp"
license = "Apache-2.0"
requires-python = ">=3.11"
dependencies = ["flwr==1.34.0"]
dependencies = ["flwr==1.35.0"]

[tool.hatch.build.targets.wheel]
packages = ["research_agent"]

[tool.flwr.app]
publisher = "local"
display-name = "Research Agent"
flwr-version-target = "1.34.0"
flwr-version-target = "1.35.0"
fab-include = ["research_agent/**/*.py"]

[tool.flwr.app.config.agent]
Expand Down
10 changes: 5 additions & 5 deletions agent/docs/source/tutorials/get-started-with-flower-agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ groups messages into a conversation.
Prefer the browser? Start with [Chat in your browser](quickstart.md).

```{note}
This tutorial targets Flower 1.34.0. Flower Agent and `flwr chat` are
This tutorial targets Flower 1.35.0. Flower Agent and `flwr chat` are

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Document interactive history for the 1.35 tutorial

After retargeting this tutorial to 1.35, its command list still omits /history and lines 129–130 incorrectly state that older run series cannot be restored interactively. The 1.35 CLI registers /history as “Show or continue conversation history” in framework/py/flwr/cli/constant.py:58-64 and handles it in chat_app.py:474-477, so users following the pinned tutorial are unnecessarily directed to the browser instead of the supported CLI workflow.

Useful? React with 👍 / 👎.

experimental and may change between releases.
```

Expand All @@ -27,8 +27,8 @@ You don't need to provide model credentials for a SuperGrid run.
Use `uvx` to run the documented version in an isolated environment:

```console
$ uvx --from flwr==1.34.0 flwr --version
flwr, version 1.34.0
$ uvx --from flwr==1.35.0 flwr --version
flwr, version 1.35.0
```

Running an explicit version keeps every command in this tutorial on the same
Expand All @@ -48,7 +48,7 @@ address = "supergrid.flower.ai"
If you maintain a custom file, ensure that section exists. Then log in:

```console
$ uvx --from flwr==1.34.0 flwr login supergrid
$ uvx --from flwr==1.35.0 flwr login supergrid
```

Open the printed authentication link and complete sign-in. The CLI stores the
Expand All @@ -57,7 +57,7 @@ resulting account credentials for later SuperGrid commands.
## Start a chat

```console
$ uvx --from flwr==1.34.0 flwr chat
$ uvx --from flwr==1.35.0 flwr chat
```

```{figure} ../_static/screenshots/flwr-chat.png
Expand Down
6 changes: 3 additions & 3 deletions agent/docs/source/tutorials/write-your-first-agentapp.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ it on SuperGrid. The example makes one model request so you can isolate project
configuration from connector logic.

Complete [Chat in your terminal](get-started-with-flower-agent.md) first. This
tutorial targets Flower 1.34.0.
tutorial targets Flower 1.35.0.

## Create the project

Expand Down Expand Up @@ -88,15 +88,15 @@ version = "0.1.0"
description = "My first Flower AgentApp"
license = "Apache-2.0"
requires-python = ">=3.11"
dependencies = ["flwr>=1.34.0,<2.0"]
dependencies = ["flwr>=1.35.0,<2.0"]

[tool.hatch.build.targets.wheel]
packages = ["hello_agent"]

[tool.flwr.app]
publisher = "local"
display-name = "Hello Agent"
flwr-version-target = "1.34.0"
flwr-version-target = "1.35.0"
fab-include = ["hello_agent/**/*.py"]

[tool.flwr.app.config.agent]
Expand Down
Loading