Shaping your own tools with agents

I had already been experimenting with web interfaces for Pi when I read a post by DODOREACH. People had asked for the Pi interface from an earlier post. Rather than release the finished app, DODOREACH shared a one-shot prompt for building your own. It gave me a good starting point for a new setup, which I then shaped around the way I work.

Pi Web gives me an interface where I can choose a project, start or resume a session, watch messages and tool calls as they happen, and keep several chats running. It works on my desktop and phone through Tailscale. Pi still handles models, login, tools, settings, and session files. I did not want the web app to become a second version of Pi that would always be catching up.

Most changes since then have been small adjustments to how I work. The phone layout is one example. Project and worker lists move into drawers, leaving the limited screen space for the conversation. I can check or continue the same sessions from my desktop without setting up a separate mobile workflow.

On a larger change, I keep requirements and architecture decisions in the supervisor session. A subagent can trace one issue or implement a bounded change in a separate context. It returns a structured handoff instead of adding its full transcript to the supervisor's context. I can inspect that transcript when I need it. Pi Web allows up to three subagents to work at the same time, but only one can edit. Parallel work helps with independent investigations. It is not the default.

Using Pi Web has made its boundary clearer. It should make Pi easier to reach and inspect, not become another development environment. Next, I want each project to define its deploy action and common scripts. A simple file browser could also be useful, but only if it supports the same narrow workflow.