> For the complete documentation index, see [llms.txt](https://docs.agenticflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agenticflow.ai/changelog/office-hour-49-safer-agent-chat-protected-uploads-and-model-cleanup.md).

# Office Hour #49: Safer Agent Chat, Protected Uploads & Model Cleanup

### 📺 Quick Recap

Office Hour #49 focuses on reliability and clarity in the places users feel most directly: chatting with agents, recovering from failed messages, moving uploads to time-limited signed links, and surfacing deprecated-model states clearly.

This release includes fixes for:

* Agent chat sessions that could become unresponsive
* Message streaming failures in the chat interface
* Continuing a conversation in the same thread after a failed message
* Deprecated model handling in agent chat
* Agent recursion-limit and runtime-error visibility
* Time-limited signed links for workflow and agent uploads
* `URL to Markdown` and `Web Scraping` node reliability issues

🎥 Watch the full session:

{% embed url="<https://www.youtube.com/watch?v=IxysLYdJsbY>" %}

***

### 🔍 What Changed & Why

#### 1. Agent Chat Is More Stable During Long-Running Conversations

Some users could hit a state where chatting with an agent made the browser difficult to recover from.

<figure><img src="https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2FcLiMA33ZXApY308m1SxI%2Fimage.png?alt=media&amp;token=e1f1fbe9-01f5-4bd2-81d1-8e1a137c46c2" alt=""><figcaption></figcaption></figure>

This was one of the highest-impact fixes in this release because it affected the core agent conversation experience, not just a secondary settings page or edge workflow.

Agent chat is now more stable during long-running responses, tool-heavy conversations, and failure recovery. The interface is smoother, less likely to get stuck, and better at recovering when an agent run does not complete cleanly.

#### 2. Chat Streaming Failures Now Show Clear Notifications

When a message stream failed, the chat interface could leave users uncertain about whether the agent was still working, stuck, or already failed.

The chat interface now surfaces clear notifications for message streaming failures. If the previous message fails, the thread remains usable and users can continue chatting with the same agent in the same conversation instead of starting over.

This makes failures easier to understand and keeps the conversation context intact.

<figure><img src="https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-af3af6fb5eeb172a979363ac11283c43a4dedcd6%2Foh49-agent-runtime-errors-visible.png?alt=media" alt="Agent chat showing a clear failure message"><figcaption><p>After: failed chat states show a clear message instead of leaving the thread looking stuck.</p></figcaption></figure>

#### 3. Agent Runtime Errors Are Now Visible in Chat

Agent chat now gives clearer feedback when an agent cannot continue because of a runtime issue.

This includes cases where:

* The agent is configured with a deprecated model
* The agent reaches its recursion limit
* The agent encounters an error while processing the chat

Instead of failing silently or appearing stuck, the chat surface now displays the issue directly or shows a toast notification. Users can understand what happened and take the next step without guessing.

#### 4. Workflow and Agent Uploads Use Time-Limited Signed Links

Workflow and agent uploads now use temporary presigned URLs rather than long-lived direct file links.

Uploaded files now use expiring URLs:

* **Workflow uploads:** signed links expire after **6 hours**
* **Agent uploads:** signed links expire after **24 hours**

This narrows the access window for uploaded files and keeps link behavior aligned with the context in which each file is used.

#### 5. Deprecated Models Marked Across Providers

Several older model entries are now deprecated across providers. This cleanup reduces confusion in the model selector and helps prevent agents and workflows from being configured with models that are no longer reliable choices.

<figure><img src="https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-e00eb8b71c8314e0ef913300273c0b120d231c5f%2Foh49-deprecated-models.png?alt=media" alt="Deprecated model badges in the model selector"><figcaption><p>Deprecated models are visibly marked in the model selector.</p></figcaption></figure>

**PixelML Provider**

* `pixelml/gemini-2.0-flash`
* `pixelml/deepseek-chat`
* `pixelml/deepseek-reasoner` (R1-0528)
* `pixelml/deepseek-v3.2-exp`

**AgenticFlow Provider**

* `agenticflow/gemini-2.0-flash`
* `agenticflow/gemini-2.0-flash-lite`
* `agenticflow/google-gemini-1.5-flash`
* `agenticflow/deepseek-v3`
* `agenticflow/deepseek-v3.2-exp`

**Google Gen AI Provider**

* `google_gen_ai/gemini-2.0-flash`
* `google_gen_ai/gemini-2.0-flash-lite`

**DeepSeek Provider**

* `deepseek/deepseek-chat`
* `deepseek/deepseek-reasoner`

If an agent is still using a deprecated model, AgenticFlow now surfaces that state in the chat experience so users can update the model instead of interpreting the failure as a generic agent issue.

#### 6. `URL to Markdown` and `Web Scraping` Nodes Are More Reliable

This release also includes fixes for workflow node behavior in `URL to Markdown` and `Web Scraping`.

<figure><img src="https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Ffc8pJPEcQ04TQKTGq8ki%2Fimg_v3_0212g_7abd8fa6-179d-4048-bbe0-0e349f0f02hu.jpg?alt=media&amp;token=9a9fcc1b-221f-4f46-8932-045d5e121475" alt=""><figcaption></figcaption></figure>

The affected nodes now handle scraping and conversion flows more reliably, reducing failed runs and improving stability for workflows that depend on web content extraction.

<figure><img src="https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-4481299e4a26a75781da4fc96fbdacc5e9fe3bbd%2Foh49-workflow-run-logs-brief-success.png?alt=media" alt="Workflow run logs showing successful web content retrieval and content brief generation"><figcaption><p>After: a workflow using web retrieval successfully fetches the Office Hour #49 changelog URL and completes the downstream generation step.</p></figcaption></figure>

***

### Bug Fixes Included

* Improved recovery behavior for unresponsive agent chat sessions
* Added notifications for message streaming failures in chat
* Preserved thread usability after a failed chat message
* Improved agent chat stability and recovery behavior
* Added visible feedback when an agent uses a deprecated model
* Added visible feedback for agent recursion-limit failures
* Added toast notifications for agent chat runtime errors
* Protected workflow uploads with signed URLs expiring after 6 hours
* Protected agent uploads with signed URLs expiring after 24 hours
* Deprecated older Gemini and DeepSeek model entries across PixelML, AgenticFlow, Google Gen AI, and DeepSeek providers
* Fixed reliability issues in the `URL to Markdown` workflow node
* Fixed reliability issues in the `Web Scraping` workflow node

***

#### 🚀 7 Workflow Blueprint Prompts <a href="#id-6-workflow-blueprint-prompts" id="id-6-workflow-blueprint-prompts"></a>

**1. Learning Content Curator Workflow**

> Using the AgenticFlow CLI, deploy the learning-content-curator blueprint. Learning topic: "agentic workflows for operations teams".
>
> Audience: "Operations managers who understand no-code automation but are new to agentic workflow design."
>
> Deploy, run once, show me the curated resources JSON, recommended first 3 resources, 7-day learning path, key concepts, practical exercise, and gaps to fill later.
>
> Leave the workflow deployed. Print the Web UI link.\
> One-line note: why this rung of the composition ladder?

***

**2. Convert ticket summary escalation workflow blueprint**

> Using the AgenticFlow CLI, deploy the ticket-summary-escalation-pack blueprint. Use this ticket thread:
>
> "Ticket #8942 | Customer: Brightline Health | Plan: Enterprise | Thread: Customer reports dashboard exports failing for finance users since Monday. Agent suggested clearing cache; issue persists. Customer says quarter-end report is blocked and asks for escalation. Last error: export job failed after 3 retries."
>
> Summary policy: "Summarize issue, sentiment, urgency, likely owner, missing context, and Slack-style escalation note. Do not claim Zendesk, Pinecone, Slack, ticket updates, or customer messages occurred."
>
> Deploy, run once, show me issue summary, customer sentiment, urgency, likely owner, missing context, and escalation note draft.
>
> Leave the workflow deployed. Print the Web UI link.\
> One-line note: why this rung of the composition ladder?

***

**3. Convert visitor entry pass workflow blueprint**

> Using the AgenticFlow CLI, deploy the visitor-entry-pass-pack blueprint. Use this visitor request:
>
> "Visitor: Aisha Morgan | Email: <aisha.morgan@example.com> | Host: Priya Shah | Visit date: 2026-06-12 | Office: SF HQ | Purpose: vendor security review | ID check: passport verified by reception | Badge type: day pass"
>
> Entry policy: "Require visitor name, valid email, host, date, office, purpose, ID check, and badge type. Draft entry pass text, host notification draft, and security checklist. Do not claim email verification, badge generation, Slack, Gmail, or access-control updates occurred."
>
> Deploy, run once, show me status, missing fields, entry pass text, host notification draft, and security checklist.
>
> Leave the workflow deployed. Print the Web UI link.\
> One-line note: why this rung of the composition ladder?

***

**4. Convert sales anomaly detector workflow blueprint**

> Using the AgenticFlow CLI, deploy the sales-anomaly-detector-pack blueprint. Use these sales rows:
>
> "Category: Subscriptions | Current week: 84200 | Baseline week: 80100 | Transactions: 316\
> Category: Services | Current week: 18400 | Baseline week: 35600 | Transactions: 22\
> Category: Hardware | Current week: 12600 | Baseline week: 11900 | Transactions: 41"
>
> Anomaly policy: "Flag category movement above 25% up or down. Calculate percentage change, identify possible investigation questions, and draft finance alert email. Do not claim QuickBooks, Gmail, accounting updates, or email delivery occurred."
>
> Deploy, run once, show me category movement table, detected anomalies, investigation questions, and finance alert email draft.
>
> Leave the workflow deployed. Print the Web UI link.\
> One-line note: why this rung of the composition ladder?

***

**5. Add Tax Deadline Compliance Pack workflow blueprint**

> Using the AgenticFlow CLI, deploy the tax-deadline-compliance-pack blueprint. Use this tax calendar:
>
> "Entity: Acme Robotics LLC | Jurisdiction: California and federal US | Upcoming: 2026-06-15 federal estimated tax payment; 2026-07-31 quarterly payroll filing; 2026-08-15 sales tax return | Owner: Finance Ops | Notes: payroll filing data is missing contractor classification review"
>
> Company profile: "Series A hardware startup with 42 employees, multi-state sales, and external CPA review. Do not provide legal or tax advice; prepare operational reminders, risk flags, and CPA questions only."
>
> Deploy, run once, show me the deadline table, risk summary, missing inputs, CPA questions, and internal action checklist.
>
> Leave the workflow deployed. Print the Web UI link.\
> One-line note: why this rung of the composition ladder?

***

**6. Sales Leaderboard Coach Workflow**

> Using the AgenticFlow CLI, deploy the sales-leaderboard-coach blueprint. Use these deal rows:
>
> "Ava | Closed Won | $18,000 | New business\
> Ben | Closed Won | $12,500 | Expansion\
> Ava | Proposal | $22,000 | New business\
> Mia | Closed Won | $9,000 | Renewal\
> Ben | Lost | $7,500 | New business"
>
> Team context: "Period: first week of June 2026. Team target: $60,000 closed won. Tone: motivating but honest, celebrate wins and call out next best actions."
>
> Deploy, run once, show me the deal summary, leaderboard JSON, leaderboard table, team progress, rep coaching notes, Slack message, and next-best actions.
>
> Leave the workflow deployed. Print the Web UI link.\
> One-line note: why this rung of the composition ladder?

***

**7. Daily Verse Email Workflow Blueprint**

> Using the AgenticFlow CLI, deploy the daily-verse-email blueprint. Use these inputs:
>
> Reflection focus: encouragement for a busy workday\
> Recipient email: your own email
>
> Deploy, run once, show me the devotional email body, subject line, and send confirmation.
>
> Leave the workflow deployed. Print the Web UI link.\
> One-line note: why this rung of the composition ladder?

***

### Get Started

* **Try AgenticFlow free:** <https://agenticflow.ai/>
* **Latest changelog:** <https://docs.agenticflow.ai/changelog>
* **Join our Discord:** <https://qra.ai/discord>
* **Found a bug?** Email <support@agenticflow.ai> with a reproducible case.