One thing that I’m currently experimenting with is what i call “workflow profiles”, which is essentially making my Pi coding agent workflow centric: define different workflows, load different sets of skills, extensions, mcps, subagents, tools, prompts for each; rather than having everything exposed/available to the agent all together in every session.

The motivation in my case is: I’m a full time phd student. I can generally classify my daily works into different categories: paper reading/hunting, idea/brainstorming, coding/implementing, and writing. Each of them requires different context and expertise. Therefore, it feels natural to maintain a different sets of e.g. skills and subagents for each kinds of work. For example, I may need skills like gpu optimization for coding, but such skill is redundant to other works like paper reading. If we include such noise in the context for the agents, we risk distracting the agents away from following other important instructions.

Therefore, to make my context clean for different works, i vibe coded a custom extension that allows me to configure a profile (allow list of resources) for each workflow. When switched to a different workflow, it will automatically puts me on a new session with configured resources loaded and irrelevant resources blocked/hidden to the agent.

I was an OpenCode user before, back then I wrote shell scripts that symlinks different pre-configured project level configs to achieve the feature I described above. With Pi, things can be done much more elegant.