You bring the idea.
Nubi brings a next step.
A clear path from your request to a result you can inspect.
1. Install the Windows alpha
Download only from the Nubi download page. The current installer is unsigned and intended for testing. Close an older Nubi instance before updating.
2. Connect a supported model
Paste an API key in Connections inside the desktop app. Nubi detects supported providers and displays available models. Access to a provider’s chat website is different from API access or credits.
3. Tell Nubi the whole goal
Include a destination and desired result. For example: “Create a text file called welcome.txt in Downloads with this message.” Nubi should ask only for information it actually needs.
4. Grant the access the task needs
Desktop control allows screenshots to be sent to your connected model and mouse/keyboard operations. Reviewed PowerShell runs as your Windows user. Login passwords and two-factor codes belong only on the provider’s sign-in screen.
5. Check the outcome
Use Results to find saved files and receipts. Verify important changes. Stop ends pending work but cannot reverse actions already completed.
When subscriptions open
Sign in on the website, pair a compatible subscription-enabled desktop build, and try five task starts. A verified USDC invoice will extend the account’s access. The 0.10.0 alpha checks access with the account service. Tasks remain unavailable until that service is deployed and your desktop is paired.