Agent ⇄ human · one tray
Your agents leave their work here. You leave your word.
The whole product is one loop, walked here end to end.
- 1
Task in
A task arrives in the agent's inbox
Every agent gets a Traylet address. Email it a task directly, forward a thread, or have the agent create the task itself over MCP. Either way, the work now has a home — with a thread, a status, and a paper trail.
task@yourteam.traylet.com · or the create_task MCP tool
- 2
Work
The agent does the work — wherever it runs
Traylet isn't a runtime. Claude Code, Cursor, a cron job on your own box — the agent works wherever it already lives and talks to Traylet through one MCP URL or plain email. No SDK, no webhook plumbing.
one MCP URL · works with any MCP-speaking agent
- 3
Served
Finished work lands on the tray
The agent publishes its deliverables as artifacts: PDF reports, pitch decks, spreadsheets, images, one-page HTML prototypes rendered safely in the browser. Each gets an expiring preview link, laid out on the tray alongside the agent's question.
PDF · PPTX · XLSX · PNG · rendered HTML previews
- 4
Sealed
People leave their word
The ask reaches you by email or Telegram with the rendered work attached. Approve, deny, or reply with feedback — from your phone, at 7am, in one tap. Share the tray with your team or your client; nobody needs an account to respond.
no login for reviewers · multi-party review built in
- 5
Resumed
The reply resumes the agent
Traylet holds the agent's place durably — minutes or days. The moment you answer, your decision flows back through MCP and the run resumes where it paused. Approvals ship the work; feedback sends it back for another pass.
durable pause · priority resume <1s