Skip to main content

30 posts shown

  1. Promise theory described agents that observe, reason, and commit. The IaC generation never delivered it and CFEngine came closest. LLMs supplied the missing reasoning layer, and swamp is built for…

    by @webframp

  2. The End of Vendor Lock-inblog.watson-labs.co.uk

    Four architectures in six weeks, under live production traffic, with no maintenance window. We didn't see any of the infrastructure requirements coming, and it didn't matter.

    by @swamp_lord

  3. Swamp is a command-line automation framework designed to be operated by AI coding agents. It gives recurring work a durable shape. Instead of asking an…

    by @alvagante

  4. A Google Photos picker session that timed out mid-selection was recovered by extracting opaque media IDs from the still-rendered DOM via DevTools, then replaying those IDs to re-select 154 photos in…

    by @mgreten

  5. The FASJSON model only spoke Kerberos, so my swamp had to kinit. I got annoyed enough to reimplement the client half of GSSAPI in TypeScript with no subprocess, and then the immutable datastore…

    by @kneel

  6. How do I get repeatable results out of AI agents in production?

    by @adam

  7. Vibe coding, spec engineering, loops, graphs. The labels keep changing because the model keeps changing. Every practice you build to compensate for today's model has a half-life, and the model is…

    by @stack72

  8. A developer reflects on how a PR-stacking pipeline design outlived two of its three original constraints — hardware limits and migration ordering — without being noticed until an offhand conversation…

    by @mgreten

  9. A reply to twonines' 'What the Factory Forgets': the recordpriorart harvest loop is the memory that sits inside my agent factory, so ephemeral caged agents still arrive warm.

    by @magistr

  10. How issue-lifecycle grew from a borrowed state machine into swamp-go-brr: the harvest/prior-art loop, the changes along the way, and the turn from human-in-the-loop to autonomous.

    by @magistr

  11. A developer builds a release-adoption pipeline for the "swamp" tool using typed, persistent workflow steps and the new CEL-based assert task type, discovering and fixing a CLI-diff parser bug in the…

    by @mgreten

  12. A developer builds a Swamp extension for Valetudo-flashed robot vacuums that uses Homie MQTT metadata to give agents a typed, self-describing contract of what the robot can do before issuing any…

    by @mgreten

  13. Four fixes into a DynamoDB sync backend, the ceiling kept moving: from a hot GSI partition to lock contention to catalog metadata no datastore could outrun.

    by @webframp

  14. A developer documents how two CLI-agent invocations against Claude unexpectedly exhausted a $20 subscription by expanding into dozens of internal turns and millions of cache-read tokens, revealing…

    by @mgreten

  15. Gaming Swamp Questbytes.helson.nz

    Quick intro Simon here - I got nudged in the direction of swamp quest yesteray morning, and quickly came to the conclusion that the way to make it fun would be to make the challenge about using as…

    by @shelson

  16. A developer replaced a travel meal-expense spreadsheet with a conversational agent backed by a structured, versioned data store, separating the accounting logic from the chat interface to reduce…

    by @mgreten

  17. A developer built a Swamp model called @mgreten/trip-packing that generates categorized packing lists from trip parameters and creates Todoist projects with idempotent, hash-marker-based…

    by @mgreten

  18. A walkthrough of configuring an AI assistant called Hermes to route tasks through a composable automation layer called Swamp, disabling broad built-in toolsets and installing a narrow adapter plugin…

    by @mgreten

  19. Adventures with config management in the swamp ecosuystem

    by @shelson

  20. This is a reflection of a post written by Sean aka webframp on a serious load test performed against the club. An insight into how it looked from the other side. I spent this last Saturday hacking on

    by @keeb

  21. A load test that briefly knocked out Swamp's telemetry pipeline, and what it took for that to read as curiosity instead of an attack.

    by @webframp

  22. Two extensions covering the same domain means the ecosystem is growing. That's not a governance problem.

    by @webframp

  23. The Keyboard on Floor 3blog.watson-labs.co.uk

    For six months, a sticky note on a London hotdesk read: “The S key is sticky, sorry - Mandeep.” What that note did to one keyboard explains exactly what agentic memory toxicity is.

    by @swamp_lord

  24. A developer describes building an agent-assisted workflow ("Swamp") to automate batch Frigate NVR exports across multiple cameras when an incident occurs, solving the problem of labor-intensive…

    by @mgreten

  25. A homelab owner describes building an AI-assisted workflow that monitors UniFi firmware releases, deduplicates version alerts, and schedules multi-stage research reviews over 21 days before…

    by @mgreten

  26. Weirtwonines.codeberg.page

    Why I built a tool whose job is to say no, and why shell access for AI agents is a pattern ready to retire.

    by @jeremy

  27. I ran a real job search through an open-source AI pipeline and learned swamp by building an extension for it in public. What the tooling replaced, what it didn't, and the honest funnel so far.

    by @sntxrr

  28. Building a Swamp Workflow reduced real world token usage of an AI Agent by 8x and improved execution time by 2x - here is how to do it yourself.

    by @adam

  29. How we built a self-hosted health pipeline with the Google Health API, Swamp extension models, and Claude — from a Xiaomi login dead end, through probing a closed API and reverse-engineering Fitbit's…

    by @magistr