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

# Other ways to start

> Choose an application integration or customer-controlled execution path, with its access requirements made explicit.

Start with the [quickstart](/getting-started/quickstart) to learn the Agent,
Environment, and Session requests. Its Session steps require a supported Harness
and execution path in your Workspace; the hosted API has no simulator fallback.
Choose another path when your goal is different.

<CardGroup cols={2}>
  <Card title="Add Checkfu to an app" icon="code" href="/guides/add-an-agent-to-your-app">
    Create Sessions from your backend. Plain HTTP needs no private package; SDK examples need an invited alpha artifact.
  </Card>

  <Card title="Connect a local agent" icon="server" href="/guides/connect-a-local-agent">
    Attach a supported operator-owned ACP process on a laptop, workstation, or VM while Checkfu keeps the Session history.
  </Card>
</CardGroup>

For deployment, choose Checkfu-managed or customer-operated Cloudflare. See
[Deployment](/concepts/deployment) for who operates the installation.
ConnectedRuntime attachment is a separate execution choice.

## Authoring and custom harnesses

The [Agent project guide](/guides/author-an-agent-project) currently describes
a source-checkout workflow for contributors or explicitly authorized
evaluators. It is not a public installation path or a prerequisite for the
HTTP quickstart.

The [custom-harness guide](/guides/bring-a-custom-harness) explains how to bring
your own implementation. BYOH means bring your own harness; it does not choose
deployment ownership or compute. Its reference source and CLI prerequisites are
separate from access to the hosted API. Use only an artifact or source checkout
you have explicitly received access to; do not assume access to the platform
repository.

The CLI and TypeScript SDK have no self-service public package channel during
private alpha. See [CLI access](/getting-started/cli-access) and
[TypeScript SDK access](/reference/typescript-sdk) for the documented artifact
requirements.

[Capability status](/getting-started/status) explains how to check the exact
deployment and Workspace. Creating a resource or seeing an endpoint does not
establish that its execution path is available.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.