dsh-taskwatch

Data, consent, and model usage

After project and task consent, TaskWatch reads the consenting task's public conversation and public tool evidence and sends that material to the supervision provider and model you selected. The provider may bill those calls according to its own terms and actual usage. TaskWatch shows known usage and marks unavailable usage as unknown; choose a model and limits appropriate for your account.

TaskWatch does not use hidden reasoning, and the supervision Agent has no execution tools. Evidence can be incomplete: a timeout, a missing or truncated event, stale result, exhausted budget, or failed request is displayed as such instead of as a normal assessment. A model assessment is advice based on the available evidence, not a guarantee that work is correct or complete.

Local storage

The private ledger defaults to ~/.dsh/taskwatch/ledger.sqlite. A nonblank DSH_HOME selects $DSH_HOME/taskwatch/ledger.sqlite; for example, launch DSH with DSH_HOME="$HOME/.dsh-private". Supported ~, ~/ and ~\ prefixes expand to the OS home. Blank DSH_HOME uses the default. Relative homes are rejected. Automatic storage must resolve outside the plugin package, launch checkout and configured workspacePath, including existing symlink destinations; an unsafe or unresolvable location stops initialization with an error. Launching from the OS home still permits the standard ~/.dsh location unless that home is explicitly configured as the workspace. This startup check covers known paths, not future session workspaces.

To keep an existing ledger or choose another location, set the TaskWatch plugin configuration's dbPath (for example, /path/to/private/taskwatch/ledger.sqlite). An explicit dbPath is preserved exactly, including existing relative-path behavior; choose its location deliberately. TaskWatch does not automatically migrate or delete ledgers when storage configuration changes or the plugin is removed. New ledger directories use mode 0700 and database files use 0600.