Running ClaudeConnect tests breaks local ClaudeConnect context directory

Resolved 💬 2 comments Opened Jan 15, 2026 by bstadt Closed Jan 16, 2026

Bug Description

Running the ClaudeConnect test suite appears to corrupt or override the local ClaudeConnect configuration, causing subsequent ClaudeConnect operations to point to a temporary pytest directory instead of the user's actual context directory.

Error

After running tests, ClaudeConnect reports:

Your context directory is: /private/var/folders/w2/frmxns952d781kx73nx40ltr0000gn/T/pytest-of-bstadt/pytest-10/test_test_user_can_operate_bef0/context

Instead of the expected user context directory.

Expected Behavior

Running tests should use isolated/mocked context directories and not affect the user's local ClaudeConnect configuration.

Environment

  • macOS
  • Running from: /Users/bstadt/root/claude

Possible Cause

The test fixtures may be setting environment variables or writing to config files that persist after test completion, rather than being properly cleaned up or isolated.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗