Spec without daemon bookkeeping.

One command turns Spec on.Every project. Every agent. Every PR.

Discover your repositories once, then run spec on from anywhere. Spec connects and watches every project without publishing its contents, gives the team one all-agent activity feed, and turns open PRs into a cloud-or-teammate review queue.

Open workspaceLive review
Install
curl -LsSf https://spec.lightreach.io/install.sh | sh
  • System-wide
    discover and watch
  • All agents
    one activity feed
  • SHA-bound
    cloud PR review
Spec: docs and prompts in-repo, versioned on the branch, with status for review and compile
Platform

Discover. On. Activity. Review.

Four human-scale commands cover the daily loop. Publishing bundle content and compiling remain explicit, so turning collaboration on never uploads source by surprise.

How teams use it

Watching is not publishing.

spec on creates or resolves only the Cloud identity needed by the watcher. spec publish is the separate content upload. That boundary keeps setup simple without turning an everyday switch into an accidental data transfer.

Enter the workspace
Three durable pillars
01

One machine-wide switch

Run spec discover once, then spec on from anywhere. Spec reconnects every registered project and starts every watcher without publishing repository content.

02

Every PR in one list

spec prs finds open pull requests across watched projects. Request your SHA-bound Compress cloud reviewer or a teammate from the project team.

03

One team activity feed

spec activity streams Codex, Claude Code, Cursor, and Compress turns across the workspace. Add --show-tool-runs only when you need the longer trace.

Spec Live

Watch every agent across the team.

Every prompt and every AI reply across every bundle you can see, in one pane. Spot a dangerous command, a vague handoff, or a leaked secret as it lands.

spec activity
● connected · workspace (all bundles) · streaming team prompts

 USER  @bayocotjc · prompt to claude_code · main · 12:08:11 · acme/widgets
  cwd ~/code/widgets  touched billing.py, auth.py  session 8a13c2
  please refactor billing.py to use the new auth helper

  ⛔ AUTO destructive-verb "refactor" + multi-file scope without tests in scope
     → spec team flag 4711 --kind warning --note 'refactor + multi-file scope'

  AI   claude-sonnet-4 · replying to @bayocotjc · in claude_code · main · 12:08:14
    here is the plan: read auth.py first, then thread the helper
    through billing.py without changing the public signature…

spec> /flag 4711 warning audit the refactor scope
  ✓ flagged #4711 as warning - audit the refactor scope
01

Prose by default

Full assistant narration from Codex, Claude Code, Cursor, and Compress stays readable. Add --show-tool-runs only when you need expanded calls, code blocks, and command traces.

02

Auto-critic, runtime toggleable

Destructive verbs, test bypass, leaked secrets, vague intent - flagged inline on both prompts and replies. --notify rings the bell on block-severity hits.

03

Act without leaving the pane

Slash commands stream alongside the feed: /flag, /summarize 2h, /focus @handle, /search, /replay 10m.

Read the Spec Live contractIn-pane commands
Docs

Everything in one handbook

Discover, connect, activity, PR review, publishing, hooks, and bundle layout in one place.

Open documentation
CLI

Install in one paste

Copy the install script, run system-wide discovery once, then use spec on from any directory.

Install guide
Workflow

Four commands for the whole daily loop.

Discovery and watchers are machine-wide. Activity and PR review are workspace-wide. Publishing and compiling stay explicit when you actually need them.

Workflow

Three beats your team already knows, drawn as one continuous pipeline.

BundleGIT BRANCHfeature/auth-capturespec.yamlCONFIGdocs/product.mdDOCSprompts/main.promptsCAPTURERESOLVED ON SPEC PUSHAuthor on your branchMarkdown, prompts, spec.yamlversioned like code.01 · LOCALSpec CloudREAD-ONLYBUNDLEbilling-apiBRANCH · COMMITfeature/auth-captureabc12f7 · spec pushReview on this branchAlign before mergeStore and inspect bundles in the browser,with branch review when your team is ready.02 · CLOUDCompileLOCALspec compile$ spec compile --locked▸ resolve bundle · spec.yaml OK▸ merge prompts · synthesize graph…✓ wrote .spec/compile-prompt.mdOUTPUT.spec/compile-prompt.mdINFERENCE · YOUR STACKClaude Code · IDE · AgentRun where you already shipArtifact stays in-repo.Run it with tools you trust.03 · LOCAL
01

Discover once

spec discover inventories saved workspaces system-wide, initializes selected repositories, and remembers existing Spec bundles too.

02

Turn Spec on

spec on connects fresh projects without uploading files, starts every watcher, and reports Watching, Stopped, or Needs connection.

03

Watch and review

Use spec activity for the team feed, spec prs for the work queue, spec review for cloud or teammate review, and spec publish only for content upload.

Why Spec

Intent in Git. Alignment in Spec. Execution at your desk.

We focus on the bundle contract and the review moment so your team can keep using familiar Markdown, Git, and local inference while Spec adds structure, not another black box.

Start with a project
docs/, prompts/, and spec.yaml in version control
Branch review before merge, without leaving Spec
Compile artifacts you run with Claude Code or your IDE