Document CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- cli, documentation
Research direction
Start by running abctl configure claude-code status and verify the CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 setting. Document that Cortex enables this setting and that it can disable Claude Code's nonessential features; done means users can find and understand this behavior.
Written by the indexing model from the issue text.
Description
abctl configure claude-code status shows, among other things
CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1
We don't document that we do this.
If anyone is using any of the nonessential features of Claude Code, enabling Cortex loses those features, silently.
- Dominant language
- Go
- Stars
- 15
- Forks
- 41
- Avg merge
- 10h 30m
- Merged PRs (30d)
- 245
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rossoctl/cortex
-
feedback laptop
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
rossoctl/cortex#1116 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
helm (Go) fails TLS through Cortex proxy on macOS — CA not in System keychainPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
duplication
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openvibely/openvibely#1443 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
keyxmakerx/Chronicle#1179 ·
Maintainers usually reply within 1 day
-
raised-by:worker
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
medici-finance/assay#2486 ·
Maintainers usually reply within 1 day
-
area/testing kind/bug triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cozystack/cozystack#4841 · 1 reaction ·
Maintainers usually reply within 2 days