The first ten minutes

Start the console:

nodwyn app

A build with native window support opens the console in its own window. The release archives open your browser instead. Both pair the console with a one-time ticket in the address, so there's nothing to copy.

Connecting a model

There's no built-in model, so a new install asks for one before it lets you start a task. Home shows two forms, one after the other.

The first form chooses a provider. It starts on Ollama, which needs no key and can run on this computer or another one on your network. You can also choose OpenAI, Anthropic, OpenRouter, Baseten, Cerebras or "another server".

A provider that needs a key can't be saved until there's a keychain to hold it, so the form shows the keychain form beside it. Pick a passphrase of at least eight characters and remember it: nobody can recover it. You can instead tick Don't protect it with a passphrase. The keychain is then a file only your user can read, but this is the weaker choice, and Settings says so for as long as you keep it.

The second form picks the model. nodwyn asks the provider for its models and offers them as buttons. Save and use it makes your choice the default for new tasks. More holds optional settings, including reasoning effort and what you use the model for. You can leave those for later.

Your API key goes into the keychain and never into config.toml. A binding row allows it only for that provider's host. A model with a key has to be reached over HTTPS unless it runs on this computer.

A first task

Home asks "What should we get done?". Under the box, Work in lists your folders, and Add a folder points nodwyn at a new one. A task reads and writes inside its folder and any folders you've mounted there. Workspaces explains how those are set up.

If the folder is a git repository, In a worktree is ticked by default under Options. The task then works on a branch of its own, nodwyn/<id>, in a copy of the repository under .nodwyn/worktrees, so two tasks on one repository don't step on each other and your checkout stays as it was.

Type what you want and press Enter. Shift+Enter starts a new line. The task opens, the model starts working, and the sidebar groups what's happening: Needs you on top, then your folders with their tasks.

When the model wants to run a command that needs your approval, the task stops and asks you. Approvals covers what you'll see then, and the tour of the console shows the rest of the screen.