Skip to content

Commit c67d129

Browse files
aster-voidclaude
andcommitted
meta: clarify local vs production log access in CLAUDE.md
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 1335c6b commit c67d129

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

CLAUDE.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ bun tidy # runs all automated checks and fixes as necessary (type+format+lint)
112112
# devenv controls
113113
bun up # spin up devenv server (usually already done by user)
114114
bun down # stop it
115-
bun tail # !important tail the logs
115+
bun tail # tail LOCAL devenv logs only (not production)
116116
```
117117

118118
# Bun Commands
@@ -129,6 +129,10 @@ Always use `bun run <script>` to run `build` or `test`.
129129
The user (usually) uses devenv's process compose to manage processes.
130130
You may inspect `.devenv/processes.log` for the logs.
131131

132+
# Production
133+
134+
You have NO access to production logs. When you need to check prod logs, ask the user to check and copy-paste the relevant output.
135+
132136
# Verification Rules
133137

134138
run `bun type-check` whenever you write code.

0 commit comments

Comments
 (0)