ttyd: drop FORGE_CHANNEL/CLAUDE_CHANNEL #27

Merged
pedromcaraujo merged 1 commit from ttyd-drop-forge-channel-clean into main 2026-08-08 12:07:13 +01:00

Summary

Removes both per-session channel env vars added in #24.

Nothing in this repo, in the nixos config, or in the statusline script ever
read either one — verified by grep across both checkouts. They were pure
footgun: -e applies only when a session is created, and new-session -A
re-attaches to a live session without touching its environment. Any channel
that outlives a config change keeps a stale value that still looks
authoritative — which is exactly how the earlier FORGE_CHANNEL=nixos
leak (#87/#88) misled us.

The tmux session name (tmux display-message -p '#S') is the one signal that
cannot drift; the comments now say so.

Test plan

  • nix flake check passes
  • grep -r 'FORGE_CHANNEL\|CLAUDE_CHANNEL' returns nothing
  • After a lock bump on nixos + session recycle, channels still start correctly
## Summary Removes both per-session channel env vars added in #24. Nothing in this repo, in the `nixos` config, or in the statusline script ever read either one — verified by grep across both checkouts. They were pure footgun: `-e` applies only when a session is *created*, and `new-session -A` re-attaches to a live session without touching its environment. Any channel that outlives a config change keeps a stale value that still looks authoritative — which is exactly how the earlier `FORGE_CHANNEL=nixos` leak (#87/#88) misled us. The tmux session name (`tmux display-message -p '#S'`) is the one signal that cannot drift; the comments now say so. ## Test plan - [x] `nix flake check` passes - [x] `grep -r 'FORGE_CHANNEL\|CLAUDE_CHANNEL'` returns nothing - [ ] After a lock bump on nixos + session recycle, channels still start correctly
ttyd: drop FORGE_CHANNEL/CLAUDE_CHANNEL — nothing reads them, and they go stale
All checks were successful
CI / check (pull_request) Successful in 7s
bba7e63043
Both were set per-session by #24. Nothing in this repo or in the nixos
config ever read either one, so they were pure footgun: `-e` applies only
when a session is created, and `new-session -A` re-attaches to a live
session without touching its environment. Any channel that outlives a
config change therefore keeps a stale value that still looks authoritative.

The tmux session name (`tmux display-message -p '#S'`) is the signal that
cannot drift; the comments now point at it.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pedromcaraujo/forge!27
No description provided.