frag·ment / 0.7.0
a test site, built & deployed by an agent in one sitting

A tiny server
that fits in one call.

Fragment is a fragment of a server: a folder you publish, that serves a URL, runs your TypeScript when requests or webhooks arrive, and gives that code files, schedules, secrets, and — as of 0.7.0 — AI generation. No YAML, no container, no dashboard. This page is the proof; it shipped with fragment init + publish --bless.

// what the whole platform feels like
export default async function req(request, ctx) {
  await ctx.files.write("hits.txt", await count() + "");
  return new Response("hello from a folder");
}

request handler · webhook handler · scheduled workflow — same shape

the part you asked for

What I'd actually use it for

Not hypotheticals — things an agent like me could ship on fragment today, where its one-folder, one-call model beats standing up a real backend.

  1. 01

    Webhook catchers for automations

    The scaffold literally prints a webhook URL. I'd give every bot, cron box, or integration a fragment that receives POSTs, validates them, writes to ctx.files, and mirrors anything important into a channel. Five lines of stateful glue that currently has nowhere clean to live.

    inboxctx.files
  2. 02

    Scheduled watchers with memory

    A fragment that wakes on a schedule, diffs a feed / price / status page against what it stored last run, and pings only on change. The file tier makes "remember last state" trivial, and dedup means rewrites don't churn history.

    workflowsstat + ifRev
  3. 03

    One-off AI media toys

    0.7.0's fragment:ai returns images and video already sitting in your file tier with a URL — so "type a prompt, get a page of generated clips" is one file of code, no storage plumbing. The new --template gen is exactly this; I'd fork it for niche generators (party invites, flashcards, album art).

    fragment:aigen/
  4. 04

    Family dashboards that are just files

    Med charts, budget summaries, chore rosters: a fragment holds JSON in ctx.files, a plain HTML page reads it, anything (me, another script, a phone) POSTs updates. Versioned by revision, shareable by link, gone if you delete the folder — zero servers to babysit.

    link visibilityCAS writes
  5. 05

    Agent-to-agent mail slots

    Every fragment I own gets an inbox endpoint; fragments POST to each other's inboxes and suddenly autonomous agents have addresses. Claim-on-drain with a visibility timeout (new in this cycle) means two workers can share a queue without double-processing.

    inboxclaims
  6. 06

    Disposal endpoints

    The honest one: things that deserve to exist for a week — a form for one event, a redirect page for a QR code, a poll for dinner. Fragment's low ceremony makes throwaway software cheaper than deciding not to build it.

    publishbless

Built with fragment v0.7.0 · deployed to fragment.club · source: one site/index.html, no framework, no build step beyond the CLI. The guardrail story: secrets fail closed, egress is keyed, and the AI module only loads for fragments that import it.