Getting Started
Cinder documentation
Start here for installation, quick start, semantic tags, architecture, and the real local-first SDK path.
Need the shortest path?
Use Quick Start when you want the smallest working route → scan → graph → run flow first.
Something feels off?
Inspect scan output, graph state, active route/context, and dispatch in a practical order.
Need the full surface?
Browse all runtime methods, hooks, extension points, and lifecycle APIs.
Cinder is a semantic runtime for websites you control. These docs are organized to get you from first install to first real command flow as quickly as possible.
Start with the shortest useful path
If you are evaluating the SDK, start here first.
Installation
Install the browser SDK, use a local-first configuration, and add the server package only if you want bounded fallback.
Quick Start
Tag one route, scan the page, inspect the graph, and run a first command through the full runtime path.
Semantic Tags
Learn the V1 tag system that gives the runtime stable application meaning instead of prompt glue.
Application Graph
See how semantic scan results become scoped graph nodes, indexes, and runtime state used by local reasoning.
API Overview
Browse the public SDK surface for scan, graph, run, speech, extension points, and lifecycle control.
Architecture
Understand the full flow from semantic tags to graph, planners, DOM execution, and optional fallback.
Beyond the core SDK
Relay Overview
A hosted, metered tier-3 proxy - tier 1 and tier 2 stay free, tier 3 AI fallback is usage-based.
CLI Overview
Crawl a real running app, audit every page for tagging gaps, and teach your coding agent to keep up.
Agent Onboarding
A single, agent-fetchable prompt that installs, tags, audits, and verifies Cinder end to end.
Recommended reading paths
Choose the path that matches your immediate goal.
I want a first working integration
Read Installation, Quick Start, and Tagging a Page.
I want to understand how it works
Read Semantic Tags, Application Graph, Local Resolution, and Architecture.
I need to debug or extend it
Read Debugging, API Overview, and Dispatch and Feedback.
What the docs assume
These docs assume the V1 promise is: install Cinder, tag a website you control, resolve common navigation/action/field/output flows locally, and use custom bindings or adapters only when the standard DOM path is not enough.
What is true about the current SDK
- the browser runtime is the product core
- semantic tags and graph structure are primary, not prompt tricks
- local-first resolution is the default path
- fallback is optional, bounded, and secondary
- ambiguity is handled more honestly than earlier MVP versions
- extension points now exist for routes, DOM adapters, custom intents, runtime context, and runtime events
Suggested next pages
Continue reading