tade — blog / agents

blog / tag

#agents

6 posts, newest first.

  1. Tade on a server of yours, and one window over all of it3 min

    A VPS of yours runs Tade with the laptop shut, and the Mac's window shows and drives every machine's projects over SSH. One Tade per machine, nothing merged.

    remotevpsagentssafety

  2. Run as many coding agents as you can land4 min

    Running agents in parallel is the easy half. Landing their work is the queue, and you are it — so that is the half Tade now leads with.

    landingagentsjevreview

  3. Tade Away: the control room, on a phone you paired9 min

    Agents run for hours, and nobody should have to sit with them. Tade Away puts the control room on a phone you paired, served by the Tade window itself.

    awayagentssafety

  4. A queue that holds, and says why it did4 min

    Three agents built this blog in order. Six times in September a fourth was held because another was already mid-edit in the files it planned to change.

    queueagentsdesign

  5. From a red main to green in thirty-six minutes5 min

    On 28 September ubuntu-latest went red on Tade's own main at 08:15. A watch found it at 08:20, an agent removed the race, and CI was green again by 08:51.

    ciwatcheschecksagents

  6. Why a task never spans two repositories4 min

    One orchestrator runs agents in every repository at once. What it refuses to do is let a single task span two of them, and the reason is git rather than tidiness.

    multi-repodesignagents

blog#agents│6 posts│latest 2026-10-18