# Computer History v1.0.0

**First public release of Computer History for DeepSeek Harness.**

Computer History helps a DSH agent resume an ongoing task using locally stored, evidence-backed activity metadata. It does not record screenshots, keystrokes, page bodies, source-file contents, terminal output or clipboard text.

## Highlights

- **Continue where you left off.** Work Episodes, Timeline and Work Threads connect recent desktop activity to a short, grounded native `@ Computer History` continuation in a fresh DSH Session. Resume selection prioritizes concrete Work State and supporting evidence rather than copying raw history into prompts.
- **Three native collectors, one npm/GitHub package.** macOS Accessibility, Windows UI Automation and Linux AT-SPI executables are built on their own native runners and bundled in a single, SHA-256-verified tarball. The installed Host selects the packaged binary automatically.
- **Privacy first.** Recording is off until the user opts in. An app allowlist, protected-surface denial, optional browser-origin/editor-root consent and configurable local data retention apply before activity is kept in SQLite.
- **Optional Companions.** A bundled Chromium/Firefox browser companion and a VS Code editor companion can add consented resource/workspace evidence and require separate setup.
- **Product verification.** The exact three-platform tarball has passed Windows/macOS/Linux clean-install, browser first-run, Settings, History/Privacy HTTP 200 and packaged collector handshake checks. macOS also has a 52-check installed Continue/disable/re-enable/uninstall lifecycle journey.

## Installation

After the npm and GitHub artifacts for this release have **actually** been published:

```bash
dsh plugin --profile <profile> add dsh-computer-history
```

Use the DSH 0.2 profile to enable the plugin, complete first-run consent and select allowed apps. Browser/editor pairing is optional and separately controlled. Alternative: install the `dsh-computer-history-1.0.0.tgz` asset from this GitHub Release using the same `dsh plugin --profile <profile> add ./...` command.

## Support and limitations

- **Verified Host:** DeepSeek Harness `0.2.0-rc.2`; other versions are not automatically supported by the declared peer ranges.
- **Linux live capture:** requires an actual X/AT-SPI desktop session and accessibility permissions. A headless CI runner returning `permission-required` verifies honest collector startup, **not** desktop observation.
- **macOS collector:** packaged executable uses ad-hoc codesigning for plugin execution. It is not a standalone notarized Finder application.
- **Data security:** the database is local SQLite but not separately encrypted. Use OS disk encryption and user filesystem protections. Downgrading database schemas is not guaranteed.
- **Model privacy:** deterministic summaries stay local by default; deliberately enabled remote summarization or sending Continue context to a cloud-configured DSH agent may transmit a bounded set of consented metadata.
- **Companion support:** separate browser/VS Code installation or pairing may be required; browser store listings are not implied.

For verification details, threat model, support instructions and release gating, see [Release process](../release.md), [Security](../../SECURITY.md) and [Development](../development.md).

## Distribution integrity

The release workflow first verifies the exact main commit, builds and tests all three platform binaries, and runs the installed product matrix. Only then does it create the immutable tag, publish **the same tarball bytes** to npm using GitHub Actions Trusted Publishing (OIDC), wait for npm Registry identity, and finally create the GitHub Release with an integrity-checked asset.

This document is a **candidate release note** until that workflow has completed. Do not claim it has been published before npm and GitHub Release are live.