Block a user
Cross-client phase 1: ClientSpec adapter, no behavior change (#5)
the_og
pushed to feat/5-client-adapter-refactor at the_og/better-claude-config
2026-08-03 22:53:55 -04:00
the_og
created branch feat/5-client-adapter-refactor in the_og/better-claude-config
2026-08-03 22:53:55 -04:00
${VAR} / .env expansion for env values — keep secrets out of the config file
the_og
deleted branch feat/76-env-var-refs from the_og/better-claude-config
2026-08-03 22:41:14 -04:00
feat: author ${VAR} references, gated on whether the client expands them (#76)
📌 STATUS — better-claude-config
"Move to environment variable" action — convert a plaintext secret into a ${VAR} reference in place
feat: author ${VAR} references, gated on whether the client expands them (#76)
the_og
created branch feat/76-env-var-refs in the_og/better-claude-config
2026-07-20 13:46:16 -04:00
${VAR} / .env expansion for env values — keep secrets out of the config file
Blocker resolved — and the answer splits by client
I said not to build the expander until we knew whether the client does this itself. Checked Anthropic's current docs. **Claude Code expands…
the_og
deleted branch fix/78-79-update-visibility from the_og/better-claude-config
2026-07-20 12:53:04 -04:00
the_og
deleted branch fix/72-73-load-crash-and-set-loss from the_og/better-claude-config
2026-07-20 12:53:03 -04:00
"Check for updates" is unreachable in practice — buried in About, and on macOS About isn't where the app says it is
fix: make the update checker visible — persistent banner + a Help menu item (#78, #79)
Update notification is ephemeral — the status line that announces it gets overwritten by the next UI action