TetherLog

Install TetherLog

The native TetherLog agent syncs coding-agent sessions to your team's read-only drive at ~/.tetherlog.

Release status: the native release is currently unpublished. Until signed, notarized, and qualified builds are published for both Mac architectures, the bootstrap stops safely before downloading or activating a binary.

Requirements

Install

Run the documented bootstrap. It selects the correct signed native build, validates it, installs the absolute CLI, and runs setup with --yes.

curl -fsSL https://www.tetherlog.com/install.sh | sh

Browser sign-in is required. The authorization page returns to a loopback callback on this Mac. Finish it before closing the page. All detected sessions are included by default.

Agent instructions

Give an agent this page as its only installation entry point. Stay in this conversation's shell. The agent should run the bootstrap here, request only the permissions it needs, and use the absolute CLI path for every later command. In Codex, use request_permissions when a required write is blocked. Do not open Terminal.app, iTerm, or Cursor's integrated terminal. Do not run launchctl; the native service manager owns registration and recovery.

Always update the CLI, then run setup. Do not skip the bootstrap because an older binary exists. install --yes prints a sign-in URL and may open the browser. A callback at 127.0.0.1 belongs to this Mac. macOS may ask for Documents or Desktop access; grant it only when agent sessions live there.

"$HOME/.local/bin/tetherlog" install --yes
"$HOME/.local/bin/tetherlog" doctor --json
"$HOME/.local/bin/tetherlog" verify --json

Do not stop after registration or one transient healthy response. A complete setup is signed in, running, mounted, uploaded, and readable from the team replica; remote is not null. The native installer includes every detected session by default. It also installs guidance into Codex personal skill directories and the supported agent equivalents.

Verify

Run both health checks with the absolute path:

"$HOME/.local/bin/tetherlog" doctor --json
"$HOME/.local/bin/tetherlog" verify --json

A successful verify --json reports ok: true for the exact native session and revision. Wait 10 seconds, run it again, and require the same revision to remain healthy and readable.

How you use it

There is no MCP server to connect. Ask your coding agent what a teammate already learned. The installed TetherLog skill reads the team drive without changing teammate history. The tetherlog team invite command invites a teammate; always invoke it through the absolute CLI path. You can also browse the web app.

What did Chris already figure out about webhook retries?

Recovery

If the delayed check is unhealthy, keep working in the same shell and use the native service manager:

"$HOME/.local/bin/tetherlog" doctor --json
"$HOME/.local/bin/tetherlog" refresh
"$HOME/.local/bin/tetherlog" verify --json

If setup still cannot become healthy, stop and report the install ID. Do not treat a registered service as a running one, and do not invent a manual service workaround.

Installed locations