If you already use Claude Code, Cursor, Codex or another coding agent, getting started with Queuey can be pretty straightforward.

Instead of starting by reading through all the documentation and working out where Queuey should fit, you can give your agent the Queuey setup prompt and let it take the first pass.

The full prompt is available in the Queuey agent setup guide.

The setup prompt tells your coding agent to install the Queuey CLI if needed, run queuey advise --json, and use the result to work out how Queuey fits into the repository.

queuey advise inspects the project and recommends how Queuey should be added based on what is already there. It checks whether the application sends events, receives them or both, and looks for things like existing queues, outboxes and jobs before suggesting a path forward.

At this point it is analysis only. You can review the recommendation before changing anything.

Let the agent make the first change

I would start with one existing webhook or event flow rather than trying to move everything at once.

The agent already has the codebase and the recommendation from queuey advise, so it can show you what needs to change without you first having to map the whole integration yourself.

If Queuey needs supporting files in the repository, the agent can generate them with:

queuey advise --write-files

From there, let the agent make the proposed changes and review the diff as you normally would.

You still review the implementation. You still test it. And if Queuey needs something the agent cannot know, it asks instead of guessing.

One of those things is the API key. That is created by you in the Queuey console, not by the agent.

When the setup is ready, the Queuey resources can be applied with:

queuey advise --apply

Then ask one more question

Once the first flow is running through Queuey, ask the agent:

What can I delete now?

In mature applications, delivery logic is rarely kept in one place. It tends to spread across workers, retries, jobs, delivery state, error handling, monitoring and recovery code.

Once Queuey takes over that responsibility, some of those pieces may no longer be needed.

In a small integration, that may be a few hundred lines. In a mature application where delivery logic has grown over time, it can be thousands.

The goal is simple: Queuey should remove responsibility from the application, not add another layer to maintain.

And because the agent has already worked through the implementation, it can also help identify what is now redundant.

Give the agent the setup prompt, review the recommendation, and see how much delivery code you can stop maintaining.