AQ Feature suggestion

I do a lot of Android Studio testing with real wireless devices, and I think Agents Room could significantly improve mobile QA by integrating directly with the local development environment. If Android Studio is running and a connected device is available, the harness could detect that automatically and expose the device/session to the agent. The agent could then launch the app, navigate through screens, test responsiveness across device sizes, reproduce issues, capture errors, and assist with debugging. The same concept could apply on macOS with Xcode, iOS simulators, and connected iPhones. ### Key idea Instead of requiring the agent to constantly search for this context, **Agents Room Harness should provide it proactively.** For example, the harness could detect: * Android Studio or Xcode is running * Connected physical devices * Active emulators/simulators * Current application/build * Device model, resolution, orientation, and OS version * Relevant logs, crashes, or build errors The harness could then inject that information into the agent's context only when needed. This would make QA much more reliable than relying primarily on browser testing, especially for native applications, responsiveness, and device-specific issues. It could also reduce token/usage costs. I've noticed agents sometimes spend a significant amount of context searching for information the harness could already know. If the harness gathers that information locally and simply tells the agent, the agent can immediately focus on the task instead of spending usage discovering the environment. Essentially: **make the harness more context-aware so the agents have to search less.** That could improve autonomous QA, debugging, responsiveness testing, and overall efficiency while potentially reducing agent usage considerably. Just my two cents. You guys have done an amazing job with Agents Room, and I think this could make the development workflow even stronger.

This gathers what several people told us separately. Their original messages stay private: only this rewording is public, and nobody sees who wrote what.

Discussion1

• The team6 days ago

  Thanks for taking the time to send this. We're cleaning up older requests, and this one isn't on our roadmap for now, so we're closing it. If it still matters to you, please submit a new request describing how you'd use it today: fresh requests with current use cases are the ones we look at first.

You will be told by email and in the app on every reply. Every message carries a link to stop them.