Your morning code briefing in 10 seconds

The AskScout web app runs in your browser, signs in with GitHub, and stores your digest history under your account so you can revisit past summaries. The AskScout CLI runs locally in any git repo, uses your own API key, and stores nothing online beyond the calls to your provider. Same digest format and same daily summary, two surfaces, depending on whether you want a hosted history or a fully local workflow.

Yes. Once you grant access during GitHub sign-in, the AskScout web app generates digests for any repo on your account, public or private, including organization repositories you have access to. The CLI works on any local git repository by default since it reads from your local clone, so private repo support is automatic with no extra configuration.

The AskScout CLI works with any git repo regardless of host, including GitLab, Bitbucket, Codeberg, Gitea, and self-hosted git servers, because it reads from your local clone rather than calling a host API. The web app currently only supports GitHub OAuth for sign-in.

The digest is automatically generated from your real git history, so it can occasionally miss nuance or restate the same change twice across sections. It stays grounded in your actual commit messages and diffs rather than working from memory, which keeps the output close to what you really shipped. For day-to-day tracking, standup notes, weekly reviews, and remembering your own work, the digest is reliably useful.

The AskScout web app has a soft cap of 30 digests per day across your entire account, which covers daily standup notes, end-of-day reviews, and weekly summaries comfortably. The CLI has no AskScout-imposed usage limit, so you can run digests as often as you want. The only limits there are your provider's API rate limits and your own spend on the key you bring.

No. AskScout reads only commit messages and diffs, meaning the specific lines added and removed in each git commit. Full source files, environment variables, secrets, build artifacts, and untracked files are never accessed or transmitted. A diff only contains code that actually changed in a commit, not your entire codebase or repository state.

Yes. AskScout's code only ever reads from your repo, never writes, modifies, or deletes anything. The full codebase is open source under the MIT license, so you can audit exactly what it does and how it handles your data. The web app uses GitHub OAuth, which you can revoke any time at github.com/settings/applications.

The web app stores your digest history under your GitHub account in a private database, so you can revisit past digests anytime. The AskScout CLI stores nothing online, with no telemetry or analytics. Locally, the CLI saves your API key in ~/.askscout/config.json with owner-only file permissions, plus a small per-project state file in .askscout/state.json that tracks pace and run history.

Yes. On the web app, Settings → Danger Zone → Delete Account permanently removes every digest, summary, and record tied to your user ID. You can also clear individual repo histories without deleting your account. For the CLI, just remove the ~/.askscout folder from your home directory and any .askscout folder inside your project to wipe local state.

Yes. AskScout is fully open source under the MIT license. The complete codebase, including the web app, the CLI, and the shared core library, is public on GitHub. You can read every line, fork the project, audit how your data is handled, or contribute improvements through pull requests.