For context, Phi is an AI-powered Chromium browser for macOS. I think many people here may not be familiar with it. The closest reference point is probably Arc, although Phi's goal is slightly different: a browser that you and your agents can both use.
The main changes in version 2.0 are Spaces for organizing tabs and fully sandboxed Profiles, which keep cookies and sessions separate. In practice, that means things like multiple Google logins no longer collide. URL rules can also ensure that specific sites open in the correct space/profile.
The assistant now has whole-browser context, and the guardrail for removing sensitive data runs locally on your Mac instead of on a server. I recently worked on optimizing the local model path on the Apple Neural Engine because it seemed wasteful to leave that hardware unused.
I am also experimenting with a new memory visualization system (we call it Nebula). Rather than displaying browser memory as a list or force graph, it presents it as a spatial surface that you can explore over time. This feature is still evolving, but it has been interesting to work on.
Next, we want to enable agents such as Claude Code or Codex to control your actual browser window rather than a separate headless Chrome instance.
Lwrless•48m ago
For context, Phi is an AI-powered Chromium browser for macOS. I think many people here may not be familiar with it. The closest reference point is probably Arc, although Phi's goal is slightly different: a browser that you and your agents can both use.
The main changes in version 2.0 are Spaces for organizing tabs and fully sandboxed Profiles, which keep cookies and sessions separate. In practice, that means things like multiple Google logins no longer collide. URL rules can also ensure that specific sites open in the correct space/profile.
The assistant now has whole-browser context, and the guardrail for removing sensitive data runs locally on your Mac instead of on a server. I recently worked on optimizing the local model path on the Apple Neural Engine because it seemed wasteful to leave that hardware unused.
I am also experimenting with a new memory visualization system (we call it Nebula). Rather than displaying browser memory as a list or force graph, it presents it as a spatial surface that you can explore over time. This feature is still evolving, but it has been interesting to work on.
Next, we want to enable agents such as Claude Code or Codex to control your actual browser window rather than a separate headless Chrome instance.
I'm happy to dig into any of this.