Question re: dirge server

Hello,

Currently the `dirge mcp` mode seems to be the main mechanism for running dirge-as-a-service. I'm interesting in web-based orchestration frontends to coding agents that do process orchestration and want to explore if dirge if a good fit here.

Anyways, `dirge mcp` seems pretty focused for the sub-agent delegation workflow; If there consideration for a more generalized interface where more about dirge's starting conditions can be controlled (e.g. setting personas, passing-in entire agent configurations and/or provider configs, setting explicit session-resumes-by-id, etc)?

I see a lot about dirge itself subsumes the use-case for a web-based frontend; I'm also interested in the idea of a highly-coupled frontend that exploits dirge internals, but mostly want to just learn more about the coding agent at this time. Looks pretty neat. Thanks!