Claude runs your day. You make the calls.
Spotlytes gives Claude Code a daily Queue. It reads your tickets and your repo, plus the Slack, email and Jira you have connected, lines up the work and does what it can on its own. You get a short list: the calls only you can make, the things you promised people, and what shipped.
Built for Claude Code. Set up by pasting one link. Try the question on the right.
How a day goes.
The Queue is one page, private to you. Claude works the list between routines and only interrupts when it needs a decision. You check in from your phone, not a chat window that scrolls away.
- 08:00
A morning briefing
One short report: what changed overnight, what needs you, and what to do first. “Today: 6 for you, redeploy stage first.”
- All day
Routines on your schedule
/triage turns new reports into tickets. /converse catches up on your threads and turns what you promised people into to-dos. You pick the commands and the times. A run that an earlier one already covered skips itself.
- When it's stuck
A push, then a tap
Each question comes with Claude's pick, a few short options and a plain-words “What does this mean?”. Answer from your phone and the job moves to the top of Up next.
- Your list
To-dos that come with the why
Who asked, where you said yes, and a drafted reply when one helps. Queue one back to Claude if it can do it for you.
- Evening
A wrap-up
What got done, what moved, and the calls still waiting on you. Every report stays on the page, so last Tuesday is one tap away.
An agent you can leave alone.
- It says why
- Every line has a “?” behind it: what is going on, why it matters, what happens if it waits, and what Claude recommends.
- It knows its limits
- When a job needs something Claude shouldn't touch, like your production database, it goes on your list with the exact steps instead.
- Your words stay yours
- Claude can tick your to-dos and add notes. It never rewrites what you wrote.
- Proof before review
- Built work comes back with before and after screenshots and how-to-test steps, not just a diff.
- Quiet when you are
- Quiet hours and per-event pushes, so a finished job never wakes you.
- Built for a phone
- Works offline and syncs when you are back. Most answers take one tap.
When the work is code, the ticket is a prototype.
Claude writes each ticket as real HTML in a sandbox, with buttons that click and realistic data. The spec sits underneath. You see the thing before anyone builds it.
- The agent claims the ticket and ticks each task the moment it finishes, with its name and the time.
- It hands off to In QA with screenshots and a how-to-test list, and the review lands on your Queue.
- Send a signed link to a stakeholder. They can try the prototype, comment and approve without an account.
- Boards, milestones and docs when you need them. Agents work a board top to bottom on one branch.
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.
- Routines
- Commands Claude runs at the times and days you pick. Each one waits on the Queue until its time, and a missed run skips itself.
- Reports and notes
- Briefings, wrap-ups, QA runs and reference notes, kept by day and searchable. Deep links go straight to one.
- 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.
- Boards and milestones
- Group tickets into a feature or a sprint, with dates and progress worked out from the tickets underneath.
Made for people who build with AI.
Leads who build with agents
You own a product, a team and a pile of promises in Slack and email. The Queue keeps track of all three and hands you only the decisions.
Building alone
You are the product manager, designer and reviewer. Claude does the building between routines, and you check in from your phone instead of rereading a chat log.
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, installs the Queue commands, 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
- Installs the Queue commands: /day, /triage and /converse
- Writes the house rules into CLAUDE.md: how to run the Queue, write a ticket and hand off
- Checks the connection by reading your Queue, then suggests a first thing to try
Let Claude run your day.
Make a workspace, paste one link into Claude Code, and pick when your routines run. Tomorrow starts with a briefing.