Answers to the questions we hear most often
Only what you connect. Each source below sends nothing until you install it.
The shell hooks record every command you run: the command line as typed, its exit code, start and end time, the shell, a per-shell session id, the hostname, your username, the OS and its version, and whether the shell is an SSH login. The daemon adds the terminal app and multiplexer you use. When an upload arrives, the server also stores the IP address it came from and that address's country.
exclude in ~/.shelltime/config.yaml takes regular expressions (Go syntax). A matching command is dropped before it is written to disk or synced.dataMasking is on by default. Before upload, it masks JSON Web Tokens (strings shaped like eyJ….….…) in a command, keeping their first and last 4 characters. It doesn't recognize other secrets such as API keys or passwords, so keep those out with exclude.~/.shelltime, readable only by your user.shelltime cc install and shelltime codex install point Claude Code's and Codex's OpenTelemetry export at the local daemon, which forwards it. Besides sessions, models, tokens and cost, that includes your prompts, tool details (shell commands, file paths, truncated tool input and output, errors) and the assistant's responses. Raw API request and response bodies and system prompts are dropped by the server.
To leave some of it out, set OTEL_LOG_USER_PROMPTS, OTEL_LOG_TOOL_DETAILS or OTEL_LOG_ASSISTANT_RESPONSES to 0 in the env of ~/.claude/settings.json, or otel.log_user_prompt / otel.log_agent_responses to false in ~/.codex/config.toml. Re-running the install command resets them. While either agent is running, the daemon also syncs its quota windows every 10 minutes.
With codeTracking.enabled: true and the VS Code, Neovim or JetBrains plugin, each heartbeat carries the file path, project name and root path, git branch, language, line count, cursor line and position, the editor and plugin with their versions, and the machine and OS. File contents aren't part of a heartbeat.
shelltime q sends your question with context about where you ask it: working directory, hostname, git state, project tooling and a listing of file names. ai.shareContext: false limits it to the shell, OS and question, and --show-context prints the request without sending it.shelltime dotfiles push uploads the supported config files, and shelltime alias import uploads the aliases in your shell config.shelltime cc backfill and shelltime codex backfill.Partly. The CLI and daemon, the install script and the Neovim and JetBrains plugins are public, so you can read exactly what they collect and send. The server, the web app and the iOS and Mac apps are closed source.
shelltime CLI and daemon (hooks, masking, sync, encryption). The CLI is MIT licensed.The VS Code extension's source isn't public.
Each of them covers one part of what ShellTime tracks, and goes deeper there.
shelltime rg searches what was synced, and its server can read what you send.ShellTime's difference is the combination: shell commands, AI coding agents and editor time in one account, with one CLI and daemon. If you only need a better local shell history, Atuin is the better fit; if you only need editor time across many editors, WakaTime is.
Yes. ShellTime offers a free plan that you can use without any payment. If you need more advanced features or higher quotas, paid plans are also available, but the free plan is generous enough for most individual developers to get started.
Recording isn't limited: shell commands, Claude Code, Codex and editor activity are all recorded on the free plan. The limits are on what you can see and use:
New accounts get a 14-day Pro trial with no card. It unlocks the Pro features, but not the larger AI credit quota or bigger teams. Compare plans.
Yes. We will never sell your data for any purpose. Your data belongs to you.
Uploads go over HTTPS. To keep something away from ShellTime entirely, exclude it before it leaves your machine. The questions below explain exactly what is collected, what the CLI's encryption does and where your data is stored.
It isn't end-to-end, and we want to be clear about that. With encrypted: true in ~/.shelltime/config.yaml and the daemon running, each upload of shell commands is encrypted on your machine with a new AES-256-GCM key, and that key is encrypted with the RSA-2048 public key of your API token.
The matching private key is on the ShellTime server. When a batch arrives, the server decrypts it and stores the commands like any others, so it can show them on your dashboard. The encryption protects the upload on its way, on top of HTTPS; it doesn't stop ShellTime from reading your commands.
exclude pattern.~/.shelltime on your machine, readable only by your user. shelltime gc removes records that were already synced.shelltime q sends your question and its context.[REDACTED]. It feeds the anonymous word cloud on the global board.You can fully remove ShellTime from your machine by running the built-in uninstall commands and then deleting the binary and config directory.
shelltime hooks uninstallshelltime daemon uninstallshelltime cc uninstall
shelltime codex uninstallrm -rf ~/.shelltimeshelltime binary from your PATH (e.g. /usr/local/bin/shelltime or wherever your package manager installed it).If your dashboard looks empty, the most common cause is that the shell hooks or daemon were not set up correctly. Make sure the integration is correctly installed for your shell (zsh, bash, or fish).
You can verify the daemon is running and synchronizing properly with:
shelltime daemon statusIf the daemon is not running, reinstall it with shelltime daemon install and confirm you have authenticated using shelltime auth.
If you didn't find the answer you were looking for, please reach out to us. We read every message and are happy to help.