Skip to content

apply error logging philosophy: distinguish operation vs program errors#1

Merged
clord merged 1 commit intomasterfrom
claude/update-claude-error-handling-jX6lW
Dec 21, 2025
Merged

apply error logging philosophy: distinguish operation vs program errors#1
clord merged 1 commit intomasterfrom
claude/update-claude-error-handling-jX6lW

Conversation

@clord
Copy link
Owner

@clord clord commented Dec 21, 2025

  • Add error logging guidelines to CLAUDE.md based on sysadmin perspective:
    errors should only indicate things that need fixing by the operator
  • Change password verification failures from error! to warn! (expected operation)
  • Change HTTP client request rejections from error! to warn! (client issues)
  • Change automation evaluation failures from error! to warn! (runtime issues)

Keeps true program errors (token generation, hardware init, config parse)
as error! since those indicate actual problems needing operator attention.

- Add error logging guidelines to CLAUDE.md based on sysadmin perspective:
  errors should only indicate things that need fixing by the operator
- Change password verification failures from error! to warn! (expected operation)
- Change HTTP client request rejections from error! to warn! (client issues)
- Change automation evaluation failures from error! to warn! (runtime issues)

Keeps true program errors (token generation, hardware init, config parse)
as error! since those indicate actual problems needing operator attention.
@clord clord force-pushed the claude/update-claude-error-handling-jX6lW branch from 25b1e2d to 732808c Compare December 21, 2025 23:44
@clord clord merged commit 3820f97 into master Dec 21, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants