@agentstrack/collector 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,168 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+A change to the event envelope or to the config file shape is a **breaking change** and will be
+released as a major version, with a migration note in this file.
+
+## [Unreleased]
+
+### Added
+- **OpenCode adapter.** Reads `~/.local/share/opencode/opencode.db` (honouring `$XDG_DATA_HOME`,
+  `$OPENCODE_DATA_DIR` and `$OPENCODE_DB`) and emits `session.started`, `session.ended`, cumulative
+  `usage.reported`, `user.prompted`, `tool.completed` / `tool.failed`, `command.executed`,
+  `file.changed` and `file.read`. OpenCode records the provider's real settled cost, so it is the
+  first agent whose sessions carry `cost_basis: REPORTED` rather than an estimate.
+
+  This is a live database the OpenCode app writes to, so it is opened `readonly` + `fileMustExist`
+  with `PRAGMA query_only` and a `busy_timeout`, one short query at a time. The collector never
+  writes to, migrates or locks a user's data.
+- **`AgentAdapter.poll()`**, an optional pull-based source for database-backed agents. `normalize()`
+  is line-oriented and a SQLite file has no lines; rather than pretend otherwise, the daemon drives
+  `poll()` on the same scan cycle, under the same `tracking.agents` gating, the same
+  `excluded_projects` filter and the same privacy pipeline. Resumption uses the spool's meta store —
+  the tailer's `(path, inode, offset)` checkpoint means nothing to a database.
+- **Per-account attribution.** `session.started` and `user.prompted` now carry an optional `account`
+  object: a stable opaque `key` (Claude Code's `oauthAccount.accountUuid`; OpenCode's
+  `<serviceID>:<accountId>`), plus `label`, `org` and `provider`. Sessions from a personal login and
+  a work login no longer merge into one identity and one bill.
+
+  `label` and `org` are PII and are stripped by the privacy pipeline in `metadata` mode; `key` and
+  `provider` always travel, so sessions still split correctly there. Credentials are never read:
+  OpenCode's `account.json` holds a live API key beside the account id and only `id`/`serviceID` are
+  touched, while `auth.json` is never opened.
+
+  Events that predate the collector's start carry **no** account. These files record only who is
+  signed in now, so a historical transcript cannot be attributed without guessing, and a guess that
+  looks like a fact is worse than a blank.
+- `SUPPORT.md`, `ROADMAP.md`, `GOVERNANCE.md`, `CODEOWNERS`, `.editorconfig`, `.gitattributes`,
+  `.nvmrc`, Dependabot config and a CodeQL workflow.
+
+### Fixed
+- **`session.started.cwd` is no longer sent as an absolute path** regardless of
+  `privacy.file_paths`. `cwd` *is* the project root, and it leaked the username, the client name and
+  the directory tree even in `metadata` mode — where `repo.project_path` was already being dropped.
+  It now follows the same rule: sent only under `file_paths: absolute`. Affected the Codex adapter
+  since 0.1.0.
+
+### Changed
+- `tracking.agents` defaults to `[claude_code, codex, opencode]`.
+- **`privacy.prompts: never` now strips the locally derived `derived_title` in `analytics` mode**, so
+  it is possible to keep token, tool and cost analytics while sending nothing derived from a prompt.
+  Previously the setting was consulted only in `full` mode, which made `never` and
+  `local_summary_only` behave identically everywhere else — a privacy control that silently did
+  nothing. `never` now applies in every mode, `full` included.
+- **Agent versions in the registration payload are real.** `ClaudeCodeAdapter.detect()` reads the
+  `version` field out of a transcript (e.g. `2.1.247`) instead of reporting the literal string
+  `'detected'`. An adapter that cannot cheaply establish a version reports none, rather than a
+  placeholder — which today is the case for Codex, whose `detect()` does not open a rollout to read
+  `session_meta.cli_version`.
+- `~/.agentstrack/` is created mode `700`, and `spool.db` with its `-wal` / `-shm` sidecars is
+  `chmod`ed `600`. Previously only `config.yaml` was hardened, so on a shared host another user could
+  read spooled telemetry.
+- The schema contract test resolves the server repository from a sibling `../agentstrack.ai` checkout
+  or `AGENTSTRACK_SERVER_REPO`, instead of an absolute path to one maintainer's machine. It still
+  skips cleanly when the server repo is absent.
+
+### Fixed
+- **A partial trailing line is no longer consumed.** The tailer advances its checkpoint only to the
+  last complete newline and re-reads an unterminated line whole on the next pass. Previously a line
+  the agent was mid-way through writing was emitted broken and its remainder arrived orphaned, so
+  both halves failed to parse and the event was lost — which happened on every live session.
+- **A failed batch can no longer delete unrelated queued events.** `Spool.fail()` now scopes its
+  retry-exhaustion delete to the event ids in the failing batch; it previously deleted table-wide on
+  `attempts`, so one batch exhausting its retries could destroy events it had never touched.
+- **`upload.max_retries: 0` no longer empties the spool.** The value is clamped to a minimum of 1.
+  `attempts >= 0` matched every row, including never-attempted ones, so a config of `0` wiped the
+  whole queue on the first upload failure. The config still accepts `0`–`20`; `0` behaves as `1`.
+
+## [0.1.0] - 2026-08-26
+
+Initial release.
+
+### Added
+
+- **Log tailing, not hooks.** Reads `~/.claude/projects/<slug>/<session-uuid>.jsonl` and
+  `~/.codex/sessions/YYYY/MM/DD/rollout-<ts>-<uuid>.jsonl` read-only, rescanning every 5 seconds for
+  `*.jsonl` files modified in the last 7 days. The collector never installs hooks and never modifies
+  `~/.claude/settings.json` or `~/.codex/hooks.json`. `CLAUDE_CONFIG_DIR` and `CODEX_HOME` are
+  honoured.
+- **Claude Code adapter** — human prompts (separated from tool results), `model.response` with the
+  full token breakdown, tool calls, `Bash` commands, and `Edit` / `Write` / `NotebookEdit` /
+  `Read` file activity. Line counts for an edit are computed locally from the tool input, as a
+  multiset difference, matching what `git diff --numstat` reports.
+- **Codex adapter** — `session.started` and turn boundaries, cumulative `usage.reported` snapshots,
+  user messages, commands with exit code and duration, agent errors, `function_call` and
+  `custom_tool_call` tool calls, and file activity parsed out of the `apply_patch` body or inferred
+  narrowly from shell redirects and pager commands.
+- **Schema v1 envelope** shared with the server, with a contract test in `npm test`. It always asserts
+  the 18 event types and that the envelope carries no tenancy fields; the field-by-field comparison
+  against the server's canonical `EVENT_SCHEMA.json` runs only when the server repository is checked
+  out alongside this one, and is skipped otherwise. This release emits 14 of the schema's 18 event
+  types.
+- **Three privacy modes**, enforced locally before the spool write: `metadata` (counts and timings;
+  titles and messages stripped), `analytics` (adds locally derived session titles — the default), and
+  `full` (which still requires `privacy.prompts: full` before any prompt text is uploaded).
+- **Built-in secret redaction**, 15 patterns covering Anthropic, OpenAI, GitHub, Slack, Stripe, AWS
+  and Google credentials, private key blocks, JWTs, bearer headers, credentials in URLs,
+  secret-shaped environment assignments, and long hex strings. Organization patterns are fetched
+  from the server and applied alongside them; a malformed org pattern is skipped, not fatal.
+- **Path privacy** — `never`, `relative` (default: relative to the project root, `~` for home, last
+  two segments for anything else) and `absolute` (opt-in). The project root itself is transmitted
+  only under `absolute`; repositories correlate by a SHA-256 of the normalized remote URL.
+- **Project exclusion** by prefix via `privacy.excluded_projects`; an excluded project emits no
+  events at all.
+- **Offline-first SQLite spool** (WAL) at `~/.agentstrack/spool.db`, holding both the queue and the
+  per-file `(path, inode, offset)` read checkpoints — so a restart resumes mid-file, a replaced or
+  truncated file is re-read from the start, and nothing is lost to a network outage.
+- **Batched gzip upload** — `upload.batch_size` events (default 100) every `upload.interval_seconds`
+  (default 30), gzipped above 1 KB, idempotent on `event_id`. A `413` halves the batch size and
+  recovers on success; retryable failures back off exponentially with jitter, capped at 5 minutes.
+- **Normalized token accounting** across both agents — `input_tokens`, `cached_input_tokens`,
+  `cache_creation_input_tokens`, `output_tokens`, `reasoning_output_tokens`, with reasoning treated
+  as a subset of output rather than added on top.
+- **Git enrichment** — branch and project root read straight out of `.git`, plus `git.commit` events
+  with SHA and diffstat for commits landing inside a session's window. The remote URL is never sent,
+  only a SHA-256 of its normalized form, so ssh and https clones of one repo correlate.
+- **CLI**: `login`, `logout`, `start`, `stop`, `status`, `doctor`, `config`, `sync`, and
+  `service install | uninstall`. Background service via launchd (macOS) or a systemd user unit
+  (Linux); neither needs root.
+- **`agentstrack sync --dry-run --print`** to see the exact post-redaction JSON that would be
+  uploaded, and **`agentstrack config --show-effective`** to see the policy actually in force.
+- **`agentstrack doctor --json`** structured diagnostics, containing no API key and no payloads —
+  safe to paste into a bug report.
+- **`AGENTSTRACK_HOME`** to relocate all local state (config, spool, log, pidfile).
+- Config at `~/.agentstrack/config.yaml`, written mode `600`. An invalid config is a hard error
+  rather than a silent fallback to defaults, so a typo cannot quietly widen your privacy mode.
+
+### Security
+
+- `organization_id` and `user_id` are absent from the event envelope by design; the server derives
+  both from the API key, so a collector cannot name its own tenant.
+- The organization privacy policy acts as a ceiling: a local config may be stricter, never looser.
+  Both `login` and the daemon clamp through one shared function.
+- The collector log records counts, queue depths and event ids — never prompts, code content, or
+  API keys.
+
+### Known limitations
+
+As released. Several of these have since been fixed — see `## Unreleased` above, and
+[ROADMAP.md](./ROADMAP.md) for what is still outstanding.
+
+- `tracking.idle_timeout_seconds` and `tracking.process_metrics` are accepted and validated but not
+  yet used by the collector; time accounting is derived server-side from the event stream.
+- `privacy.shell_arguments: full` behaves the same as `redact_secrets` — secret redaction is applied
+  to commands unconditionally.
+- `session.ended`, `heartbeat`, `model.request` and `git.branch_changed` exist in the schema but no
+  adapter emits them yet, and no adapter populates `task_category`.
+- The backfill window is fixed at 7 days and is not configurable.
+- `event_id` is generated per enqueue rather than derived from content, so re-reading a truncated
+  transcript would produce duplicate events server-side. Retrying a batch is unaffected.
+- The service installer supports launchd and systemd only. `agentstrack start --foreground` works
+  anywhere Node 20+ does.
+
+[Unreleased]: https://github.com/agentstrack/collector/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/agentstrack/collector/releases/tag/v0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.