Use Ocelot

Use this guide when

Use this page when you want to work through EnderDash chat instead of jumping across several panels manually.

Before you begin

Make sure you know:

• whether the task is tied to one server or the whole organization
• which Ocelot tools are enabled in that organization
• whether the task needs approval before Ocelot acts

If you are not sure what Ocelot can touch, start with Configure Ocelot Guardrails or ask an admin to check the settings.

Start with the right scope

• Pick a specific server when the task is runtime-specific.
• Work at the organization level only when the task genuinely spans several servers or shared settings.

This keeps Ocelot's context smaller and usually produces better answers.

Ask Ocelot to inspect before it changes anything

For operational work, the safest pattern is:

1. inspect the current state
2. summarize the finding
3. propose or execute the next action

That sequence is more reliable than asking for a fix before the problem is understood.

Keep requests concrete

Good prompts name the object, the action, and the expected result.

Examples:

• Show me the last 100 console lines with errors only
• Find every file that mentions 25565
• Check whether the server is falling behind on TPS
• Show me the LuckPerms nodes for the moderator group
• Is Chunky still pregenerating the overworld?

Review sensitive actions

Depending on the organization settings:

• high-impact actions can require confirmation
• some tool groups can be disabled entirely
• emergency stop can block Ocelot activity until an admin re-enables it

If Ocelot refuses a request, that is usually a policy or permission decision, not a chat failure.

Save useful findings

If the result should stay attached to the workspace, ask Ocelot to save a note. Notes are useful for:

• recurring operational facts
• server-specific gotchas
• troubleshooting outcomes the team will need later

If Ocelot stops early

Check these first:

• the organization still has available Ocelot usage
• the required tool group is enabled
• you are working in the right server or organization scope

Admins can review those controls in Configure Ocelot Guardrails.