Repository navigation
Labels
P2Planned: limited in scope, has a way around it, or a missing featurePlanned: limited in scope, has a way around it, or a missing featureenhancementNew feature or requestNew feature or request
Description
Priority
medium. The change adds a page and its script in the web layer. It adds no backend module. The code that runs a recipe does not change.
Components
- app/nullius (backend)
- app/web (routes)
- templates and static files
- docs and the site
- catalogue (benchmarks, agents, capabilities)
- the standard (ports, kits, relay, runs)
- CI, workflows and skills
Today
- Saved recipes are files in
<data>/recipes/on the server. The only view of them is the Saved recipes dialog in the run builder. - The dialog shows a name, the runner and a date for each recipe. To see what a recipe holds, you must load it into the builder and replace the recipe on the page.
- The dialog cannot duplicate or export a saved recipe. To export one, you load it and export it from the Review step.
- A recipe can name a benchmark, an agent or a provider that this Nullius does not have now. The dialog marks the recipe "Draft" and gives no reason. The builder gives the reason only after you load the recipe.
Wanted
- A Recipes page in the Manage group of the sidebar, with its own icon.
- A table made with the table toolkit, with search, Columns, Sort by and the pager. The columns are the name, one column for each builder step from 01 to 07 with the builder's step names, and the save date. A long value is cut in its cell, and the tooltip shows the full value.
- An Import button on the title line. It imports a recipe file, or a list, through the strict import. A toast shows the reason for a refusal.
- Actions for each row: Open in the run builder, Info (the full recipe step by step, and its JSON), Duplicate under a free name, Export JSON, and Delete after a confirmation.
- A row whose recipe this Nullius cannot run shows one short warning with an alert icon. The tooltip and Info give the reasons. The page uses the builder's own check of a loaded recipe. It does not add a second check.
- A browser on another machine sees Import, Duplicate and Delete greyed, with the reason as the tooltip. Open, Info and Export work.
Acceptance
- The sidebar has a Recipes link in the Manage group, with an icon from the sprite.
- The table has the name, Benchmark, Runner, Dataset, Agent, Model, Limits, Where and Saved columns, and search, Columns, Sort by and the pager work.
- A long cell value is cut, and its tooltip shows the full value.
- Import adds a good file and shows the reason for a bad file in a toast.
- Open loads the recipe into the builder at Review, as the Saved recipes dialog does.
- Info shows each step and the JSON. Duplicate saves a copy under a free name. Export downloads the JSON. Delete asks first.
- A recipe that names a benchmark, agent or provider that this Nullius does not have shows the warning, and its tooltip names the problem.
- A browser on another machine sees Import, Duplicate and Delete greyed with the reason.
- With no saved recipe, the page shows one line and the Import button.
- The docs say where to manage saved recipes.
Dependencies and related
- Keep saved builder recipes in the user data directory, not in the browser #202 (closed by feat(builder): keep saved recipes in the user data directory #203): saved recipes are kept on the server. This page builds on its API.
Metadata
Metadata
Assignees
Labels
P2Planned: limited in scope, has a way around it, or a missing featurePlanned: limited in scope, has a way around it, or a missing featureenhancementNew feature or requestNew feature or request
Activity
feat(builder): add a Recipes page for the saved recipes (ThinkFlowLab…