# Quickstart

Connect a project, install one runtime, and verify your first real event.


[Illustration: setup]

## Create your project

Create a project in the dashboard and give it a name. An empty project is ready for installation; it does not have production measurements yet. Use **Onboard your agent** for the setup prompt, or follow the framework guides below.

## Connect your agent (optional)

Authenticate the local CLI using the API URL for your deployment. In a source checkout, the executable is available through the workspace:

```bash title="Terminal"
pnpm --filter @everock/cli start login --api-url http://localhost:4001
```

Approve the device login in your browser. Your agent can reuse that session through the local MCP server. See [CLI](/docs/agents/cli) and [MCP](/docs/agents/mcp) for the complete setup.

## Install your runtime

Install the public JavaScript beta in your application. Browser, Node.js and edge runtimes use the same package. Set the collector URL to a running Everock API that your application can reach. The Next.js, Vite and NestJS tabs use locally built adapters. Follow the linked framework guide to build the archive and substitute its actual path.

- [Next.js setup](/docs/sdks/nextjs): `npm install @everock/next`
- [Vite setup](/docs/sdks/vite): `npm install @everock/vite`
- [Node setup](/docs/sdks/node): `npm install @everock/sdk`
- [NestJS setup](/docs/sdks/nestjs): `npm install @everock/nest`

Follow the complete framework guide to configure your project and collector.

The browser SDK observes the browser. Install the Node or edge entry in your backend too when your application includes server routes, workers, or separate APIs. A GitHub connection adds repository access; it does not install telemetry.

JavaScript frameworks and runtimes: Next.js, React, Vue, Svelte, Node.js, NestJS, Cloudflare; repository integration through GitHub.

## Verify an event

Use the actual public key and collector URL from your project. Generate one intentional handled error in a development environment and confirm it arrives under the correct project, component, environment, and release.

```ts title="Temporary browser check"
import { captureError, flush } from '@everock/sdk';
captureError(new Error('Everock setup verification'), { handled: true });
await flush();
```

Remove this test after verification. A received event confirms that runtime's delivery path; it does not prove that every service has been instrumented.

The CLI and MCP packages in this checkout are private workspace packages. Use workspace executables until a distributable package is published; do not assume a public npx command already exists.