Use Cases

Real problems SlopDrop solves.

1. AI Agent Output That Outlives the Chat

Your agent writes a brilliant architecture plan. A detailed code review. A migration strategy. Then the conversation ends and it's... gone. Buried in chat history, unfindable, unreferenceable.

With SlopDrop: The agent writes to a local file. The watcher syncs it. It has a permanent URL you can paste into a ticket, a PR, or a Slack thread. It's still there next week.

2. Multi-Checkout / Multi-Machine Development

You work across branches, worktrees, or multiple machines. That analysis doc Claude wrote? It's on your laptop at home. Your specs are on the work machine. Nothing is in sync.

With SlopDrop: The watcher runs in the background. Every .md file syncs as you save. Switch machines, open the URL. It's there. No git commits, no manual uploads, no "which folder was that in?"

3. Linking AI Docs in Tickets and PRs

Your AI agent generates a ticket analysis or a spec. You want to link it in Linear, GitHub, or Jira. But it's a local file. You can't link to your filesystem.

With SlopDrop: Every synced file gets a persistent URL. slop drop spec.md → paste the link in your ticket. Done. Anyone on the team with access can read it, rendered beautifully.

4. Team Knowledge Base (Without the Overhead)

You don't want to maintain a wiki. You don't want to set up Notion. You just want a place where the team's AI-generated docs live and are findable.

With SlopDrop: Point the watcher at your ai-docs/ folder. Every teammate's work syncs automatically. Browse at yourteam.slopdrop.dev. Private by default, full tenant isolation.

5. Code Review Artifacts

AI code reviews generate long, detailed output. Too long for a PR comment. Too valuable to lose.

With SlopDrop: Pipe the review to SlopDrop, link it in the PR. The reviewer sees the full analysis. It's versioned — re-run the review and the URL updates.

6. Research and Extraction Pipeline

You process articles, videos, podcasts through AI and extract insights. Those extractions pile up as local files.

With SlopDrop: Sync your research/extractions/ folder. Browse them rendered at your subdomain. Wiki-links connect related docs. Build a searchable knowledge base without building anything.

7. Client-Facing Documentation

You generate docs for clients — audit reports, analysis, recommendations. They need to read them somewhere professional, not a Google Doc you forgot to share.

With SlopDrop: Each client gets a tenant. Their docs render at clientname.slopdrop.dev. Protected by Cloudflare Access — only their email domain gets in. You control visibility.

8. Onboarding New Team Members

New dev joins. "Where's the architecture doc?" "Check the ai-docs folder." "Which machine?" "Uh..."

With SlopDrop: "It's at team.slopdrop.dev/project/architecture." Done. Every doc the team has ever generated, rendered and browsable. The onboarding doc is also a SlopDrop doc.