Cursor Automation runs: no more interactive chat input in browser

Support Bug Reports
, ,
1

Hello,

We are using cursor automations for some analysis of support tickets coming in.
A new automation run gets triggered by a webhook and the cloud agent usually runs through fine.

What we really liked was being able to go into the automation run agent thread and interact with it further: ask backup questions and drill down more etc.

Now in the browser view of the agent automation runs, we can NOT interact with the agent anymore. There is not chat input box anymore. What we need to do now, i open it in Curosr desktop wich is a few extra clicks, takes a few seconds and overall is very annoying.

What is the issue here? Is this a bug or was the feature removed? This was an integral part of our workflow unfortunately. It seems like the options to interact witht he cloud agent still exists, but only through desktop app. Why?

Thanks for any support!

Example agent run id: bc-b925937a-3808-4de6-9334-59aeff74f40f
Automation id: 2f2a4541-7180-11f1-8cbf-12b154d6cb29

  • Operating system: Browser (Google Chrome) on Mac …
2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

7

Hey @kkra, thanks for the report, and sorry about the disruption to your workflow!

This is not a removed feature. It is an issue on cursor.com that we are already tracking: when an agent was started by an automation, the web page is currently not picking up your team’s follow-up permission correctly, so it hides the chat input even though your team settings allow follow-ups. Nothing on your side is misconfigured, and no settings change is needed.

The desktop app reads that permission differently, which is why “Open in Cursor” still lets you continue the conversation. That is the workaround for now, and I know it is a few extra clicks.

I have added your report to the internal tracking for this and will update this thread.