SessionSeal

Who it's for

Engineering leads at 5-50-person software companies who allow Codex CLI, Claude Code, or Aider on developer machines and currently rely on git log, shell history, and manual code review.

The problem

Time and legal: after an unwanted change, secret exposure, or unexpected network call, reconstructing what the coding assistant did takes days and lacks tamper-evident evidence for SOC 2, customer security reviews, or incident postmortems.

How to build it

Linux CLI wrapper plus local report viewer; launches Codex CLI, Claude Code, or Aider inside a traced session, records file/process/network events, and renders an HTML/PDF report without sending session data to a cloud service.

How it makes money

Engineering or security teams pay $18-$25 per developer per month for signed session packets and network allowlists; free shell history and git logs do not capture process/network events or produce tamper-evident reports.

Why it doesn't exist yet

Incumbents skip neutral local audit because it adds friction and exposes cross-vendor assistant behavior; an indie can ship an OS-level wrapper that works across terminal coding tools without needing vendor APIs.

First users

First 10 users come from the HN Codex Linux preview thread and r/LocalLLaMA; security-conscious team leads install it to produce one signed packet for a risky repo before allowing broader assistant use.

Build size

1 person x 10 weeks or 2 people x 6 weeks; includes Linux CLI wrapper using eBPF/auditd, local SQLite event log, network allowlist blocking, Ed25519 signing, and HTML/PDF report generation; excludes Windows, macOS, IDE plugins, cloud policy console, and team analytics.

Biggest risk

OpenAI, Anthropic, or GitHub ships native signed session audit and network/command controls inside their official Linux coding tools.

Conditions for a hit (all 3 required)

• Given a session started with a single CLI command, it writes a JSONL event log containing process starts, file writes, and network connections, with each entry chained by SHA-256 hashes.
• If a traced process attempts a network connection to a host outside the configured allowlist, the connection is blocked and a violation event appears in the session log within 5 seconds.
• Within 60 seconds of session end, it outputs an HTML or PDF report listing command timeline, changed-file hashes, network destinations, and an Ed25519 signature verifiable with a public key.

How it's judged (in 6 months)

By judge date, a public GitHub repo with >=1,000 stars whose README explicitly offers all three: Linux CLI wrapper for terminal coding assistants, signed session report, and network allowlist blocking; or a Product Hunt launch with those same three claims reaches daily top 5.(judgment date 2027-02-14)

AI self-confidence 45/100 — self-reported likelihood of meeting the criterion, not a business success rate