---
name: setup-queuey
description: "Set up Queuey, reliable webhook and event delivery, in a repository. Works out whether the code sends or receives events, chooses the path, writes the configuration and stops for the API key. Use when the user wants events or webhooks delivered reliably, or asks to connect a codebase to Queuey."
---

# Set up Queuey in a repository

Queuey: Operational webhook delivery engine — reliable event delivery with retries, DLQ, idempotency, HMAC & OAuth2 signing, and per-key ordering.

The steps below are the prompt people paste from the setup page. Follow them in order. "Me" in them is the user you are working for.

```text
Set up Queuey (https://queuey.ai) in this repository.

1. Install the CLI if it is not already there. With .NET 8 or later:
     dotnet tool install -g Queuey.Cli --prerelease
   No .NET? Every release ships the CLI as one self-contained file, with
   no runtime needed, for osx-arm64, osx-x64, linux-x64, linux-arm64 and
   win-x64 (.zip). On macOS or Linux, with this machine's platform in place
   of osx-arm64:
     curl -fsSL https://github.com/Queuey-AI/queuey-client/releases/latest/download/queuey-osx-arm64.tar.gz | tar -xz
   Then move ./queuey onto PATH, or call it as ./queuey. A 404 means there is
   no build for this machine: install .NET 8 and use the command above.
   Check that it runs:  queuey --help

2. Run:  queuey advise --json
   It reads this repository and returns: whether we send events, receive them or
   both; which path to publish by; the evidence behind each conclusion; the next
   steps; and any question it could not answer from the code.

3. Follow what it returned.
   - Tell me its reasoning in your own words, and name the files it read.
   - If it asks a question (usually: can the network here be trusted?), ask me
     before you decide. A factory, kiosk, vehicle or on-prem box usually cannot.
   - Do NOT write your own retry loop, local queue, backoff or offline buffer.
     That is Queuey.Edge, already built and maintained. If the advice points to
     Edge, use Edge.

4. Set it up:
   queuey advise --write-files     # queuey.deploy.json + a .gitignore line
   Then do what it recommended, where it told you to:
   - In a .NET project, add the package it named (dotnet add package
     Queuey.Client, or Queuey.Edge) and wire up the publish call.
   - Anywhere else it says plain HTTP, and there is no package to add: POST to
     the ingress with fetch or the HTTP client the repository already uses,
     as in https://queuey.ai/docs/md/quickstart. Only from server-side code — the API
     key must never end up in a browser bundle.

5. Stop and ask me for an API key when you need one. Minting it is something I
   do in the console at https://app.queuey.ai (Manage license → API keys) — never you.
   Once I have given you one, you can run:  queuey advise --apply
   to create the queue.

Reference, as plain text rather than HTML: https://queuey.ai/llms-full.txt
It holds every docs page at once; if your fetch cuts it short, read single
pages instead: https://queuey.ai/docs/md/{slug}, for example /docs/md/quickstart.
Read it when you need exact syntax; do not guess at it.
```

## If the user only wants an analysis

Change nothing: no files, no workspace, no credentials.

```text
Analyse this repository for Queuey (https://queuey.ai) but change nothing.

Install the CLI if needed. With .NET 8 or later:
     dotnet tool install -g Queuey.Cli --prerelease
   No .NET? Every release ships the CLI as one self-contained file, with
   no runtime needed, for osx-arm64, osx-x64, linux-x64, linux-arm64 and
   win-x64 (.zip). On macOS or Linux, with this machine's platform in place
   of osx-arm64:
     curl -fsSL https://github.com/Queuey-AI/queuey-client/releases/latest/download/queuey-osx-arm64.tar.gz | tar -xz
   Then move ./queuey onto PATH, or call it as ./queuey. A 404 means there is
   no build for this machine: install .NET 8 and use the command above.
Then run:  queuey advise

Summarise what it says: do we send, receive or both; which path it recommends;
and the evidence it read that from. List the files it would create, but do not
create them. If it asks a question it could not answer from the code, put that
question to me.
```

## When the flow needs design decisions

Ingress authentication, idempotency, ordering, retries, payloads and delivery authentication are covered by the design-event-delivery skill: https://queuey.ai/.well-known/agent-skills/design-event-delivery/SKILL.md

Source: https://queuey.ai/docs/agent-setup