Work with the Assistant

Lead with the outcome

Describe what should become possible, who or what will use it, and the result it should return.

Less useful: “Connect an LLM to MongoDB.”

More useful: “Create a capability that answers product-catalog questions, returns the matching records, and never modifies the catalog.”

The second request gives Elyxis an outcome, output expectation, and safety constraint while leaving room to reuse available capabilities.

Add constraints that change the result

Useful constraints include:

• required input and output shape;
• read-only versus mutation behavior;
• latency, data-boundary, or provider requirements;
• reusable versus one-time execution; and
• facts that must appear in the returned evidence.

Avoid listing implementation details that do not affect the outcome. They can prevent Elyxis from reusing something that already works.

Elyxis uses the Environment selected in your session when your request does not name one. Check it with /context; you do not need to repeat its name in each request.

Refine the active request

Use short follow-ups when they clearly modify the current task:

Only include active products.
Return the source product IDs too.
Keep the catalog read-only.

Start a new session with /new when you switch to unrelated work. Use /history when you are unsure what conversation context remains, and /context to inspect selected durable resources.

Correct before confirming

If a confirmation proposes the wrong action, reject it and state the correction. Do not approve first and try to repair the request afterward.

Use concrete payloads

When your task includes text, JSON, a schema, or an API description, provide the exact payload and say what it represents. Keep secrets out of conversational requests; use approved Elyxis configuration and key-store mechanisms instead.

Know when to reset

• /clear removes conversation memory within the current session.
• /new starts a fresh Assistant session and is the clearest boundary for unrelated work.
• /context lets you verify resource bindings before a sensitive or environment-specific request.