CLROOM support

Support

Clean Room Launcher (CLROOM) is a small open-source project. There is no paid support contract or guaranteed response-time SLA.

Before asking for help

Start with the public documentation:

• Troubleshoot CLROOM
• Install CLROOM
• Clean-launch walkthrough
• Problem and search-language index
• When to use CLROOM — and when not to
• Codex and CLROOM
• Claude Code and CLROOM
• Current limitations
• Verify a CLROOM release
• Privacy and data flow

If you do not know the provider’s exact term, use the problem index first. It maps common symptoms and alternate wording to the canonical technical answer.

Bug reports and usage questions

Use GitHub Issues for non-sensitive bugs, documentation gaps, compatibility questions, and feature requests.

For a useful technical report, include only the minimum safe information needed to reproduce the problem:

• CLROOM version;
• macOS / architecture;
• Codex or Claude Code version;
• exact CLROOM command with secrets removed;
• expected behavior;
• observed behavior;
• a minimal reproduction if available.

Do not paste credentials, provider tokens, prompts, transcripts, private repository contents, unrestricted environment dumps, or home-directory listings.

Security vulnerabilities

Do not put vulnerability details or sensitive reproductions in a public issue.

Use the process in SECURITY.md and the repository Security policy.

Provider behavior

CLROOM support claims are version-, platform-, and path-specific. Before reporting a provider difference, check the current provider page and configuration matrix.

A newly documented Codex or Claude Code capability does not automatically mean CLROOM has qualified that capability.

Contributions

For code or documentation changes, use CONTRIBUTING.md. Substantial product, provider, platform, release-path, or security-boundary changes should start with an Issue so scope and evidence can be discussed before implementation.