Dept. of Human Enrichment · field equipment
One setup.
A robot on call.
Add reviewed lessons to the place you build. Choose your app, copy the right instruction, and keep going.
Coding agents can help with setup. Web chats use their own connector settings. Your app still controls trust and permissions.
Choose your appThe guided route
Let your coding agent help.
Copy this request. Paste it into the coding chat for your project.
Install HWTL for this project from https://human-wants-to-learn.dev/install. Use this app’s public setup steps and keep my other settings. Enable stable HWTL updates where this app supports them; keep normal permission prompts. Test a real robot lesson link. If setup needs a connector, a scope choice or a manual step, guide me through it. The agent needs setup tools. A plain web chat cannot install a local plugin from a prompt. Use the app guide below if it cannot make the change.
Claude Code needs a one-time marketplace auto-update choice. See Updates in its app guide below.
Your app. Its normal setup.
Where do you build?
Pick one route. You do not need to install every option.
Claude CodeNative pluginChecked: CLI 2.1.301 lifecycle
Automatic robot learning links in supported Claude Code responses. Recognition runs locally; the lesson opens on HWTL.
Install, scope, enable, disable and removal checks passed in isolated Claude Code 2.1.301 settings. Other versions and interactive rendering still need their own checks.
- Step 1
Open your project in Claude Code
Use the Claude Code conversation where you are building. The slash command below belongs there, not in a plain shell or claude.ai web chat.
- Step 2
Install HWTL and review the source
Paste the command, then follow Claude’s source, component and scope review. Reload plugins or start a new session when Claude asks.
Enter this slash command at the Claude Code prompt./plugin install hwtl --marketplace https://human-wants-to-learn.dev/releases/claude/marketplace.json
Other setup options
Choose the option and scope you want. Configuration blocks must be merged with existing entries.
claude plugin install hwtl --marketplace https://human-wants-to-learn.dev/releases/claude/marketplace.json --scope local claude plugin install hwtl --marketplace https://human-wants-to-learn.dev/releases/claude/marketplace.json --scope user HWTL plugin v0.7.13. Node 20.20.2+. In-chat install: Claude Code 2.1.275+; combined terminal install: 2.1.292+. Automatic annotations need MessageDisplay support.
Check that it is connected
claude plugin list --json Confirm HWTL is installed and enabled for the intended project. Then try the short request in the lesson-link check below.
Updates: what happens automatically?
In Claude Code, open the plugin manager, choose Marketplaces, then human-wants-to-learn-stable. Select Enable auto-update. Third-party marketplace updates are off by default.
Background updates can change the installed files while an open session keeps its loaded version. Reload plugins or start a new session to apply the update. Follow any new trust review.
/plugin /reload-plugins Remove only HWTL
Use the same scope you installed. This local-scope command removes only HWTL from the current project. If you installed with user scope, change local to user.
Remove the HWTL marketplace separately in Claude’s plugin manager only if you no longer need it. Keep unrelated sources and settings.
claude plugin uninstall hwtl@human-wants-to-learn-stable --scope local Something did not work
- If you already installed the private HWTL preview, check the plugin list before switching. Keep one HWTL entry enabled for this project; review its scope before disabling it.
- If the combined install command is unknown, update Claude Code or use its plugin manager and the official guide.
- If HWTL is installed but links are missing, check that it is enabled for this project, the host supports MessageDisplay, and the project has not disabled HWTL.
- Your learning profile can suggest an earlier foundation or hide a familiar concept. Code blocks are not rewritten.
CodexRemote MCPPublic preview · host test pending
Ask HWTL for a reviewed lesson through a tool. This route returns a learning link; it does not install passive inline annotations.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in Codex; use the check below.
- Step 1
Open this project’s Codex configuration
Merge the block below into .codex/config.toml in the project. Keep its other settings. Codex loads project MCP configuration only for trusted projects; use its normal trust review.
Merge this block into the settings file named in this step. Keep the existing server entries.[mcp_servers.hwtl] url = "https://human-wants-to-learn.dev/mcp" - Step 2
Start a fresh chat and test the tool
Enable HWTL in the app’s tool list if needed. Use the test request below, then follow its real lesson link.
Other setup options
Choose the option and scope you want. Configuration blocks must be merged with existing entries.
codex mcp add hwtl --url https://human-wants-to-learn.dev/mcp Check that it is connected
codex mcp list Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
Remove only HWTL
Remove only the mcp_servers.hwtl table from the configuration where you added it. Preserve other servers and project settings.
Something did not work
- Make sure the HWTL server is enabled in this app and that you are using the chat mode that can call tools.
- If HWTL is listed but no lesson appears, ask for hwtl_learn by name. A remote tool does not automatically add icons beside every term.
- A managed account may restrict custom servers. Use the app’s normal access process; do not bypass its policy.
CursorRemote MCPPublic preview · host test pending
Ask for HWTL lesson links from Cursor’s tool-enabled chat. This connection is an MCP server, not a published HWTL Cursor plugin.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in Cursor; use the check below.
- Step 1
Open the Cursor installer
The button below opens Cursor’s native MCP install flow. Review the server URL before accepting.
Add HWTL to Cursor - Step 2
Enable the tool in chat
Use Cursor’s tool-enabled chat and test HWTL. MCP calls follow Cursor’s normal approval controls.
Other setup options
Choose the option and scope you want. Configuration blocks must be merged with existing entries.
{
"mcpServers": {
"hwtl": {
"url": "https://human-wants-to-learn.dev/mcp"
}
}
} Check that it is connected
Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
Remove only HWTL
Remove only the hwtl server in Cursor’s MCP settings or configuration. A separate HWTL native plugin is not installed by this route.
Something did not work
- Make sure the HWTL server is enabled in this app and that you are using the chat mode that can call tools.
- If HWTL is listed but no lesson appears, ask for hwtl_learn by name. A remote tool does not automatically add icons beside every term.
- A managed account may restrict custom servers. Use the app’s normal access process; do not bypass its policy.
VS Code + Copilot ChatRemote MCPPublic preview · host test pending
Use HWTL as an MCP tool in Copilot Agent mode. This is not a claim that an HWTL Marketplace extension has been published.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in VS Code + Copilot Chat; use the check below.
- Step 1
Open VS Code’s MCP installer
Use the install button and review the HTTP server. Or use the terminal command in the alternative steps.
Add HWTL to VS Code - Step 2
Choose Agent mode in Copilot Chat
Enable HWTL in the tools picker, complete the normal trust review and ask for a lesson.
Other setup options
Choose the option and scope you want. Configuration blocks must be merged with existing entries.
code --add-mcp '{"name":"hwtl","type":"http","url":"https://human-wants-to-learn.dev/mcp"}' {
"servers": {
"hwtl": {
"type": "http",
"url": "https://human-wants-to-learn.dev/mcp"
}
}
} Check that it is connected
Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
Remove only HWTL
Remove only hwtl from VS Code’s MCP server configuration. If you used a workspace file, keep its other server entries.
Something did not work
- Make sure the HWTL server is enabled in this app and that you are using the chat mode that can call tools.
- If HWTL is listed but no lesson appears, ask for hwtl_learn by name. A remote tool does not automatically add icons beside every term.
- A managed account may restrict custom servers. Use the app’s normal access process; do not bypass its policy.
- If your terminal does not recognize code, use the install button or VS Code’s MCP configuration interface.
Grok BuildRemote MCPPublic preview · host test pending
Use HWTL from xAI’s Grok Build coding CLI. Grok Build and the Grok website have different setup flows.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in Grok Build; use the check below.
- Step 1
Add the HTTP server from your terminal
Paste this at a shell prompt, outside the Grok Build conversation.
Enter this at a shell prompt, outside an active coding-assistant conversation.grok mcp add --transport http hwtl https://human-wants-to-learn.dev/mcp - Step 2
Use the HWTL tool in a new chat
Complete any normal host review and test the lesson request. A connected tool is different from passive inline annotations.
Check that it is connected
Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
Remove only HWTL
Remove the hwtl MCP server using Grok Build’s server settings. Keep unrelated plugins, servers and trust settings.
Something did not work
- Make sure the HWTL server is enabled in this app and that you are using the chat mode that can call tools.
- If HWTL is listed but no lesson appears, ask for hwtl_learn by name. A remote tool does not automatically add icons beside every term.
- A managed account may restrict custom servers. Use the app’s normal access process; do not bypass its policy.
Grok on the webCustom connectorPublic preview · host test pending
Use a custom MCP connector from grok.com. Pasting a shell command into a web chat does not install a coding plugin.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in Grok on the web; use the check below.
- Step 1
Open Grok’s connector settings
Visit grok.com/connectors. Choose New Connector, then Custom.
Open Grok connectors - Step 2
Add the HWTL server URL
Name it HWTL, paste this URL into the server URL field, and follow Grok’s connector review. Enable it in your chat before testing.
Paste this URL into the MCP server URL field in the app named in this step.https://human-wants-to-learn.dev/mcp
Check that it is connected
Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
Remove only HWTL
Disconnect HWTL in Grok’s connector settings. This does not uninstall anything from your computer.
Something did not work
- Make sure the HWTL server is enabled in this app and that you are using the chat mode that can call tools.
- If HWTL is listed but no lesson appears, ask for hwtl_learn by name. A remote tool does not automatically add icons beside every term.
- A managed account may restrict custom servers. Use the app’s normal access process; do not bypass its policy.
- Make sure you are using Grok’s Custom connector flow, not the Grok Build CLI or a different product named Groq.
Windsurf / CascadeGuided remote MCPPublic preview · host test pending
This guide is for legacy Cascade in Windsurf. Devin Local, the default agent for new tabs, uses a different configuration. Follow its own setup instead of copying this block.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in Windsurf / Cascade; use the check below.
- Step 1
Open this app’s MCP setup
Use Cascade’s Add Server or Open MCP config file action. Ask your setup agent to preserve existing entries.
- Step 2
Add an HTTP server named hwtl
Merge the block below into the configuration opened by this app, then refresh its tools. Keep the other server entries.
Merge this block into the settings file named in this step. Keep the existing server entries.{ "mcpServers": { "hwtl": { "serverUrl": "https://human-wants-to-learn.dev/mcp" } } }
Check that it is connected
Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
Remove only HWTL
Remove only the hwtl server from the configuration opened by this app, then refresh the tools.
Something did not work
- Make sure the HWTL server is enabled in this app and that you are using the chat mode that can call tools.
- If HWTL is listed but no lesson appears, ask for hwtl_learn by name. A remote tool does not automatically add icons beside every term.
- A managed account may restrict custom servers. Use the app’s normal access process; do not bypass its policy.
- Use this block only with legacy Cascade. Devin Local uses a different configuration. Open the actual app’s setup instead of overwriting a remembered file path.
Gemini CLIProject-scoped remote MCPPublic preview · host test pending
Use HWTL through Gemini CLI’s documented HTTP MCP connection. This route does not require an HWTL native extension and does not add passive inline annotations.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in Gemini CLI; use the check below.
- Step 1
Open a shell in your project
Paste the command below in your computer terminal, outside the Gemini conversation.
Enter this at a shell prompt, outside an active coding-assistant conversation.gemini mcp add --scope project --transport http hwtl https://human-wants-to-learn.dev/mcp - Step 2
Start a fresh Gemini CLI session
Review the normal tool prompts, then ask HWTL for a lesson. Make sure your account still uses Gemini CLI; Antigravity has a separate guide below.
Check that it is connected
gemini mcp list Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
Remove only HWTL
Remove the hwtl entry from the same project scope. This does not remove other servers or an unrelated native extension.
gemini mcp remove --scope project hwtl Something did not work
- Make sure the HWTL server is enabled in this app and that you are using the chat mode that can call tools.
- If HWTL is listed but no lesson appears, ask for hwtl_learn by name. A remote tool does not automatically add icons beside every term.
- A managed account may restrict custom servers. Use the app’s normal access process; do not bypass its policy.
- Google has changed Gemini CLI access for some account plans. Use its current account guidance; do not relabel this command as an Antigravity command.
Antigravity CLISetup route being checkedHWTL setup guide pending
Antigravity is a separate Google coding host. A working Gemini CLI MCP command does not establish its configuration format or HWTL compatibility.
- Step 1
Confirm the actual Google host
If you use Antigravity CLI, follow that product’s guidance rather than the Gemini command above.
- Step 2
Use public lessons while this setup is checked
The HWTL guide will add this route after its exact configuration and normal user flow are verified.
Check that it is connected
This route is pending. The public lesson library works without installing this adapter.
Updates: what happens automatically?
HWTL’s Antigravity install and update flow has not been verified.
Remove only HWTL
If you configured an experimental HWTL connection, remove only that entry through the actual host’s settings.
Something did not work
- Gemini CLI and Antigravity are distinct products with their own account and configuration rules.
GitHub Copilot CLIHost adapter pendingHWTL setup guide pending
Copilot CLI has its own plugin system. The VS Code MCP route above does not install a Copilot CLI plugin.
- Step 1
Use the correct Copilot product
Choose VS Code + Copilot Chat above if you want the documented remote MCP setup there.
- Step 2
Wait for the HWTL CLI adapter or use web lessons
No public HWTL Copilot CLI package or marketplace is claimed here.
Check that it is connected
This route is pending. The public lesson library works without installing this adapter.
Updates: what happens automatically?
Copilot CLI’s third-party marketplace auto-update needs explicit user-level configuration. A direct repository install is not proof that updates are enabled.
Remove only HWTL
Use the Copilot CLI plugin manager to remove an experimental HWTL entry only if you installed one.
Something did not work
- VS Code extensions, Copilot CLI plugins and its SDK/server sessions have different install and update behavior.
OpenClawGateway remote MCPPublic preview · host test pending
Use OpenClaw’s native HTTP MCP manager for HWTL lesson tools. No downloaded HWTL bundle is needed for this route. It does not make Claude’s passive hooks run in OpenClaw.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in OpenClaw; use the check below.
- Step 1
Add HWTL to the intended OpenClaw Gateway
Paste the command into a shell for that OpenClaw environment. This is a Gateway-wide server definition, so review that scope before running it.
Enter this at a shell prompt, outside an active coding-assistant conversation.openclaw mcp add hwtl --url https://human-wants-to-learn.dev/mcp --transport streamable-http - Step 2
Enable the server and test its lesson tool
In Settings → MCP → Configured servers, check hwtl and its normal access controls. You can also use Add server there instead of the CLI.
Check that it is connected
Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
Remove only HWTL
Remove hwtl from the Gateway’s configured MCP servers. Disabling it for one session is different from removing the saved global definition. Preserve other servers, plugins and skills.
Something did not work
- Make sure the HWTL server is enabled in this app and that you are using the chat mode that can call tools.
- If HWTL is listed but no lesson appears, ask for hwtl_learn by name. A remote tool does not automatically add icons beside every term.
- A managed account may restrict custom servers. Use the app’s normal access process; do not bypass its policy.
- Keep the explicit streamable-http transport. HWTL does not provide a legacy SSE endpoint.
- A compatible plugin bundle does not establish that OpenClaw executes Claude JSON hooks or adds passive annotations.
Muse Code (Meta)Guided project MCPPublic preview · host test pending
Muse Code is Meta’s coding tool. Muse Wonder and Muse Wonder Full are models you can use through it. This documented remote MCP route returns HWTL lesson tools; a native HWTL hook is not required or claimed.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in Muse Code (Meta); use the check below.
- Step 1
Add HWTL to the project’s .mcp.json
Merge the block below into that file. It uses Muse Code’s documented streamable-http spelling, not another app’s configuration aliases.
Merge this block into the settings file named in this step. Keep the existing server entries.{ "mcpServers": { "hwtl": { "type": "streamable-http", "url": "https://human-wants-to-learn.dev/mcp" } } } - Step 2
Start a new Muse Code process
Review its normal workspace trust prompt and test the HWTL tool. Starting a new chat inside an already running process does not reload the MCP configuration.
Check that it is connected
Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
After editing the MCP configuration, start a new Muse Code process. Its versioned guide says running sessions keep their startup configuration.
Remove only HWTL
Remove only hwtl from the project’s .mcp.json, preserving other servers. Start a new Muse Code process to apply the change.
Something did not work
- Make sure the HWTL server is enabled in this app and that you are using the chat mode that can call tools.
- If HWTL is listed but no lesson appears, ask for hwtl_learn by name. A remote tool does not automatically add icons beside every term.
- A managed account may restrict custom servers. Use the app’s normal access process; do not bypass its policy.
- A model name is not an installation target. Use Muse Code’s actual installed-version guide.
- The versioned guide warns that some tool filters were recorded but ignored in the documented version. Do not assume another client’s tool allowlist rules apply here.
Another MCP appGuided remote MCPPublic preview · host test pending
A client that supports remote HTTP MCP may be able to request HWTL lessons. Compatibility and tool approval are still app-specific.
The read-only connection passes protocol and real MCP client checks. Individual app installation and chat rendering checks are shown separately.
The HWTL service is available as a public preview. This page does not claim a completed install test in Another MCP app; use the check below.
- Step 1
Find the app’s custom MCP server setting
Use its official documentation. If it has no such setting, use the HWTL website instead.
- Step 2
Add HWTL and verify a real lesson
Use this URL only in a supported remote HTTP MCP field. Review permissions, enable the tool and use the test request.
Paste this URL into the MCP server URL field in the app named in this step.https://human-wants-to-learn.dev/mcp
Check that it is connected
Enable HWTL in the app’s tools or connector list. Then use the lesson-link check below. A server listing alone does not prove the full flow.
Updates: what happens automatically?
HWTL maintains the remote lesson service. There is no local HWTL package to update in this route.
Your app may need a reconnect or a new chat to discover changed tools. Its own software and any other plugins keep their own update rules.
Remove only HWTL
Remove only the HWTL custom server or connector in the same app.
Something did not work
- Plain web chats cannot install local plugins from a prompt. Perplexity, Groq and browser annotations are not claimed as tested integrations by this page.
Check the signal
A real link.
A real lesson.
Use this after connecting. Seeing a server name is only the first check.
Claude Code native plugin
Ask for a short explanation. In a supported response, look for a robot learning link beside a concept.
Explain what a terminal does and what a shell command is. Keep it to two short sentences. Remote MCP or web connector
Ask for HWTL’s tool by name. This route returns a lesson link when the tool is called.
Use hwtl_learn to find the reviewed Terminal lesson. Show me its robot learning link. HWTL is enabled.
Check the intended project, account or connector.
The robot link is real.
It points to a reviewed HWTL lesson, not an invented address.
The lesson opens.
Read the notes, try the quick quiz and load any reviewed videos you choose.
Not sure where to paste?
Where does this instruction go?
A Terminal window can show a shell or run Claude Code. Check which program is ready for your input; the window’s name or a single prompt symbol is not enough.
- Ask your coding assistant
- A plain-language request goes in the assistant’s conversation. It can run a command only if that tool and your permission are available.
- Claude Code command
- A Claude Code slash command, such as
/plugin, belongs at the Claude Code prompt. It is not a shell command or a command for every chat website. - Computer terminal · shell prompt
- A shell command belongs in a shell, such as zsh or Bash. On a Mac, use Terminal or an editor’s integrated terminal with a shell ready for input.
Copying does not run anything. Read the instruction’s purpose and destination before entering it. Example output is a result to read, not another command.
A connector URL belongs in that app’s server URL field. A configuration block belongs in its named settings file. Neither is a command to send to every AI chat.
Brief your supervisor
Choose a robot.
Set your pace.
Start with the public lessons. Choose your website companion and learning preferences when you are ready.
Building an app with the xAI API?
The API has a remote MCP tool route using server_url and server_label. That belongs in your application’s API request; it is different from a Grok Build plugin or a grok.com connector. Follow the current API’s tool policy instead of copying another provider’s approval fields.
xAI remote MCP documentation