Project / Beta testing

Bring evidence.

The most useful contribution is a clear account of what you tried, what happened, and what should have happened.

Founder-stage workflow

How to help today

CEX is not an open-source project. The reliable contribution channels are direct beta feedback and reproducible bug reports.

  • Test a real task and describe where continuity failed.
  • Try a stronger or different model and compare the runtime behavior.
  • Report confusing permissions, missing state, packaging failures, or unclear recovery.
  • Point out documentation that assumes knowledge a new user would not have.

Email beta feedback

Make it reproducible

A useful bug report

  1. Name your operating system and CEX version.
  2. Describe the task and the exact steps that led to the problem.
  3. Say what you expected and what happened instead.
  4. Attach a screenshot or redacted log when it adds evidence.
  5. Remove credentials, tokens, personal data, and private workspace content.
For security issues, use the private channel.

Do not publish exploitable details. Follow the security reporting guidance.

Build with CEX

Extensions, not runtime forks

You can build projects, agents, skills, tools, and workflows through the interfaces CEX intentionally provides. Those creations are yours. The core runtime repository remains private and is not accepting public pull requests.

CEX may publish selected SDKs, schemas, examples, or interoperability specifications under separate terms later. Publishing those pieces would not make the proprietary CEX runtime open source.

Community

Keep the work constructive

Be direct about code and behavior without attacking the person behind it. Respect privacy, do not share secrets or private traces, and give people enough context to reproduce a claim. The Discord community link will be added when the server is ready.