What Skutter reads
Skutter works out your hours from these kinds of activity on your Mac. All of it is stored on this Mac, and there is no account. Skutter never uploads it on its own.
What it records
- Shell commands
- From the hooks Setup adds to zsh, bash, fish: each command line, the folder it ran in, when it started and ended, and its exit status. Each terminal session also notes the terminal app, tab and shell it runs in, and the Mac's name.
- Running programs
- Every few seconds the background service lists your own processes. For each program started from a recorded terminal or agent session, it keeps the program's path, its arguments and its working folder. On a Mac it does the same for any of your programs whose file is not inside an app bundle or under /System, whether or not a hook saw it start: Homebrew tools, helpers in /usr/libexec and /usr/sbin, and programs in your home folder such as language servers or nvm's node.
- Apps, windows and documents
- Through Accessibility (Skutter Observer): which app is in front, each time that changes, and when the Mac is idle or locked. For Terminal, iTerm2, VS Code, Xcode, JetBrains IDEs, Safari, Chrome, Arc, Brave, Firefox, Edge, GitHub Desktop, Figma, Slack, Linear, Notion and any app that declares itself a developer tool, also the window title and the path of the open document. Other apps are recorded by name only. While 1Password or Apple Passwords is in front, only the time is recorded, not even the app. A private browser window is recorded as the browser's name only.
- Web addresses
- For a browser in front: the address's host and path, without the fragment, and without the query string unless you add the site to the keep-query list in Skutter's policy file. For banking, health, mail, messaging and sign-in sites, only the host, and no window title.
- Git commits
- When it writes notes, Skutter reads git's own log in your projects' repositories: each commit's id, subject, time and branches, and the author's and the committer's names and email addresses. It keeps the names and addresses you commit under, so it can tell your commits from other people's. Each recorded command also notes the repository, branch and commit it ran at.
- Agent sessions
- From the hooks Setup adds to Claude Code and Codex: when a session starts and ends, its folder, and for each tool call the tool's name and its main argument, up to 2,048 bytes. That argument is the call's command, file path, web address it fetched, search pattern or folder, or the task prompt it hands a sub-agent; for any other tool, one of the call's text fields, such as a search query. For the prompts you type, only the time you sent each one, never the text. If you run skutter repair, it fills in tool calls the hook missed from Claude Code's own transcripts on this Mac, keeping the same argument.
- Tokens and plan limits
- From Claude Code and Codex's own session logs on this Mac: each session's model and token counts. For Claude Code, also your plan's usage percentages and reset times, from its status line (Setup points it at Skutter) and from Claude Code's state file, which also gives the account's email address and id so Skutter can tell accounts apart. Claude Code's credentials file is never opened.
What it never records
- Keystrokes, or anything you type into an app
- The screen, or screenshots of it
- File contents: only the paths above
- Command output
- The text of the prompts you type to an agent, or the agents' replies
- Window titles of apps outside the list above (their name is recorded)
- Other users' processes on the Mac
Read the hooks yourself
The shell hooks are short scripts, installed as they are. The agent hook is part of the skutter command itself; a small shell version is used only inside containers, where skutter is not installed.
skutter-hook.zshzsh hookskutter-hook.bashbash hookskutter-hook.fishfish hookAgentHooks.swiftthe agent hook on a Mac (Claude Code, Codex)AgentToolArg.swiftwhich tool argument it keepsskutter-agent-hook.shthe agent hook inside a container
Where it goes
Hooks append what they see to files in Skutter's folder on this Mac; the background service then moves it into a database in the same folder. Skutter never uploads any of it on its own. It leaves the Mac only when you choose: a day's project and client totals, if you add them to feedback you send, and the reports an AI client you connect through MCP asks for. What the app does send over the network, and when, is in the privacy policy.
Redaction is narrow: values of secret-looking assignments (such as TOKEN=… or --password=…) and AWS access key ids are replaced before commands, agent tool arguments, program arguments and window titles are stored in the database. Other secrets, such as an Authorization header, are not recognised, and a command or tool argument sits unredacted in its hook file until the service moves it.
Read the privacy policy ›