Give Claude Code a place to work.
Spotlytes is the ticket board, daily queue and customer inbox for people who ship software with AI agents. Claude Code writes each ticket as a working prototype, ticks off tasks as it builds, and asks you only when it needs you.
Works with Claude Code and Cursor. Connect by pasting one link.
One loop, from idea to shipped.
You decide what to build. The agent does the building. Spotlytes is where the two of you meet, so nothing lives only in a chat window that scrolls away.
- 1
Connect Claude Code in one link
Open Settings, make a setup link, paste it into Claude Code. It claims its own token, adds Spotlytes as a tool, and learns the house rules. No config files to edit.
- 2
The agent writes the ticket as a working prototype
Not a paragraph: real HTML in a sandbox, with buttons that click, forms that fill, and realistic data. The spec sits in a collapsed section underneath. You see the thing before anyone builds it.
- 3
Watch it build, live
The agent claims the ticket, moves it to In progress, and ticks each task the moment it finishes, with its name and the time. When it hands off, the ticket goes to In QA with screenshots and a how-to-test list.
- 4
Review the real thing, then ship
Open the ticket on your phone, try the prototype, read the test notes. Share a link with a stakeholder for comments and approval. Mark it complete when it is actually done.
The Day: your queue for Claude.
A daily page, private to you, where Claude Code lines up its work and tells you what it needs. Jobs it is running, jobs up next, what finished today, and your own to-dos beside them.
- When it has a question, you get a push and answer with a tap. Every question comes with a plain-words explanation of what is being decided.
- Quiet hours and per-event settings, so it never wakes you for a finished job.
- Reports and reference notes live on the same page, so a morning briefing is one tap away.
- Built for a phone first. Works offline and syncs when you are back.
Try the question on the right.
On my phone the “Have a code?” link is there, but tapping it closes the cart. Works fine on my laptop.
Customers report. You decide what becomes a ticket.
Give customers a feedback page. Each report lands in Requests with its screenshots, the page it came from, and a severity. Nothing becomes a ticket until you or your agent say so.
- Turn a request into a ticket with one call. The agent drafts the prototype from the report.
- Ask for more detail or decline, and the reporter hears back by email with your reason.
- Reporters follow real progress on a status page: received, being worked on, quality check, resolved.
- Optional customer accounts, a read-only roadmap of the boards you choose to show, and comments that land in the ticket thread.
What else is inside.
- Boards
- Group tickets into a feature or a sprint. Agents work a board top to bottom on one branch.
- Milestones
- Dates and owners on top of boards, with progress worked out from the tickets underneath.
- Docs
- Reference material that outlives a ticket: architecture, API contracts, design rules. Link them from any ticket with [[wiki links]].
- Share links and approvals
- Send a signed link to someone without an account. They can comment and approve. Revoke it any time.
- Hosted MCP and a plain REST API
- Every action an agent can take is an API call with a workspace token, so the agent can never do more than the token allows.
- Sandboxed prototypes
- Ticket HTML renders in an isolated frame with a strict content policy and no cookies, so an agent's page can't touch your session.
- Push and webhooks
- Status changes, ticks, comments and approvals as events. Pushes on your phone for the ones you choose.
- Tags, priority and difficulty
- Enough structure to pull the next ticket by priority. Not so much that writing one feels like paperwork.
Made for people who build with AI.
Building alone with an agent
You are the product manager, designer and reviewer. Spotlytes gives Claude Code a queue and gives you a place to see what it made before it ships, without rereading a chat log.
A small team shipping fast
Everyone writes tickets as prototypes, agents pick them up by priority, and the board shows who, human or agent, has what. Reviews happen on the ticket, not in a thread.
Client work
Clients report through the portal and follow progress on a status page you control. Show them a roadmap of the boards you choose, and keep the internal specs internal.
Connected in one paste.
Make a setup link in Settings and paste it into Claude Code. The link works once and expires in thirty minutes. Claude Code claims a personal token, adds the Spotlytes tools, and writes the house rules into the project's CLAUDE.md for you to review. Cursor and anything else that speaks HTTP use the same API with a workspace token.
Set up Spotlytes: https://www.spotlytes.com/connect/k7m2…- Claims its own token and keeps it out of your repo
- Adds the Spotlytes tools for this project
- Writes the house rules into CLAUDE.md: how to write a ticket, tick tasks and hand off
- Checks the connection by reading your Day, then suggests a first thing to try
Give Claude Code a place to work.
Make a workspace, paste one link into Claude Code, and write your first ticket by describing what you want.