DEDUPEDAuthorization notice. Dynolab is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA researcher who runs many model tests and loses track of which results belong to which question.
The problemPrompts, outputs and notes for one question end up scattered across files and chats.
The outcomeA saved study with your question, prompts, results, observations and revisions, with incomplete runs marked.
What you need first
- An Apple Silicon Mac running macOS 14 or later
- The Dyno app downloaded from the latest GitHub release
- An MLX model downloaded through Discover in the app
Steps
- Start a model or pool in Models.
- Open Lab → Studies and create a study for your question.
- Add prompts and run them, then record observations next to the results.
- Compare revisions and export measurements with their provenance when you need them.
Prompt for your agent
In the canivel/dynolab repo, read docs/research-notebooks.md and create a study for the question <question>. Expected output: a saved study with prompts, results and observations in Lab → Studies. Verify that any token-limited or incomplete run is shown as incomplete, not as an answer.
Caveat. Dyno's notebook keeps your evidence locally, but the README does not say it syncs or shares studies with anyone.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page