> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inklyai.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Why AI native

> Learn why Inkly is built for AI-native demo authoring, maintenance, customization, and discovery.

Inkly is AI native because demos are not locked inside a visual editor. They live as code in a hub, and the CLI gives agents a reliable way to capture and update them.

Your demo workflow can use the same agents you already use for product work. Claude Code, Codex, Cursor, and other agents can read the source, capture product flows, edit content, and keep demos current.

<CardGroup cols={2}>
  <Card title="Authoring" icon="terminal" href="#authoring">
    Agents can use the CLI as a browser harness to capture complete product stories.
  </Card>

  <Card title="Maintenance" icon="code" href="#maintenance">
    Demos can update alongside product changes, releases, and merged PRs.
  </Card>

  <Card title="Customization" icon="wand-sparkles" href="#customization">
    Agents can tailor demos for each customer, prospect, segment, or use case.
  </Card>

  <Card title="Discovery" icon="search" href="#discovery">
    Hosted demos are built to be readable by people and AI systems.
  </Card>
</CardGroup>

## Authoring

Inkly treats AI agents as first-class demo authors. The CLI lets an agent open Chrome, inspect the page, follow stable element references, record each step, and export a demo folder.

The agent owns the product story while Inkly handles the browser and capture mechanics. Use `inkly capture` for screenshot and video demos, or `inkly capture-html` when you want HTML-based demos.

## Maintenance

Demos go stale when they live outside the product workflow.

Inkly keeps demos in the same repository-backed model as the rest of your product work. When a release changes the UI, a merged PR updates a flow, or positioning changes, an agent can update the relevant steps, copy, annotations, and assets before you publish.

## Customization

Demo as Code also makes personalization practical.

Because demo config, copy, steps, annotations, and captured HTML are files, an agent can tailor a demo for a customer, segment, or deal without rebuilding it. It can rewrite intro screens, emphasize the right features, trim irrelevant steps, and add account-specific guidance.

HTML capture gives agents more room to customize captured content because the screen is stored as editable structure instead of only a flat image. Screenshot and video capture is still the best starting point for most demos.

## Discovery

Inkly demos are hosted for humans, but they are designed to be readable by AI systems too. A hosted demo hub gives people a public page to browse and gives agents a stable URL they can inspect, summarize, and reason about.

Inkly is designed to expose AI-readable context for hosted demos, including a `hostlm.txt` entry point for demo URLs. The goal is simple: the same hosted demo should be understandable to a person in the browser and to an AI assistant reading the page context.

## What this changes

AI native demos make the demo process part of your daily workflow.

You can bring your own agents, polish in the no-code editor, keep the source in a repository, publish as a hosted hub, and keep improving the demo as the product changes.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/get-a-quick-start">
    Create your first demo with an agent or the Chrome extension.
  </Card>

  <Card title="Agentic capture" icon="robot" href="/cli/capture">
    Capture a demo end to end with an AI agent.
  </Card>

  <Card title="Hubs and demos" icon="folder" href="/concepts/hubs-and-demos">
    Learn how demos live inside a repo-backed hub.
  </Card>

  <Card title="Install the CLI" icon="terminal" href="/cli/install">
    Install `inkly` so agents can capture, preview, and publish demos.
  </Card>
</CardGroup>