Simulearn Help: Your AI Coding Mentor is Here

Simulearn landed in your Sapior toolbox with a promise: **stop reading about errors and start living them**. It’s a fully sandboxed, browser‑native workshop where you debug real‑world infrastructure hiccups, race conditions, and misconfigured APIs—all with an AI mentor that doesn’t just suggest fixes, it teaches you *why*.

That mentor is the heart of Simulearn. But when you’re inside a scenario and the clock is ticking, knowing how to ask for help changes everything.

How Simulearn’s help works

The Simulearn environment clones the same runtime you’d see in a Vercel preview deploy or a Browserbase session: instant logs, live network tab, and a persistent shell. Its AI tutor is context‑aware, not just a general‑purpose LLM. It reads your recent commands, your current file diffs, and the scenario’s objective. When you hit a wall, you’re not starting from zero.

The `/help` command (and when to use it)

In the Simulearn terminal or the in‑app chat panel, type `/help` followed by a question or a natural language description of what you’re trying to do. For example:

/help why is the Node.js event loop blocking in the order‑processing scenario?

The tutor will respond with a diagnosis tailored to your exact state—down to the line of code that’s stalling the event loop. This isn’t a generic Stack Overflow answer; it’s a pairing session with a senior engineer who has read the whole repo.

Contextual hints (the lightbulb icon)

If you prefer not to interrupt your flow, click the lightbulb icon in the top‑right bar. Simulearn’s AI scans your last three minutes of activity and offers a nudge—a hint, not a spoiler. The hints follow a progressive‑disclosure model:

**Level 1**: A concept reminder (“Consider how `process.nextTick` queues callbacks”).

**Level 2**: A diagnostic probe (“Check the `uncleared` interval in `server.js`”).

**Level 3**: A partial solution snippet you can apply yourself.

You control the depth. Many engineers stay at Level 1 to preserve the learning tension.

Getting help from the community

Simulearn scenarios are shareable via a temporary link. If you want a second set of eyes from a colleague or the Sapior Discord, open the **Session menu → Share snapshot**. The recipient sees a read‑only replay of your environment; they can annotate, highlight stack traces, and send recommendations back. This is how teams at [Linear](https://linear.app) and [Vercel](https://vercel.com) onboard new developers: they pair on Simulearn scenarios that mirror their actual production incidents.

Troubleshooting common Simulearn roadblocks

“The AI tutor isn’t responding to my /help query.”

First, make sure your session is active (the status dot in the bottom‑left should be green). If the tutor stalls, run `@reset-tutor` in the terminal—this clears the conversation memory without losing your scenario progress. On rare occasions, a large log output can exceed the context window; collapse unnecessary panels before asking a question.

“I can’t see the database or the third‑party API results.”

Simulearn sandboxes network calls, but it expects you to start mock services explicitly. Each scenario README lists the required `npm run` commands. If you skipped one, the `/help` command will automatically detect the missing dependency and suggest a fix.

“The environment feels slow.”

Simulearn runs on [Browserbase’s](https://browserbase.com) headless infrastructure, so latency is similar to a real CI runner. If you’re experiencing lag, check the performance tab; you can adjust the container size from **Settings → Resources** to allocate more CPU—especially useful for data‑heavy scenarios.

Advanced help workflows

**Custom scenario debugging**: If you’ve imported your own repository as a scenario, the AI tutor bases its guidance on your README and test suite. Use `/help @tests` to get a roadmap of failing tests and the lines most likely causing them.

**Voice‑first help**: In the Sapior desktop app, you can invoke the tutor by voice (⌘+Shift+H). The tutor’s responses will be read aloud, preserving the screen space for your code.

**Pinning answers**: When the tutor shares a critical snippet, click the pin icon to keep it on your sidebar throughout the session. This is how you build your own “living documentation.”

Simulearn’s help system isn’t a crutch—it’s a designed part of the learning loop. Use it often, especially when you think you *should* know the answer. That’s where the real growth happens.