KNOWLEDGE.DEV TOOLCHAIN

Developer tools with a supercar stance.

A focused control surface for the tools around Knowledge.Dev: install the local stack, launch lessons fast, connect an MCP server, and keep workbench workflows visible while agents operate on real code.

6 tools and flows
Local runtime first
MCP guided context
DESIGNED FOR FLOW

Two bright guide lines cut through the page like track markers: setup on one side, orchestration on the other.

TOOLS

Everything referenced in the docs, staged as one system

These tools are described in `web/docs` and arranged here as a single fast lane instead of disconnected utilities.

01 Available

Launcher App

Install, update, and maintain Knowledge.Dev components, including the local MCP binary and related development tooling.

View setup
02 Available

Demo Prompt

Start a lightweight lesson path with almost no setup, as long as you already have an AI coding agent ready to work.

See flow
03 Available

MCP Server

The control channel for lesson state and guided context, keeping the playground session grounded while the agent leads the work.

Connect MCP
04 Workbench

Logs

A live feed for development output, so runtime information stays visible while systems boot, sync, and respond.

Open docs
05 Workbench

Procs

Process supervision for local development, giving you direct sight over what is running, what failed, and what needs intervention.

Open docs
06 Workbench

Agent

Orchestrate Claude Code and Codex through their SDKs and work with agents as cooperating operators, not just chat windows.

Read overview
FLOW

Built like a fast pit lane

A1

Prime the machine

Use the launcher to get the local stack into shape without manually assembling every component.

A2

Ignite the session

Use the demo prompt or quick start path to move from install into a real lesson with minimal drag.

A3

Lock context

Attach the MCP server so the agent uses the lesson runtime as the source of truth.

A4

Drive with telemetry

Bring logs, process control, and agent coordination into one visible loop instead of juggling hidden terminal state.

NEXT STEP

Open the docs and take the first lap.

Go to documentation