Your workspace.
Your decisions.

Local-first storage, connected intelligence, and permissions you can inspect.

Local-first does not mean offline-only

Juno keeps workspace records and conversation history locally. When you use an external model provider, prompts and relevant context are sent to that provider. Its account terms, retention policies and charges apply. Connected tools may send information to their own services.

Files and computer access

Tool access depends on the task, workspace and configured permissions. Review the operation requested before granting access. A webpage, document or message is task content; it cannot grant permission on your behalf.

Code, Mission and verification

Read-only questions and file-changing work have different effects. Check the actual result and verification evidence. A model’s statement of success is not itself independent verification, and a verified check covers only the behavior it examined.

Providers and credentials

Connect only accounts you intend Juno to use. Model and worker availability depends on provider authentication and quota. Do not place credentials in prompts, shared screenshots or bug reports.

Diagnostics and support

Review any diagnostics before sharing them with support. Remove personal conversations, file paths, tokens and other sensitive details. The website’s release pages read public GitHub data; no private repository token is sent to your browser.

This website

Website pages are served by Vercel. Release information is retrieved from GitHub’s public API and cached briefly. Following an installer link takes you to GitHub. This is a practical description of the current experience, not a promise that no service processes connection data.

Questions? Contact Tanishk.