Loop App Origin
Loop exists because agent skills rot the same way docs do, and Kevin refused to refresh them by hand every Monday.
Loop launched 2026-04-27 at https://loooop.dev with the tagline "Skills that never go stale." Source: Loop The product treats skills as living documents: attach sources (docs, changelogs, repos, RSS), set a refresh cadence, run a research agent, and save immutable version diffs. No silent overwrites.
The origin logic connects directly to No One-Off Work and wiki operating philosophy. If an agent workflow repeats, it belongs in automation, not chat memory. Loop exports raw skill endpoints (e.g. /api/skills/frontend-frontier/raw) so any agent always pulls the latest cron-refreshed version. Source: Loop
Architecture at launch: Supabase Postgres, Clerk auth, Stripe billing, Vercel AI Gateway routing, Firecrawl signal fetch, @vercel/queue job dispatch, and @vercel/sandbox for Node/Python agent sessions. Source: Loop Public catalog shipped ten actively refreshed skills and ten MCP servers on day one.
Content Backlog and Frontend and Design Skills link Loop to Kevin's public builder arc: open-source operator desk as proof of agent-native product thinking.
Timeline
- 2026-04-13 | Loop project page created. Source: Loop
- 2026-04-27 | Public launch at loooop.dev. Source: Loop
- 2026-05-31 | Story page compiled. Source: compiled from wiki graph