Browser Use and Agent-to-Agent Feedback
Once an agent can use a browser, another AI system becomes a source of feedback it can consult directly—not just a separate tab the human has to manage.
I added an integrated browser to Coding App, along with tools the agent can call to navigate and inspect web pages. The browser lives beside the project workspace, so the agent can move between local files, its own tool results, and the outside world without losing the thread of the task.
That makes it possible for the agent to consult another AI system as part of its workflow. In this example, the local Qwen model reads the existing /hai content, opens ChatGPT in the embedded browser, asks for feedback on the most recent post, and brings the response back into its own context. It can then use that critique to decide what to change.
The interesting shift is that the browser is not only a way to fetch information. It becomes a visible collaboration surface between AI systems: one model can ask another to critique, explain, compare, or pressure-test an idea, while the human can see the request, the navigation, and the returned page in the same interface.
This also extends the inspectability theme of the series. Once the agent can act outside the local workspace, it becomes important to show where it is going, what it is doing there, and what information it brings back. The browser is more useful when it is connected to the workspace, but that connection should remain visible enough for the human to question, interrupt, and control.