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

# Quickstart

> Install OneShot GTM and review your first candidates.

## Open the dashboard

Bun 1.3 or later is required. With Bun installed:

```bash theme={null}
bunx oneshot-gtm-server
```

This downloads the published dashboard server. The terminal CLI requires a source checkout; it is not published to npm.

## Install from source

```bash theme={null}
git clone https://github.com/oneshot-agent/oneshot-gtm
cd oneshot-gtm
bun install
bun run cli -- init
bun run cli -- doctor
bun run --cwd apps/web build
bun run cli -- ui
```

The dashboard opens on the workspace's port, normally [http://127.0.0.1:3030](http://127.0.0.1:3030) for the default workspace.

## Configure your motion

In Setup, describe your product, who it is for, and the founder experience that makes your approach credible. Add factual product links: replies may use these links, but should not invent them. Optional founder fields can remain blank.

Configure your LLM provider and OneShot credentials. Add a sender identity before sending. Run `doctor` to see missing credentials or deliverability issues. Some finders need additional keys: for example, GitHub finders need `GITHUB_TOKEN` for practical rate limits.

In Queue, configure a finder, inspect its readiness message, and run it. Discovery and research can spend money. Review the queued person's evidence and draft before approving or sending.

## Preview a drain

```bash theme={null}
bun run cli -- find drain podcast-guest --dry-run
```

Choose a play matching approved rows in your own queue. A dry run is a preview, not a live send. See [finders](/oneshot-gtm/finders) for discovery and [sending](/oneshot-gtm/sending) for sender setup.

For a fictional dashboard, use `bun run cli -- demo seed`, then `bun run cli -- demo ui`. Demo state is isolated; action calls are not simulated.