verbiricha (npub107j…ncxg) I've been using fragua for a couple weeks now and I quite like it. Some feature requests:
- i want tool steps to have structured output (for example i have a tool to compute branch name). Right now only llm steps can provide structured output? I've hacked around this by having an llm call my tool, but it's not ideal.
- I wish the webui had some more contextual actions (i.e. approve/decline changes) on the run's detail page
- I wish there were more timestamps in the run list and detail pages.
- I want some control over worktree creation. I have a workflow that I use for feature work or if I pass it a PR url it looks at my review and addresses it. This leads to worktree collision where sometimes the initial run for that branch left tree dirty or the branch checked out and fragua fails to account for this. I've worked around it temporarily by creating a new branch for every run.
I'm not asking you to implement all this. Just letting you know in case it dovetails with feedback from other users. I am not using it as intended where I want to apply the changes to my local git worktree at the end of a run. I am running fragua on a remote sandboxed machine and most of my workflows open or update a PR that I review elsewhere. Which makes the Approve/Discard step at the end of the run kind of unecessary. I'm thinking about building my own webui that is beads-aware but still uses fragua to drive workflows under the hood.
mplorentz / Matt Lorentz
npub16z…l92l7
2026-09-09 16:53:44 UTC
Author Public Key
npub16zsllwrkrwt5emz2805vhjewj6nsjrw0ge0latyrn2jv5gxf5k0q5l92l7Published at
2026-09-09 16:53:44 UTCEvent JSON
{
"id": "584cddbb48326dcc1c6149cd41b6851f8c5f920e7980d9f9ee7e97b239f785b7",
"pubkey": "d0a1ffb8761b974cec4a3be8cbcb2e96a7090dcf465ffeac839aa4ca20c9a59e",
"created_at": 1788972824,
"kind": 1,
"tags": [
[
"p",
"7fa56f5d6962ab1e3cd424e758c3002b8665f7b0d8dcee9fe9e288d7751ac194"
]
],
"content": "nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg I've been using fragua for a couple weeks now and I quite like it. Some feature requests: \n- i want tool steps to have structured output (for example i have a tool to compute branch name). Right now only llm steps can provide structured output? I've hacked around this by having an llm call my tool, but it's not ideal.\n- I wish the webui had some more contextual actions (i.e. approve/decline changes) on the run's detail page\n- I wish there were more timestamps in the run list and detail pages.\n- I want some control over worktree creation. I have a workflow that I use for feature work or if I pass it a PR url it looks at my review and addresses it. This leads to worktree collision where sometimes the initial run for that branch left tree dirty or the branch checked out and fragua fails to account for this. I've worked around it temporarily by creating a new branch for every run.\n\nI'm not asking you to implement all this. Just letting you know in case it dovetails with feedback from other users. I am not using it as intended where I want to apply the changes to my local git worktree at the end of a run. I am running fragua on a remote sandboxed machine and most of my workflows open or update a PR that I review elsewhere. Which makes the Approve/Discard step at the end of the run kind of unecessary. I'm thinking about building my own webui that is beads-aware but still uses fragua to drive workflows under the hood.",
"sig": "df58d6377f61e5c112a03939d676b482e60fc6eff6312dea37920868f49b1472dcc6f8d82c87c49cc073370d1bcb61bd069836d73b283fbca45028e3bf3cc300"
}