Knowledge.Dev Docs

Troubleshooting

Use this page when the local setup, MCP connection, or playground session is not working as expected.

Start With the Local Setup

If you are still setting things up, begin with the Launcher.

Make sure you have:

  • installed the launcher with cargo install knowledge
  • run knowledge at least once so it can prepare the correct binary for your system
  • signed in with knowledge login if you expect access to the full course library

If you are unsure whether you are already signed in, check with:

knowledge status

Check the MCP Connection

If the agent cannot open courses or does not seem to understand the lesson workflow, the MCP Server is usually the first thing to verify.

Make sure:

  • the server was added to the same agent you are using now
  • it was added from the folder where you want to work on the course
  • the agent session was started with that MCP connection available

If you need to connect it again, follow the MCP Server setup page.

If the Playground Does Not Start

If playground <id> does not start the course correctly:

  • confirm that you are inside a clean folder for that course
  • confirm that MCP is connected in the agent session
  • confirm that the playground ID was copied from the correct playground description page
  • start a fresh agent session and try the same prompt again

The expected flow is described in Playground Workflow.

If Access Looks Wrong

If the course library or access level does not match your account:

  • confirm that you signed in with the correct knowledge.dev account
  • run knowledge status and verify the current state
  • if needed, run knowledge logout and then knowledge login again

This usually fixes stale local session state.

Still Stuck?

When you ask for help, include:

  • which agent you are using
  • whether the MCP Server is connected
  • the playground ID you tried to open
  • the exact command or prompt you used
  • what happened instead of the expected result

Then reach out through:

If you have questions, visit our Discord

← FAQ