All of the ones I mentioned work great for me. You can dream up your interface and inject technical design ideas and your claw can code it up; as you test it, you fix it if you get new ideas for how it should work.)

For example my recipe project is built around a relatively simple sqlite db. Input for new recipe is in arbitrary format as it goes to an agent (image snapshot on iphone; txt file, speaking it out in a telegram message; a text prompt); the model figures out what to extract and save from the projects’ documents and the context of the specific telegram thread. Output is in whatever form I ask for; rescaled for a number of people; fit in single compact paragraph; or detailed ingredients first then instructions; possibly replace missing ingredients. Query can be arbitrary complex—it almost always finds the recipe I want so far much to my surprise; once I had to followup to select a specific option from a couple ambiguous variants. By default, I like to keep the replies for my recipe queries brief, practical, projected to my cookware. Once I set up this very simple recipe project and imported a couple old datasets, I gave up all of multiple previous recipe schemes (text files or org notes with complex syncing schemes, iPhone apps…)