One useful change, from the first request to the next session. Desktop and phone are part of the same working process.
Request beta accessDependency Radar is our example project: a small tool that checks package releases and links to their sources. In this walkthrough, we’re making its report friendlier for a teammate, while leaving update decisions to the developer.
“Help me make Dependency Radar friendlier for a teammate. Add a short intro to the report that explains what to review before updating anything.”How the project stays together
The agent asks what would help. The developer answers from their phone: put the introduction in the printed report, just above the timestamp. The plan keeps the change small: one sentence, updated checks and the README.
Before you update anything, read the release notes printed under each package.See the phone side
Review the implementation and its checks in the project. Then update the explanation beside the code. A passing check is useful evidence; the final review is still yours.
Keep the release check read-only. Review the sources before choosing an update.How the project stays together
Save the project rule and the next goal. Continue with another model without discarding the project material. Knowledge is editable, so an old decision doesn’t have to become permanent.
Never update packages automatically. Keep release-note links beside each package.How the project stays together
Model Finder lets you compare capabilities, context, published rates and available scores. Search for what matters to your work, then put the options side by side. A catalogue entry doesn’t connect a provider; you still choose which accounts to use.
Matchmaker checks local model options against your hardware and working preferences. Inspect memory needs, capabilities and licence requirements before downloading. Fit and speed are estimates; run a benchmark when you want to test the real thing.
Explore model tools →Canvas brings the project’s interface into the workspace. Try the buttons, check a smaller viewport and keep the source close while you work. You’re looking at the actual page, with its real interactions.
We gave Dependency Radar a release-review desk: a package watchlist beside a focused inspector. Select a package, follow its source links and mark it reviewed. Nothing installs or changes a dependency.
Code, documentation, goals and workflows belong to the same project. Chat is the starting point; the workspace gives each piece of the job somewhere to go.
Miton is in development. Public beta access has not opened yet.
Planned v1 pricing: A$10 a month.
Founding lifetime: A$199, paid once.
We plan to offer founding lifetime access during launch and for 12 months after v1 launches. We’ll review the offer’s availability then; existing lifetime licences remain lifetime.
One licence per active machine. Hosted model usage is separate.
See pricing and launch terms →