diff --git a/content/docs/developers/agent-builder.mdx b/content/docs/developers/agent-builder.mdx index 0f62b1a..f46d5f4 100644 --- a/content/docs/developers/agent-builder.mdx +++ b/content/docs/developers/agent-builder.mdx @@ -19,8 +19,8 @@ Write this in the message box: Send the message. - - New Agent message box with a request for help preparing for meetings. + + New Agent message box with a request for help preparing for meetings. @@ -28,9 +28,9 @@ Fluso opens a setup conversation called **Manager**. It gives the Agent a name a Read the setup beside the conversation. Ask for a change there if needed. Select **Launch agent** when you are ready. - - - The creation request and Manager's reply, with the Launch agent button below. + + + Meeting Prep's Manager shows the creation request and ready reply beside the instructions, files, capabilities, and Launch agent button. @@ -55,8 +55,8 @@ In our run, the Agent estimated costs we had not supplied. We corrected that and We also asked for a shorter version: three decisions, the missing costs, and one question to ask first. - - Meeting Prep updates the workshop brief after a room change and a correction about unknown costs. + + Meeting Prep updates the workshop brief after a room change and a correction about unknown costs. @@ -65,7 +65,7 @@ You can correct details, attach another document, or ask for a shorter answer in When you find a way of working you want to keep, [teach it your preferences](/developers/improve). - **My Agents** and **New Agent** offer Fluso starting points for research, project follow-through, inbox triage, and document review. Preview one to create your own copy. Manager helps with missing app connections. + On **New Agent**, **Explore agents made by Fluso** offers starting points for research, project follow-through, inbox triage, and document review. Preview one to create your own copy. Manager helps with missing app connections. **Fill in a form instead** lets you enter the setup directly. **Continue setup** lets you return to an unfinished creation. diff --git a/content/docs/developers/examples/release-review.mdx b/content/docs/developers/examples/release-review.mdx index b60def4..c2a0199 100644 --- a/content/docs/developers/examples/release-review.mdx +++ b/content/docs/developers/examples/release-review.mdx @@ -14,11 +14,13 @@ Create a reviewer through [New Agent](/developers/agent-builder). Explain what i > *"Help me decide whether we're ready to launch. Compare the notes, test results, and open issues I share. Tell me what still blocks us and what information is missing. Don't publish anything or contact anyone."* -Then attach the actual material. Explain when you need the decision and what must be true before launch. +Then attach the material for your review. Explain when you need the decision and what must be true before launch. - - - A launch-review request with five attached documents from this documentation project. +For this example, we gave the Agent sample files for a fictional documentation launch. + + + + Release Reviewer receives five sample documents and a request to check the reader journey and validation evidence in separate sessions. @@ -30,9 +32,7 @@ For a larger review, you can ask: The Agent can use separate [sessions](/developers/guides/conversations) while it works on the overall review. -In our local run, two sessions checked different parts of this documentation release. The Agent recommended waiting because checks and approval were still pending. It returned a report with both sessions' findings. - -It also misread one progress note as a contradiction. We clarified it in the conversation, and it corrected the saved report. +In our run, two sessions checked the draft guides and validation notes. The Agent recommended waiting because some launch requirements were still unresolved. It saved their findings in `release-review.md`. Read the reasoning, not only the recommendation. An earlier successful check may cover an older version of the work. @@ -50,12 +50,12 @@ You can schedule a later check with a [one-time routine](/developers/schedules). The routine reread the saved report and validation notes. It found no new evidence, so it kept the unresolved checks open. - - A compact routine message and its completed follow-up in the Agent conversation. + + The routine reports no new evidence and keeps the launch checks open in the Agent conversation. Its result appeared in Inbox. The routine did not approve or publish the release. -The screenshots show real responses to this documentation project's files. The example requests above are wording you can adapt to your own launch. +The example requests above are wording you can adapt to your own launch. diff --git a/content/docs/developers/guides/conversations.mdx b/content/docs/developers/guides/conversations.mdx index 161a483..c76f8d3 100644 --- a/content/docs/developers/guides/conversations.mdx +++ b/content/docs/developers/guides/conversations.mdx @@ -26,20 +26,22 @@ For example, one session might check venue offers while another checks the budge You usually keep talking to the main conversation. You do not need to manage each session yourself. -For a real example, see [Review a launch](/developers/examples/release-review). +For an example, see [Review a launch](/developers/examples/release-review). ## Inspect sessions when useful -Open **Sessions** above the composer to see their progress. Select one to read its assignment and answers. **Main conversation** takes you back. +When the Agent has created sessions, open the dropdown beside its title. Select one to read its assignment and answers. **Main conversation** takes you back. **New result** marks a result you have not read. **Uses an earlier setup** means the session started before a saved change to the Agent. - - - The Sessions list shows Reader journey review and Validation evidence review as idle, both using an earlier setup. +These sessions belong to our fictional launch-review example. Select one to read its findings.}> + + The Sessions menu lists Main conversation, Agents Documentation Review, and Launch Requirement Mapping. All three show Idle. +Session titles are generated automatically. The two sessions shown here checked the reader journey and validation notes. + The Agent can reuse sessions, give them corrections, and cancel work it no longer needs. Requested results return automatically. diff --git a/content/docs/developers/guides/files.mdx b/content/docs/developers/guides/files.mdx index 2e85b42..ea30162 100644 --- a/content/docs/developers/guides/files.mdx +++ b/content/docs/developers/guides/files.mdx @@ -16,11 +16,13 @@ Projects help organize work. Agents in your account can still use shared files e ## Save a reference it should keep -Add files under **Knowledge** in the Agent editor for material it should use repeatedly. A writing guide, review checklist, or agreed policy can fit here. +Open the Agent conversation's side panel with the panel icon at the upper right. Under **Setup**, select **Edit**. Under **Knowledge**, select **Add files**. Choose the reference. Select **Save changes**. + +A writing guide, review checklist, or agreed policy can fit here. - - The Knowledge section contains Meeting brief checklist.md and an Add files control. + + The Knowledge section contains Meeting brief checklist.md and an Add files control. diff --git a/content/docs/developers/guides/inbox.mdx b/content/docs/developers/guides/inbox.mdx index b85142c..155e10e 100644 --- a/content/docs/developers/guides/inbox.mdx +++ b/content/docs/developers/guides/inbox.mdx @@ -4,13 +4,13 @@ icon: inbox description: See what needs you without opening every Agent. --- -Open **Inbox** in the Agents sidebar to find approvals, failures, and routine results. +Select the bell icon at the bottom of the Agents sidebar to open **Inbox**. In the popup, select **Open full Inbox** to see approvals, failures, and routine results. -Choose **Open result** to return to the conversation. Read the answer and open any files it produced. +Select **Routine updates** to find a completed routine. Click its row to return to the conversation. Read the answer and open any files it produced. - - - Inbox showing a completed routine and an Open result link. + + + Inbox with All selected shows Routine ran entries for Release Reviewer and Meeting Prep, with two Routine updates. @@ -24,13 +24,11 @@ The number beside **Inbox** counts unseen updates. Opening Inbox clears the unre ## Find a particular update -Use **Filters** to choose an Agent or show only approvals, failures, or routine results. +Use **All**, **Approvals**, **Failures**, or **Routine updates** to choose the type of update. An empty filtered list means nothing matches that view. It does not mean all work is complete. - The sidebar opens **All updates**. A direct link without filters, or resetting filters, opens **Approvals & failures**. - Inbox shows recent updates rather than a complete history. Separate session results stay in their conversations, but their approvals can appear here. Only updates displayed in a visible Inbox tab become seen. Filtered-out items keep their unread state. A changed update can become unread again. diff --git a/content/docs/developers/guides/settings.mdx b/content/docs/developers/guides/settings.mdx index 258a6d8..d473182 100644 --- a/content/docs/developers/guides/settings.mdx +++ b/content/docs/developers/guides/settings.mdx @@ -4,7 +4,7 @@ icon: sliders-horizontal description: Choose what your Agent can use and how it should respond. --- -Select the **Edit agent** pencil in a conversation to open its setup. **Edit** lets you change the fields yourself. **Manager** lets you describe the change in conversation. +Open the Agent conversation's side panel with the panel icon at the upper right. Under **Setup**, **Edit** opens the saved fields. **Refine with manager** opens a conversation where you can describe the change. For changes to its usual way of working, start with [Improve your Agent](/developers/improve). @@ -17,8 +17,8 @@ For changes to its usual way of working, start with [Improve your Agent](/develo Choose what the job needs. You can add more later. - - The Capabilities picker shows Meeting intelligence selected, with one skill and no connectors. + + The Capabilities picker shows Meeting intelligence selected, with one skill and no connectors. diff --git a/content/docs/developers/guides/sharing.mdx b/content/docs/developers/guides/sharing.mdx index 4d961c3..fc951d5 100644 --- a/content/docs/developers/guides/sharing.mdx +++ b/content/docs/developers/guides/sharing.mdx @@ -10,7 +10,7 @@ Your conversations, routines, project files, and connected account credentials a ## Choose what to share -1. Open the Agent's actions menu. +1. Open the **⋯** menu on the Agent's row in the sidebar. 2. Select **Share**. 3. Choose any reference files, custom skills, or custom connection URLs to include. 4. Select **Create public link**. @@ -19,9 +19,9 @@ Instructions and settings are included. Anyone with the link can read the publis Read the selected files and skill folders before publishing. Check connection URLs too: a URL can itself contain private information or an access key. - - - The Share Agent dialog has the meeting checklist selected and explains what the public link includes. + + + The Share Agent dialog lists two unchecked custom skills, explains what stays private, and offers Create public link. diff --git a/content/docs/developers/improve.mdx b/content/docs/developers/improve.mdx index e7f51b0..2332fdc 100644 --- a/content/docs/developers/improve.mdx +++ b/content/docs/developers/improve.mdx @@ -18,17 +18,17 @@ You can keep working there until the answer is useful. Use **Manager** when you want the Agent to follow that preference in future work. -1. Select the **Edit agent** pencil in the conversation. -2. Choose **Manager** on the setup page. +1. Open the Agent conversation's side panel with the panel icon at the upper right. +2. Under **Setup**, select **Refine with manager**. 3. Explain what you want to keep. > *"For future meeting briefs, put the decisions first. Keep the background short, and finish with three questions I should ask. Save that as my usual format."* Read the saved instructions beside the conversation. Then return to the Agent and give it another task. - - - A request to put decisions first, followed by Manager's confirmation that it saved the format. + + + Manager confirms the decisions-first format beside the revised instructions. Its reply also says it could not verify the attached checklist's contents. @@ -42,7 +42,7 @@ Tell the Manager what happened and what you wanted instead: This gives it a useful rule to save. You can also ask it to review corrections from the working conversation. -Prefer to make the change yourself? **Edit** opens the saved fields. There is no version-history screen, so explain what to restore if you want to undo a change. +Prefer to make the change yourself? **Edit**, beside **Refine with manager**, opens the saved fields. To undo a change through Manager, explain what to restore. [Settings and app access](/developers/guides/settings) explains the other controls, including response style, files, and connected apps. diff --git a/content/docs/developers/index.mdx b/content/docs/developers/index.mdx index 51a50eb..28d5283 100644 --- a/content/docs/developers/index.mdx +++ b/content/docs/developers/index.mdx @@ -22,11 +22,11 @@ Prefer another starting point? [Browse the examples](/developers/examples). ## Come back when you need it -**My Agents** brings your assistants together and shows upcoming routines. Open an Agent to continue its conversation. +The **Agents** sidebar lists your assistants. Select an Agent to continue its conversation. - - - My Agents shows Meeting Prep and Release Reviewer, with a morning routine coming up for Meeting Prep. + + + The Agents view shows the sidebar beside the New Agent workspace. Release Reviewer has a green dot and a Working label above Meeting Prep. The workspace includes the job prompt and Explore agents made by Fluso. diff --git a/content/docs/developers/schedules.mdx b/content/docs/developers/schedules.mdx index f8cd5f2..9198c95 100644 --- a/content/docs/developers/schedules.mdx +++ b/content/docs/developers/schedules.mdx @@ -24,13 +24,15 @@ Check the saved time and timezone in **Routines**. If the timing could be ambigu ## Set it yourself -Open **Routines** in the Agents sidebar, or use the routine control in the conversation. Write the message, choose the Agent, and set the time. +Open the Agent conversation's side panel with the panel icon at the upper right. Under **Routines**, select **Add**. Write the message and set the time. -You can choose one time, daily, weekdays, weekly, or a repeating interval. +The editor offers **Once**, **Daily**, **Weekdays**, and **Weekly**. It schedules work for the current Agent. - - - A one-time routine for Meeting Prep at 8 AM in Europe/Zurich, asking it to review the workshop's open decisions. +Check the timezone. Select **Create routine**. + +Use the New routine panel on the right to schedule a follow-up for our fictional launch-review example. Check the message, time, and timezone before saving.}> + + The New routine panel for Release Reviewer has Once selected for 9 AM in Asia/Kolkata and a request to update the release review while keeping unresolved checks pending. @@ -76,7 +78,7 @@ Check that the Agent pauses or deletes the routine when that condition is met. T Existing custom timing stays unchanged unless you change the frequency. - On **Routines**, you can apply the same message and timing to several Agents. Each gets its own routine. + Expand **Also run on other agents** in the routine editor to apply the same message and timing to several Agents. Each gets its own routine. **Select all** covers the Agents currently in the picker. It does not include Agents created later. @@ -85,7 +87,7 @@ Check that the Agent pauses or deletes the routine when that condition is met. T An Agent already using the same instructions at another time needs an explicit selection to add another timing. - Open the session and use its routine control. The sidebar editor targets the Agent's main conversation. + Open the session and use its routine control. To schedule work in the main conversation, open that conversation first. A session's routine uses that session's saved setup. A routine in the main conversation uses the setup selected for its new turn. diff --git a/public/images/agents/agent-capabilities.png b/public/images/agents/agent-capabilities.png deleted file mode 100644 index 1c4ef6f..0000000 Binary files a/public/images/agents/agent-capabilities.png and /dev/null differ diff --git a/public/images/agents/inbox-result.png b/public/images/agents/inbox-result.png deleted file mode 100644 index 27d2c97..0000000 Binary files a/public/images/agents/inbox-result.png and /dev/null differ diff --git a/public/images/agents/knowledge-files.png b/public/images/agents/knowledge-files.png deleted file mode 100644 index 07f2d4f..0000000 Binary files a/public/images/agents/knowledge-files.png and /dev/null differ diff --git a/public/images/agents/meeting-brief.png b/public/images/agents/meeting-brief.png deleted file mode 100644 index b782ee8..0000000 Binary files a/public/images/agents/meeting-brief.png and /dev/null differ diff --git a/public/images/agents/meeting-create.png b/public/images/agents/meeting-create.png deleted file mode 100644 index 6ca1d21..0000000 Binary files a/public/images/agents/meeting-create.png and /dev/null differ diff --git a/public/images/agents/meeting-manager.png b/public/images/agents/meeting-manager.png deleted file mode 100644 index 404db33..0000000 Binary files a/public/images/agents/meeting-manager.png and /dev/null differ diff --git a/public/images/agents/meeting-refinement.png b/public/images/agents/meeting-refinement.png deleted file mode 100644 index 1bd5424..0000000 Binary files a/public/images/agents/meeting-refinement.png and /dev/null differ diff --git a/public/images/agents/my-agents.png b/public/images/agents/my-agents.png deleted file mode 100644 index ed4ac45..0000000 Binary files a/public/images/agents/my-agents.png and /dev/null differ diff --git a/public/images/agents/native/agent-capabilities.png b/public/images/agents/native/agent-capabilities.png new file mode 100644 index 0000000..5c3a8d2 Binary files /dev/null and b/public/images/agents/native/agent-capabilities.png differ diff --git a/public/images/agents/native/agents-overview.png b/public/images/agents/native/agents-overview.png new file mode 100644 index 0000000..cd4239f Binary files /dev/null and b/public/images/agents/native/agents-overview.png differ diff --git a/public/images/agents/native/inbox-result.png b/public/images/agents/native/inbox-result.png new file mode 100644 index 0000000..403b78d Binary files /dev/null and b/public/images/agents/native/inbox-result.png differ diff --git a/public/images/agents/native/knowledge-files.png b/public/images/agents/native/knowledge-files.png new file mode 100644 index 0000000..001cc5a Binary files /dev/null and b/public/images/agents/native/knowledge-files.png differ diff --git a/public/images/agents/native/meeting-brief.png b/public/images/agents/native/meeting-brief.png new file mode 100644 index 0000000..fd1b66e Binary files /dev/null and b/public/images/agents/native/meeting-brief.png differ diff --git a/public/images/agents/native/meeting-create.png b/public/images/agents/native/meeting-create.png new file mode 100644 index 0000000..58744c4 Binary files /dev/null and b/public/images/agents/native/meeting-create.png differ diff --git a/public/images/agents/native/meeting-manager.png b/public/images/agents/native/meeting-manager.png new file mode 100644 index 0000000..7481bf8 Binary files /dev/null and b/public/images/agents/native/meeting-manager.png differ diff --git a/public/images/agents/native/meeting-refinement.png b/public/images/agents/native/meeting-refinement.png new file mode 100644 index 0000000..d46709c Binary files /dev/null and b/public/images/agents/native/meeting-refinement.png differ diff --git a/public/images/agents/native/review-request.png b/public/images/agents/native/review-request.png new file mode 100644 index 0000000..a143606 Binary files /dev/null and b/public/images/agents/native/review-request.png differ diff --git a/public/images/agents/native/routine-editor.png b/public/images/agents/native/routine-editor.png new file mode 100644 index 0000000..4ae3348 Binary files /dev/null and b/public/images/agents/native/routine-editor.png differ diff --git a/public/images/agents/native/routine-result.png b/public/images/agents/native/routine-result.png new file mode 100644 index 0000000..7e82259 Binary files /dev/null and b/public/images/agents/native/routine-result.png differ diff --git a/public/images/agents/native/sessions-list.png b/public/images/agents/native/sessions-list.png new file mode 100644 index 0000000..1acd54f Binary files /dev/null and b/public/images/agents/native/sessions-list.png differ diff --git a/public/images/agents/native/share-options.png b/public/images/agents/native/share-options.png new file mode 100644 index 0000000..725072c Binary files /dev/null and b/public/images/agents/native/share-options.png differ diff --git a/public/images/agents/review-request.png b/public/images/agents/review-request.png deleted file mode 100644 index 2772e8a..0000000 Binary files a/public/images/agents/review-request.png and /dev/null differ diff --git a/public/images/agents/routine-editor.png b/public/images/agents/routine-editor.png deleted file mode 100644 index e67458a..0000000 Binary files a/public/images/agents/routine-editor.png and /dev/null differ diff --git a/public/images/agents/routine-result.png b/public/images/agents/routine-result.png deleted file mode 100644 index 8b6e65c..0000000 Binary files a/public/images/agents/routine-result.png and /dev/null differ diff --git a/public/images/agents/sessions-list.png b/public/images/agents/sessions-list.png deleted file mode 100644 index 0df178a..0000000 Binary files a/public/images/agents/sessions-list.png and /dev/null differ diff --git a/public/images/agents/share-options.png b/public/images/agents/share-options.png deleted file mode 100644 index 621b924..0000000 Binary files a/public/images/agents/share-options.png and /dev/null differ