The inbox for AI engineers
Your AI engineers are working.Shipyard tells you when they need you.
Claude finished the build. Grok needs a decision. Cursor opened a pull request. Shipyard captures every meaningful update, organizes it by project, and drafts the response that keeps the work moving.
Stop checking every terminal, browser tab, and coding agent.
Works with Claude Code, Grok, Cursor, GitHub, and custom agents.
Needs Reply
Claude
SignalTrue is ready for production.
Rollout approval required.
Grok
Authentication changes are complete.
One migration decision remains.
Waiting on AI
Devin
Implementing the reporting update.
Completed
Cursor
Pull request #284 passed review.
Claude
SignalTrue is ready for production.
Everything passed staging.
- ✓214 tests passed
- ✓End-to-end suite passed
- ✓Production build succeeded
- ✓Migration verified
Recommendation
Run the backfill first, deploy behind a feature flag, and begin at 10%.
Decision needed
Should I start the rollout?
Suggested reply
Run the backfill, deploy behind the feature flag, and begin at 10%. Monitor errors for 30 minutes before increasing exposure.
Claude needs your decision
SignalTrue has reached a stopping point.
Open ShipyardConnect the tools you already use
Any agent can connect through the Shipyard capture protocol.
AI can do the work
The work stops when the AI needs you.
AI coding agents can plan, build, test, and debug for hours. Then they reach a decision. They finish a task. They encounter a failure. They need another prompt. And they sit there.
Unless you continuously check every terminal, browser tab, repository, and agent, valuable work remains idle.
- Claude CodeWaiting for rollout approval.
- GrokTask complete. Waiting for instructions.
- CursorPull request ready for review.
- GitHubDeployment failed.
- DeepSeekBlocked on access.
The coding is increasingly autonomous.Managing the handoffs is not.
One inbox for every AI engineer
Shipyard keeps the conversation moving.
Shipyard runs quietly alongside the tools your team already uses. It captures meaningful updates automatically, groups related work into threads, and brings forward only what deserves your attention.
When an AI engineer stops, Shipyard tells you why and prepares the next response.
- AI engineer works
- Shipyard captures the update
- The conversation is triaged
- You receive an alert
- Your response is already drafted
- The AI continues
No copying markdown. No forwarding messages. No remembering which agent has the ball.
Automatic capture
Keep working exactly as you do today.
Continue using Claude Code, Grok, Cursor, GitHub, DeepSeek, and the terminal. Shipyard Local runs quietly in the background and captures meaningful project activity as it happens.
It understands
- which project the work belongs to
- which AI session produced it
- whether it is progress, completion, failure, or a question
- which updates belong in the same conversation
- whether you need to respond
Shipyard observes the workflow. It does not interrupt it.
brew install tryshipyard/tap/shipyard shipyard login shipyard connect .
SignalTrue connected
- ✓Claude Code detected
- ✓Grok detected
- ✓Git repository detected
- ✓Capture active
- ✓Notifications active
Intelligent triage
See what needs you. Ignore what does not.
Not every AI event deserves an interruption. Shipyard separates conversations into familiar inbox states.
Threads requiring a human decision rise to the top. Routine activity stays quiet. Completed work remains searchable without cluttering the day.
Shipyard is organized around one question: what needs my attention right now?
Attention layer
Know the moment an AI engineer stops.
Shipyard alerts you when your input can move the project forward. Receive a notification when an AI engineer:
- needs a decision
- requests approval
- becomes blocked
- encounters a failure
- completes important work
Use browser push, native desktop notifications, the Shipyard web app, or an installed mobile web app.
Walk away from the terminal. Shipyard will bring you back when it matters.
Shipyard
Grok needs your approval
The notification system passed all tests. Approve the production rollout to continue.
Open ThreadSuggested replies
The next prompt is already written.
Every important update arrives with a response drafted from the full project conversation. Shipyard does not merely summarize what happened. It recommends what should happen next.
Review the suggestion. Edit it when needed. Press Send.
Spend less time reconstructing context and more time making decisions.
Claude recommends
Run the migration before deployment and begin the rollout behind a feature flag at 10%.
Suggested reply
Run the migration first. Deploy behind the feature flag and begin at 10%. Monitor errors for 30 minutes before increasing exposure.
Two-way communication
Reply from Shipyard. Let the AI continue.
Shipyard is not a read-only notification feed. When you approve or edit a response, Shipyard returns it to the originating AI workflow and updates the thread as the work continues.
- Claude needs approval
- Shipyard drafts the response
- You press Send
- Claude receives the instruction
- Work resumes
- The next update returns to the same thread
One project. One conversation. No prompt shuttling.
Immediately familiar
Projects are mailboxes.Tasks are threads.AI engineers are senders.
Shipyard uses a workflow people already understand. Each project has an inbox. Each task becomes a conversation. Every AI update stays attached to the work that produced it.
Search, reply, snooze, archive, and move on.
No new project-management methodology to learn. Just a better way to communicate with AI engineers.
- All Projects
- Inbox
- Needs Reply
- Waiting on AI
- Completed
- Snoozed
Stop becoming the message router.
Before Shipyard
- Open Claude
- Read the response
- Remember the project
- Open GitHub
- Review the pull request
- Open Grok
- Check whether it finished
- Rewrite the next prompt
- Return to Claude
- Repeat
With Shipyard
- Open the inbox
- Review what needs you
- Approve the drafted replies
- Let the work continue
You should not manage tools.You should manage conversations.
More agents. Less coordination.
Run several AI engineers without losing track of the work.
Shipyard gives every project one consistent place for updates, questions, approvals, and completed work. Whether two agents are working or twenty, you always know what is active, what is finished, what failed, what needs a decision, and who has the next move.
SignalTrue
Claude
Waiting for rollout approval.
DeepSeek
Grok
Working on local memory sync.
DataBridge
Cursor
Provider migration complete.
Shipyard
Claude
Browser notifications need production approval.
How it works
Connect once. Work normally.
01
Connect a project
Run Shipyard Local inside an existing repository. Shipyard detects the repository and supported AI tools.
shipyard connect .
02
Start work in your existing tools
Use Claude Code, Grok, Cursor, GitHub, or custom agents as usual. No special prompt syntax is required.
03
Shipyard captures meaningful updates
Relevant work becomes a normalized project conversation. Routine telemetry stays in the background.
04
Respond from the inbox
Receive an alert, review the suggested reply, and send the next instruction. The AI continues.
Works with your existing stack
Every AI engineer reports to the same inbox.
Claude Code
Capture sessions, meaningful updates, decisions, failures, and completions.
Grok
Organize tasks, results, and requests for the next instruction.
Cursor
Bring agent activity and project artifacts into the appropriate thread.
GitHub
Attach pull requests, checks, reviews, merges, and deployments to the work that created them.
DeepSeek
Connect local autonomous workflows through the Shipyard protocol.
Custom Agents
Send structured events through the Shipyard API, CLI, SDK, or MCP adapter.
Built for development work
Your projects remain yours.
Shipyard is designed for sensitive engineering workflows.
Read About Security- Credentials stored securely in macOS Keychain
- Encrypted data in transit and at rest
- User-scoped projects and conversations
- Row-level security
- Revocable machine credentials
- Private notification previews by default
- No source code in lock-screen alerts
- No secrets written to repository configuration
- Raw capture events preserved for debugging and auditability
“AI agents can work independently for hours, but they still stop when they need context, approval, or another decision. Shipyard makes sure that moment never gets lost.”
Spend less time checking.Keep more work moving.
Fewer idle agents
Respond when an AI reaches a stopping point instead of discovering it hours later.
Less context switching
Manage Claude, Grok, Cursor, GitHub, and custom agents through one consistent inbox.
Faster decisions
Review evidence, accept the recommendation, and send a grounded response without rebuilding the context.
Simple pricing
Start with one inbox.
Individual
For developers and founders managing their own AI engineers.
- Multiple projects
- Claude Code and Grok capture
- Browser and desktop notifications
- Suggested replies
- Cross-device sync
Team
For engineering teams coordinating multiple agents and repositories.
- Shared projects
- Role-based access
- Team inboxes
- Centralized security controls
- Custom integrations
FAQ
Does Shipyard replace Claude Code, Grok, or Cursor?
No. Continue using the AI tools you already rely on. Shipyard captures their meaningful updates and gives you one place to manage the conversation.
Do I need to copy prompts or markdown into Shipyard?
No. Shipyard Local captures supported AI activity automatically and associates it with the correct project and thread.
Does Shipyard record every internal AI action?
No. Shipyard preserves the events required for reliability, but the inbox surfaces only meaningful updates, decisions, failures, and completions.
Can I reply to an AI engineer from Shipyard?
Yes. Shipyard drafts the response and returns your approved instruction through the connected local adapter whenever the originating tool supports continuation.
Will I be notified when an agent finishes?
Yes. Shipyard can send browser, desktop, in-app, and mobile-web notifications when work completes or requires your attention.
Is Shipyard another project-management tool?
No. Shipyard is an inbox. Projects are mailboxes, tasks are threads, and AI engineers report their work as messages.
Does Shipyard work when the browser is closed?
Yes. Shipyard Local captures work independently of the browser, and supported notifications can reach you when the web app is closed.
Can custom AI agents connect?
Yes. Custom agents can communicate through the Shipyard capture protocol and normalize their work into the same inbox experience.
Your AI engineers should never sit waiting for you.
Connect your projects. Keep working in the tools you already use. Shipyard will tell you when something needs your attention—and have the next response ready.
Be among the first developers to manage Claude, Grok, Cursor, and custom agents from one inbox.