Beta testing guide

What to expect

The private beta is a chance to explore Elyxis, try useful workflows, and help improve the product. Before requesting access, here is what participation involves:

• Ready to try: Beta Testing includes sample data and configured connections. Sign in and try the prepared scenarios—no database setup or personal OpenAI key is required.
• Your own workspace: each tester receives a separate tenant with isolated databases and configuration, plus an empty Sandbox for building from scratch. Your experiments affect your tenant, without changing another tester’s workspace.
• Optional customization: you can try your own OpenAI key or MongoDB data. These are the supported configuration options for now; the supplied scenarios work with the prepared setup. See the connection requirements below before bringing your own data.
• An evolving product: features and behavior may change, and some requests or configuration changes may fail. Explore the scenarios, try variations, and tell us what worked or got in your way. The feedback checklist explains what helps us investigate.

Your invitation includes the CLI package and access instructions. Install the CLI, sign in, and choose Beta Testing for your first session.

Two Environments, two starting points

The sample data is already loaded in Elyxis’s MongoDB cluster, and the connection is configured for you. That database is private. You do not need to create a database, supply a MongoDB URL, or bring an OpenAI key to try the prepared scenarios.

The earlier recorded walkthrough labels the prepared Environment Demo. In your beta workspace, choose Beta Testing for that role.

Explore the sample business data

The prepared onboarding scenario follows a consulting team helping a client get started. The answer is spread across related business records:

The supplied baseline contains 25 fictional clients, 40 projects, and 695 related records. It includes four detailed starting scenarios:

The sample businesses and projects reference lists all 25 clients and 40 projects, explains how the data fits together, and provides copyable queries for different businesses. Use project IDs to distinguish similarly named projects. Its counts and expected findings describe the original data; your tenant may differ after changes.

Start with Willowbrook Service Desk Onboarding, the scenario shown in the website walkthrough. It uses dated sample records, so the examples below use fixed dates instead of “today.”

Before running a scenario, check the selected Environment and inspect the available Apps:

/context

List all apps.

Look for Beta Testing in the context and Onboarding Readiness Review in the available Apps. If a supplied resource is missing or unavailable, reply to your beta invitation for help.

Requests use the Environment already selected in your session. You do not need to repeat its name in each request.

Review onboarding readiness

Ask for a review with evidence and a draft follow-up:

Review onboarding readiness for Willowbrook Service Desk Onboarding
as of 2026-10-14T12:00:00Z.
Identify missing client documents, documents awaiting internal approval,
blocked work, and the latest inbound client communication.
Cite supporting record IDs and responsible people.
Draft a client follow-up for review without sending it.

For the supplied scenario, check that the answer:

• identifies the signed statement of work and service desk access authorization as missing;
• recognizes that the requirements pack was received on October 12 and still needs internal approval;
• separates the client’s next actions from the team’s internal approval work;
• explains the blocked work and cites supporting records; and
• provides a follow-up draft for review, without claiming it sent a message.

Wording can vary. Check the facts and supporting evidence rather than expecting an identical response. If you have changed the sample data or configuration, the result may also change.

Compare an earlier point in time

In the same session, ask for the earlier view:

Run the same onboarding readiness review for
Willowbrook Service Desk Onboarding as of 2026-10-11T12:00:00Z.
Explain what changes in the findings and the draft client follow-up.
Do not send anything.

At this earlier point, the requirements pack had not yet arrived. It should appear among the missing client documents. The follow-up should reflect what was known on October 11, rather than using the later receipt as if it had already happened.

This is a useful test of follow-up requests, reuse, and reasoning over dated records. Use /context to check selected resources and /history to review the conversation.

Try your own variations: ask for a shorter summary, request the evidence behind a finding, or focus on the responsible people. Report unsupported claims, missing evidence, unexpected clarification questions, or a result that ignores your requested date.

Experiment with your own configuration

Custom configuration is optional. For now, beta customization supports OpenAI and MongoDB:

“Reachable over the public internet” describes network connectivity; it does not mean allowing unauthenticated database access. Ask the beta team for the connection requirements before changing network access rules. Your own provider accounts may incur charges.

These requirements apply when connecting your own data. The supplied sample database is already connected privately and needs no setup from you.

Use Sandbox for a fresh setup. Prepare the necessary Settings and Keystore references before following the capability creation tutorial. Other integration setup is outside the supported beta customization scope for now.

You can also experiment with the configuration in Beta Testing. Changes may interrupt its prepared scenarios. Updating Settings does not automatically reconfigure an already built or running App; review any required rebuild or materialization and verify the result. If you need help restoring the supplied setup or sample data, reply to your invitation. Do not assume an automatic reset.

Share useful feedback

Reply to your beta invitation with:

• the Environment and the request you entered;
• what you expected and what actually happened;
• whether you were using the supplied setup or had changed data or configuration;
• the time of the attempt and any relevant App or capability identifiers; and
• a screenshot or short recording when it helps explain the problem.

Exclude API keys, database passwords, access tokens, and your local CLI credential file. Describe the issue before retrying an action whose outcome is uncertain.

We welcome feedback on successful results too: what was useful, what took too much explanation, and which capability you would like to try next.