Choose where the agent works
The desktop app, CLI, and VS Code extension share an account and plan usage. They keep workspace tools close to the code. Pick a graphical workspace for reviewing a broad change, a terminal for a repeatable task, or the editor when you want code and conversation side by side.
Give the agent evidence, not guesses
A passing type check, a test result, and a browser interaction establish different things. Use all the checks the change needs. Language-server diagnostics require a working server for the language; browser interaction requires the desktop browser integration and an accessible app.
A developer stays responsible for the result
Use Plan mode to review an approach before implementation. Choose edit permissions to suit the repository, inspect command output, and review the final diff. Do not grant broad unattended permissions to a repository containing production credentials.
Hosted model requests include relevant prompts and code context. LoopCode is in early access; desktop signing and notarisation remain in progress. Installation instructions state the current requirements and first-launch behavior.
KEEP GOING
A useful next step.
Put it to work in your project.
Desktop, CLI, and VS Code. One LoopCode account. Free to start.