ttmacer

No problem, glad to ignite some spark! Just to clarify, what I mentioned is also effectively possible with other harnesses. Pi's minimalism just made it more ergonomic to focus on the right things and encouraged me to question and thus learn.

AFAIK Pi out of the box as other harnesses handles this use case via dot directories on your filesystem. So a .pi directory in your working directory Pi gets started in is the place where you would implement such a profile. Note that there is also a global .pi in the home directory, which takes precedence over session-local .pi directories.

In the past I used this abstraction conveniently to setup different agents for different purposes. I kinda like having this abstraction on my filesystem to inspect instead of it being hidden away in a opaque harness or, even worse, the weights of the model.

EDIT: then a Pi Extension that swaps .pi directories out, maybe via git worktrees, is just the low-hanging fruit to establish your profiles pattern I think.

to correct, I meant "pivoting towards the idea that Pi is "more" than a coding agent"

It's so great to see now that the folks behind Pi also try to pivot away from the idea that Pi is more than a "coding" agent. Its minimalism, and tool call primitives really lends itself to be a general purpose agent for your OS that you gradually extend on demand for your specific use case.

Since January I use Pi professionally as well as personally and I can only recommend to start small and grow your harness over time. For example, for an agent in production it was so helpful for me to use Pi in interactive mode via tmux to get a feel of the agentic flow, tool calls and reasoning traces for a certain use case while only the stylized responses are rendered in Telegram via an extension to the user. As a Developer, I have full technical observability and control while providing and incrementally improving a service to a user at the same time.

Excited how Pi Durable will fit in and can support more. Congrats and thank you!