<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>OFFYCE Blog</title>
  <subtitle>Guides, deep dives, and comparisons on running multi-agent Claude Code: orchestration, agent memory, automation, and the tooling landscape.</subtitle>
  <link href="https://offyce.company/blog/feed.xml" rel="self" />
  <link href="https://offyce.company/blog/" />
  <updated>2026-08-19T00:00:00.000Z</updated>
  <id>https://offyce.company/blog/</id>
  <author><name>OFFYCE</name><uri>https://offyce.company</uri></author>
  <entry>
    <title>Our Agents Ran Our Launch-Week Analytics</title>
    <link href="https://offyce.company/blog/agents-ran-our-launch-week-analytics/" />
    <id>https://offyce.company/blog/agents-ran-our-launch-week-analytics/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Use Cases" />
    <summary>Ten Reddit threads, 501 comments, a Product Hunt page, GitHub traffic and PostHog funnels — read, cross-referenced, and reported by a hive of agents. The workflow, and how to point it at your own launch.</summary>
  </entry>
  <entry>
    <title>An Agent Redesigned the Blog You&#39;re Reading</title>
    <link href="https://offyce.company/blog/an-agent-redesigned-this-blog/" />
    <id>https://offyce.company/blog/an-agent-redesigned-this-blog/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Use Cases" />
    <summary>Reddit said our blog was unreadable and AI-sloppy. So one agent redesigned it end to end: a new editorial theme, and 119 hand-drawn hero illustrations rendered as code for exactly $0 in image APIs. This is the making-of.</summary>
  </entry>
  <entry>
    <title>Launching OFFYCE v0.4.4: Windows Agents Can Finally Talk</title>
    <link href="https://offyce.company/blog/launching-offyce-v0-4-4/" />
    <id>https://offyce.company/blog/launching-offyce-v0-4-4/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
    <summary>v0.4.4 fixes the bug that silently broke agent-to-agent messaging on Windows, starts hive services on the very first run, rebuilds dark mode so you can read it, and adds a 227-skill catalog, a Prerequisites page, and designed release notes.</summary>
  </entry>
  <entry>
    <title>Nº 5 Product of the Day: Our Product Hunt Launch, by the Numbers</title>
    <link href="https://offyce.company/blog/number-five-on-product-hunt/" />
    <id>https://offyce.company/blog/number-five-on-product-hunt/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
    <summary>OFFYCE finished #5 Product of the Day on Product Hunt — ahead of DeepSeek&#39;s harness launch that day. Here&#39;s what actually happened: the numbers, the people who showed up, and the two pieces of feedback we&#39;re already shipping fixes for.</summary>
  </entry>
  <entry>
    <title>Run a Release Train with Agents</title>
    <link href="https://offyce.company/blog/run-a-release-train-with-agents/" />
    <id>https://offyce.company/blog/run-a-release-train-with-agents/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Use Cases" />
    <summary>Version bumps, changelog entries, release notes in plain language, site updates, and link checks — the release chores that always slip are exactly the work a hive does well. The workflow behind our seven-releases-in-eight-days week.</summary>
  </entry>
  <entry>
    <title>Seven Releases in Eight Days: 0.3.8 → 0.4.4</title>
    <link href="https://offyce.company/blog/seven-releases-in-eight-days/" />
    <id>https://offyce.company/blog/seven-releases-in-eight-days/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
    <summary>Between August 11 and August 18 we shipped seven releases: memory condensation that finally works, an update checker, a whole new brand, a public telemetry contract, ten engines named honestly, and the Windows fix. The full tour.</summary>
  </entry>
  <entry>
    <title>The Newline That Silenced Every Windows Agent</title>
    <link href="https://offyce.company/blog/the-newline-that-silenced-windows-agents/" />
    <id>https://offyce.company/blog/the-newline-that-silenced-windows-agents/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Internals" />
    <summary>A cmd.exe parsing rule from the 1980s meant Windows agents received exactly one line of their multi-line startup protocol — and nothing errored. The anatomy of our worst silent failure, and the fix.</summary>
  </entry>
  <entry>
    <title>Turn a Firehose of Feedback into a Backlog with Agents</title>
    <link href="https://offyce.company/blog/turn-feedback-into-a-backlog-with-agents/" />
    <id>https://offyce.company/blog/turn-feedback-into-a-backlog-with-agents/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Use Cases" />
    <summary>516 Reddit comments, 27 Product Hunt threads, GitHub issues and Discord — launch week buries you in feedback that decays if unprocessed. The agent workflow that turned ours into a ranked backlog, with receipts.</summary>
  </entry>
  <entry>
    <title>We Opened a Discord (Merge a PR, Become Employee of the Month)</title>
    <link href="https://offyce.company/blog/we-opened-a-discord/" />
    <id>https://offyce.company/blog/we-opened-a-discord/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
    <summary>OFFYCE has a Discord now. Come watch releases land, get help with your floor, and earn the most thematically necessary contributor role in open source.</summary>
  </entry>
  <entry>
    <title>What 516 Reddit Comments Told Us About OFFYCE</title>
    <link href="https://offyce.company/blog/what-reddit-told-us-about-offyce/" />
    <id>https://offyce.company/blog/what-reddit-told-us-about-offyce/</id>
    <published>2026-08-19T00:00:00.000Z</published>
    <updated>2026-08-19T00:00:00.000Z</updated><category term="Story" />
    <summary>We launched across ten subreddits, collected 2,233 combined upvotes and 516 comments, and then read every single one. What landed, what got roasted, and what we shipped because of it.</summary>
  </entry>
  <entry>
    <title>What&#39;s Up With OFFYCE: Six Weeks, Four Releases, and the Part of the Stack You Actually Own</title>
    <link href="https://offyce.company/blog/whats-up-with-offyce/" />
    <id>https://offyce.company/blog/whats-up-with-offyce/</id>
    <published>2026-08-08T00:00:00.000Z</published>
    <updated>2026-08-08T00:00:00.000Z</updated><category term="Story" />
    <summary>Everything that shipped between v0.3.3 and v0.3.7 — a Michael who knows the floor and runs the app by voice, a git time-machine in the IDE, nine agent engines, a queue that respects your draft, Node that installs itself, and the auto-update bug that had been silently broken since the day we shipped it.</summary>
  </entry>
  <entry>
    <title>Our Auto-Update Never Ran Once: A CommonJS Export That Vanished Into an ESM Namespace</title>
    <link href="https://offyce.company/blog/why-our-auto-update-never-ran/" />
    <id>https://offyce.company/blog/why-our-auto-update-never-ran/</id>
    <published>2026-08-08T00:00:00.000Z</published>
    <updated>2026-08-08T00:00:00.000Z</updated><category term="Internals" />
    <summary>OFFYCE shipped auto-update in v0.3.4 and it silently never worked in a single packaged build. The cause was one destructuring assignment across the CommonJS/ESM boundary — and a catch block that threw the evidence away. Here&#39;s how we found it, and what v0.3.7 changes.</summary>
  </entry>
  <entry>
    <title>Launching OFFYCE v0.3.5: A Michael Who Knows the Floor, a Git Time-Machine, and an App That Updates Itself</title>
    <link href="https://offyce.company/blog/launching-offyce-v0-3-5/" />
    <id>https://offyce.company/blog/launching-offyce-v0-3-5/</id>
    <published>2026-08-06T00:00:00.000Z</published>
    <updated>2026-08-06T00:00:00.000Z</updated><category term="Story" />
    <summary>The v0.3.4 + v0.3.5 wave: voice orchestration with live floor context and full app control, markdown previews everywhere, commit history and branch compare in the built-in IDE, a six-tab Settings redesign, xAI Grok and Kimi Code engines, auto-update, and a queue that always has an escape hatch.</summary>
  </entry>
  <entry>
    <title>qm vs OFFYCE: YC&#39;s Multiplayer Harness or a Local-First Agent Office?</title>
    <link href="https://offyce.company/blog/qm-vs-offyce/" />
    <id>https://offyce.company/blog/qm-vs-offyce/</id>
    <published>2026-08-06T00:00:00.000Z</published>
    <updated>2026-08-06T00:00:00.000Z</updated><category term="Comparisons" />
    <summary>An honest comparison of YC&#39;s qm and OFFYCE: both orchestrate fleets of CLI coding agents with security postures, scheduled background work, and Slack — one as a headless multiplayer harness for teams, one as a local-first desktop office with real terminals, voice, and a built-in IDE.</summary>
  </entry>
  <entry>
    <title>The Command Center: Kanban, Fleet, and Budgets in One Place</title>
    <link href="https://offyce.company/blog/command-center-guide/" />
    <id>https://offyce.company/blog/command-center-guide/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Guides" />
    <summary>A guide to OFFYCE&#39;s Command Center — the task kanban, live fleet monitoring, per-agent budgets and cost telemetry — and when to watch the board instead of the floor.</summary>
  </entry>
  <entry>
    <title>CrewAI and AutoGen vs a Local Agent Harness: Framework or App?</title>
    <link href="https://offyce.company/blog/crewai-autogen-vs-a-local-agent-harness/" />
    <id>https://offyce.company/blog/crewai-autogen-vs-a-local-agent-harness/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Comparisons" />
    <summary>CrewAI, AutoGen (now Microsoft Agent Framework), and LangGraph are frameworks — Python you write to build your own agent system. A multi-agent harness is an app you download that runs a team on your repos today. Here&#39;s how to tell which one you actually need.</summary>
  </entry>
  <entry>
    <title>GitHub Copilot CLI vs Claude Code as Hive Workers</title>
    <link href="https://offyce.company/blog/github-copilot-cli-vs-claude-code-for-hive-work/" />
    <id>https://offyce.company/blog/github-copilot-cli-vs-claude-code-for-hive-work/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Comparisons" />
    <summary>How GitHub Copilot CLI and Claude Code behave as agent engines inside a multi-agent harness: hooks, inbox mail, orchestration, session lifecycle — and why the right answer is to run both.</summary>
  </entry>
  <entry>
    <title>How to Add a GitHub Copilot CLI Agent to Your Floor</title>
    <link href="https://offyce.company/blog/how-to-add-a-github-copilot-cli-agent/" />
    <id>https://offyce.company/blog/how-to-add-a-github-copilot-cli-agent/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Guides" />
    <summary>A step-by-step v0.3.3 walkthrough: install GitHub Copilot CLI (or let the harness install it for you), hire a Copilot worker, pick a model, and know exactly what print mode can and can&#39;t do.</summary>
  </entry>
  <entry>
    <title>How to Hire From the Agent Gallery</title>
    <link href="https://offyce.company/blog/how-to-hire-from-the-agent-gallery/" />
    <id>https://offyce.company/blog/how-to-hire-from-the-agent-gallery/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Guides" />
    <summary>A practical guide to OFFYCE&#39;s Agent Gallery: browse six off-the-shelf hires, import one from a link or file, review the pre-filled manifest, customize identity, workspace, engine, and briefing — then spawn it yourself.</summary>
  </entry>
  <entry>
    <title>How to Brief Your Orchestrator (So the Floor Actually Ships)</title>
    <link href="https://offyce.company/blog/how-to-talk-to-your-orchestrator/" />
    <id>https://offyce.company/blog/how-to-talk-to-your-orchestrator/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Guides" />
    <summary>A practical guide to briefing OFFYCE&#39;s GOD orchestrator: state the goal not the steps, set constraints and budgets, name the deliverable, and let Michael staff the floor. With bad-vs-good brief examples, mid-run steering, and Talk mode.</summary>
  </entry>
  <entry>
    <title>How to Use the Built-in Monaco IDE</title>
    <link href="https://offyce.company/blog/how-to-use-the-built-in-monaco-ide/" />
    <id>https://offyce.company/blog/how-to-use-the-built-in-monaco-ide/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Guides" />
    <summary>A practical walkthrough of OFFYCE v0.3.3&#39;s built-in Monaco IDE: the title-bar IDE button, the git CHANGES rail with side-by-side diffs vs HEAD, the file tree, tabs, Cmd/Ctrl+S save — and the agent review workflow it enables.</summary>
  </entry>
  <entry>
    <title>Launching OFFYCE v0.3.3: A Built-in Monaco IDE and GitHub Copilot CLI Support</title>
    <link href="https://offyce.company/blog/launching-offyce-v0-3-3/" />
    <id>https://offyce.company/blog/launching-offyce-v0-3-3/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Story" />
    <summary>OFFYCE v0.3.3 adds a full Monaco IDE — file tree, editor tabs, save, and side-by-side git diffs of your agents&#39; changes — plus GitHub Copilot CLI as a first-class agent engine, our first community-contributed provider.</summary>
  </entry>
  <entry>
    <title>Loop Engineering: Designing Agent Loops That Converge</title>
    <link href="https://offyce.company/blog/loop-engineering-for-ai-agents/" />
    <id>https://offyce.company/blog/loop-engineering-for-ai-agents/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Concepts" />
    <summary>Everyone engineers the prompt; almost nobody engineers the loop around it. Stop conditions, drain loops, retry with backoff, compaction cycles, breaker escalation, budgets, and human gates — the outer-loop mechanics that make an agent converge instead of run away.</summary>
  </entry>
  <entry>
    <title>Orca vs OFFYCE: Agent IDE or Agent Office?</title>
    <link href="https://offyce.company/blog/orca-vs-offyce/" />
    <id>https://offyce.company/blog/orca-vs-offyce/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Comparisons" />
    <summary>Orca is a YC-backed Agent IDE for driving coding agents side by side in isolated worktrees. OFFYCE is an agent office that runs itself. An honest comparison of the two — and when each one is the right pick.</summary>
  </entry>
  <entry>
    <title>Review Agent Work Where It Happens</title>
    <link href="https://offyce.company/blog/review-agent-work-where-it-happens/" />
    <id>https://offyce.company/blog/review-agent-work-where-it-happens/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Concepts" />
    <summary>AI agents produce diffs faster than humans can review them, and alt-tabbing to an external editor breaks supervision flow. The case for review-in-place: OFFYCE&#39;s built-in Monaco IDE puts a CHANGES rail and side-by-side diffs vs HEAD right on the office floor.</summary>
  </entry>
  <entry>
    <title>Run a Mixed-Engine Office: the Right CLI for Every Desk</title>
    <link href="https://offyce.company/blog/run-a-mixed-engine-office/" />
    <id>https://offyce.company/blog/run-a-mixed-engine-office/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Guides" />
    <summary>A practical guide to mixing agent engines on one OFFYCE floor: Claude Code as orchestrator, Codex for coding bursts, Copilot for dispatched tasks, and OpenCode/Crush/pi.dev for BYOK keys and local models.</summary>
  </entry>
  <entry>
    <title>Running Agents in tmux vs an Agent Harness</title>
    <link href="https://offyce.company/blog/tmux-and-scripts-vs-an-agent-harness/" />
    <id>https://offyce.company/blog/tmux-and-scripts-vs-an-agent-harness/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Comparisons" />
    <summary>tmux panes, git worktrees, shell scripts, and cron will absolutely run several Claude Code sessions at once. Here&#39;s what that DIY setup does well, where it breaks at scale, and what a purpose-built agent harness automates.</summary>
  </entry>
  <entry>
    <title>Voice Is a Control Plane, Not a Gimmick</title>
    <link href="https://offyce.company/blog/voice-as-a-control-plane-for-agent-fleets/" />
    <id>https://offyce.company/blog/voice-as-a-control-plane-for-agent-fleets/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Concepts" />
    <summary>Voice is a terrible way to write code and a great way to run a fleet. Why low-bandwidth commands over high-bandwidth work is the right split — with OFFYCE&#39;s Talk mode (echo-back confirmation, spend caps, michael-voice attribution) as the case study.</summary>
  </entry>
  <entry>
    <title>What Is an Agent Development Environment (ADE)?</title>
    <link href="https://offyce.company/blog/what-is-an-agent-development-environment/" />
    <id>https://offyce.company/blog/what-is-an-agent-development-environment/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Concepts" />
    <summary>ADE means two things in 2026: a platform for building agents (Letta&#39;s sense) and a workspace for shipping code with fleets of coding agents (Orca&#39;s sense). Here&#39;s the full tooling map — chat IDEs, agent CLIs, agent IDEs, and agent harnesses — and how to pick.</summary>
  </entry>
  <entry>
    <title>What Is Harness Engineering?</title>
    <link href="https://offyce.company/blog/what-is-harness-engineering/" />
    <id>https://offyce.company/blog/what-is-harness-engineering/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Concepts" />
    <summary>Harness engineering is the discipline of building everything around the model — PTY plumbing, lifecycle hooks, mailboxes, memory, budgets, human gates, observability — because that&#39;s where agent reliability actually comes from. A definition, and four case studies from inside OFFYCE.</summary>
  </entry>
  <entry>
    <title>Your First Hour With OFFYCE</title>
    <link href="https://offyce.company/blog/your-first-hour-with-offyce/" />
    <id>https://offyce.company/blog/your-first-hour-with-offyce/</id>
    <published>2026-07-03T00:00:00.000Z</published>
    <updated>2026-07-03T00:00:00.000Z</updated><category term="Guides" />
    <summary>A minute-by-minute walkthrough of your first hour with OFFYCE: install, the onboarding wizard, your first brief to Michael, watching the floor, approving your first escalation, and leaving a schedule running.</summary>
  </entry>
  <entry>
    <title>Launching OFFYCE v0.3.2: Talk to Michael, a Realtime Voice Orchestrator</title>
    <link href="https://offyce.company/blog/launching-offyce-v0-3-2/" />
    <id>https://offyce.company/blog/launching-offyce-v0-3-2/</id>
    <published>2026-06-27T00:00:00.000Z</published>
    <updated>2026-06-27T00:00:00.000Z</updated><category term="Story" />
    <summary>OFFYCE v0.3.2 adds Realtime Michael — a low-latency voice channel to the GOD orchestrator. Talk to Michael and he listens, answers, and acts: reading the hive and, behind spoken echo-back confirmation, dispatching, spawning, and steering the floor in real time.</summary>
  </entry>
  <entry>
    <title>Run OFFYCE Locally on a Mac Mini</title>
    <link href="https://offyce.company/blog/run-offyce-on-a-mac-mini/" />
    <id>https://offyce.company/blog/run-offyce-on-a-mac-mini/</id>
    <published>2026-06-22T00:00:00.000Z</published>
    <updated>2026-06-22T00:00:00.000Z</updated><category term="Guides" />
    <summary>A step-by-step guide to running a whole OFFYCE hive offline on an Apple Silicon Mac Mini — how to size models to your unified memory, install Ollama or LM Studio, and wire OpenCode and Crush to a local endpoint.</summary>
  </entry>
  <entry>
    <title>Run OFFYCE on Open-Source Models — Fully Local or via a Third-Party Provider</title>
    <link href="https://offyce.company/blog/run-offyce-on-open-models/" />
    <id>https://offyce.company/blog/run-offyce-on-open-models/</id>
    <published>2026-06-22T00:00:00.000Z</published>
    <updated>2026-06-22T00:00:00.000Z</updated><category term="Guides" />
    <summary>OFFYCE v0.3.1 runs your agent floor on open-weight models — gpt-oss, Qwen3, DeepSeek, Llama, Mistral, GLM, Kimi — either fully local (Ollama/LM Studio/vLLM) or through a third-party OSS provider. Here&#39;s how to wire each across the OpenCode, Crush, and pi engines.</summary>
  </entry>
  <entry>
    <title>Launching OFFYCE v0.3.0: Selectable Engines, Integrations &amp; Slack-Spawned Workers</title>
    <link href="https://offyce.company/blog/launching-offyce-v0-3-0/" />
    <id>https://offyce.company/blog/launching-offyce-v0-3-0/</id>
    <published>2026-06-21T00:00:00.000Z</published>
    <updated>2026-06-21T00:00:00.000Z</updated><category term="Story" />
    <summary>OFFYCE v0.3.0 makes every hire — and Michael himself — a pluggable engine, adds an integrations registry with a write-only secret broker, and lets the god orchestrator spawn an ephemeral worker straight from Slack.</summary>
  </entry>
  <entry>
    <title>Treating a Hire Manifest as Untrusted Input</title>
    <link href="https://offyce.company/blog/hire-manifest-untrusted-input/" />
    <id>https://offyce.company/blog/hire-manifest-untrusted-input/</id>
    <published>2026-06-15T00:00:00.000Z</published>
    <updated>2026-06-15T00:00:00.000Z</updated><category term="Internals" />
    <summary>A shareable agent-config manifest is attacker input. How OFFYCE&#39;s import pipeline stays inert: no auto-spawn, default-deny flags, and an SSRF-safe bounded fetch.</summary>
  </entry>
  <entry>
    <title>Launching OFFYCE v0.2.8: Shareable Hires</title>
    <link href="https://offyce.company/blog/launching-offyce-v0-2-8/" />
    <id>https://offyce.company/blog/launching-offyce-v0-2-8/</id>
    <published>2026-06-15T00:00:00.000Z</published>
    <updated>2026-06-15T00:00:00.000Z</updated><category term="Story" />
    <summary>OFFYCE v0.2.8 ships Shareable Hires: a one-click, portable agent role manifest + The Hiring Fair gallery. Click a hire link, review every field, then spawn it yourself.</summary>
  </entry>
  <entry>
    <title>Shareable Agent Roles: A Portable Format for Hiring AI Coworkers</title>
    <link href="https://offyce.company/blog/shareable-agent-roles/" />
    <id>https://offyce.company/blog/shareable-agent-roles/</id>
    <published>2026-06-15T00:00:00.000Z</published>
    <updated>2026-06-15T00:00:00.000Z</updated><category term="Concepts" />
    <summary>Why agent roles should be portable: what a hire manifest encodes, how one-click hiring stays safe, and how The Hiring Fair turns tacit setup into a shareable artifact.</summary>
  </entry>
  <entry>
    <title>Deploy a Blog-Writer Agent: The One That Wrote This Post</title>
    <link href="https://offyce.company/blog/deploy-a-blog-writer-agent/" />
    <id>https://offyce.company/blog/deploy-a-blog-writer-agent/</id>
    <published>2026-06-10T00:00:00.000Z</published>
    <updated>2026-06-10T00:00:00.000Z</updated><category term="Use Cases" />
    <summary>How OFFYCE&#39;s blog is written by an automated writer agent in the hive — drafts in a worktree, single-committer integration, Eleventy build, human-gated deploy. Build your own.</summary>
  </entry>
  <entry>
    <title>Deploy a PR Reviewer That Never Sleeps — In About One Prompt</title>
    <link href="https://offyce.company/blog/deploy-automated-pr-reviewer-agent/" />
    <id>https://offyce.company/blog/deploy-automated-pr-reviewer-agent/</id>
    <published>2026-06-10T00:00:00.000Z</published>
    <updated>2026-06-10T00:00:00.000Z</updated><category term="Orchestration" />
    <summary>A how-to for standing up a fully automated PR-reviewing agent in OFFYCE — one that reads your real source (not just the PR description), de-dupes noise, and only escalates what matters. With a real triage run that turned 22 duplicate firings into a clean v0.2.5 patch queue.</summary>
  </entry>
  <entry>
    <title>Run Your AI Agent Hive from Slack: The Complete Setup</title>
    <link href="https://offyce.company/blog/run-ai-agent-hive-from-slack-setup/" />
    <id>https://offyce.company/blog/run-ai-agent-hive-from-slack-setup/</id>
    <published>2026-06-10T00:00:00.000Z</published>
    <updated>2026-06-10T00:00:00.000Z</updated><category term="Guides" />
    <summary>Step-by-step setup for driving OFFYCE&#39;s AI agent hive from Slack: create the app, set scopes, paste the tunnel Request URL, and @mention your bot to start work — done-summaries post back in-thread.</summary>
  </entry>
  <entry>
    <title>The Clone Army Is a Trap: Why a Mixed Swarm Beats Ten Identical Agents</title>
    <link href="https://offyce.company/blog/the-clone-army-trap-mixed-swarm-vs-identical-agents/" />
    <id>https://offyce.company/blog/the-clone-army-trap-mixed-swarm-vs-identical-agents/</id>
    <published>2026-06-10T00:00:00.000Z</published>
    <updated>2026-06-10T00:00:00.000Z</updated><category term="Concepts" />
    <summary>Spinning up tens of identical top-tier CLI agents feels powerful and burns tokens on work a cheaper agent could do. A mixed-capability swarm with shared memory wins on cost — and often on quality.</summary>
  </entry>
  <entry>
    <title>How to Trigger Your AI Agent Hive from a GitHub Webhook</title>
    <link href="https://offyce.company/blog/trigger-ai-agents-from-github-webhook/" />
    <id>https://offyce.company/blog/trigger-ai-agents-from-github-webhook/</id>
    <published>2026-06-10T00:00:00.000Z</published>
    <updated>2026-06-10T00:00:00.000Z</updated><category term="Guides" />
    <summary>Wire a GitHub webhook to OFFYCE: a secret-gated local endpoint turns each repo event into a task for your GOD orchestrator — POST a message, get a token, poll the result. No server to host.</summary>
  </entry>
  <entry>
    <title>Why CLI Agents Are So Powerful — and How OFFYCE Spends Fewer Tokens Doing the Same Work</title>
    <link href="https://offyce.company/blog/why-cli-agents-are-powerful/" />
    <id>https://offyce.company/blog/why-cli-agents-are-powerful/</id>
    <published>2026-06-10T00:00:00.000Z</published>
    <updated>2026-06-10T00:00:00.000Z</updated><category term="Concepts" />
    <summary>CLI agents are powerful because they have terminal-level access: they run builds, tests, and git, and verify their own work by executing it. Here&#39;s why that matters — and the concrete ways OFFYCE cuts token consumption while doing it.</summary>
  </entry>
  <entry>
    <title>Launching OFFYCE v0.2.4</title>
    <link href="https://offyce.company/blog/launching-offyce-v0-2-4/" />
    <id>https://offyce.company/blog/launching-offyce-v0-2-4/</id>
    <published>2026-06-09T00:00:00.000Z</published>
    <updated>2026-06-09T00:00:00.000Z</updated><category term="Story" />
    <summary>OFFYCE v0.2.4 is here: Claude Code, OpenAI Codex, and Antigravity (Gemini) agents now run as one hive with full parity — no API keys, no setup. Brief a GOD orchestrator, automate basically anything in one prompt, and close the lid while it keeps working.</summary>
  </entry>
  <entry>
    <title>OFFYCE v0.2.4 Feature Walkthrough</title>
    <link href="https://offyce.company/blog/offyce-v0-2-4-feature-walkthrough/" />
    <id>https://offyce.company/blog/offyce-v0-2-4-feature-walkthrough/</id>
    <published>2026-06-09T00:00:00.000Z</published>
    <updated>2026-06-09T00:00:00.000Z</updated><category term="Guides" />
    <summary>A comprehensive guide to every change in OFFYCE v0.2.4 — how the Codex lifecycle-hook bridge achieves full hive parity, what the Schedules tab adds, why tunnelmole replaced localtunnel, and what else shipped.</summary>
  </entry>
  <entry>
    <title>Launching OFFYCE v0.2.0</title>
    <link href="https://offyce.company/blog/launching-offyce-v0-2-0/" />
    <id>https://offyce.company/blog/launching-offyce-v0-2-0/</id>
    <published>2026-06-07T00:00:00.000Z</published>
    <updated>2026-06-07T00:00:00.000Z</updated><category term="Story" />
    <summary>OFFYCE v0.2.0 is here: a Command Center overhaul, per-agent token budgets, live OpenTelemetry observability, a circuit breaker, durable SQLite persistence, and a big round of community fixes.</summary>
  </entry>
  <entry>
    <title>One Prompt, Five PR Reviews, and an Hourly Automation — A Dogfooding Story</title>
    <link href="https://offyce.company/blog/one-prompt-automated-pr-review/" />
    <id>https://offyce.company/blog/one-prompt-automated-pr-review/</id>
    <published>2026-06-07T00:00:00.000Z</published>
    <updated>2026-06-07T00:00:00.000Z</updated><category term="Story" />
    <summary>How a single prompt to the OFFYCE god agent reviewed all open PRs and set up a recurring hourly PR reviewer — while the repo was blowing up with 400+ stars.</summary>
  </entry>
  <entry>
    <title>Does the June 2026 Agent SDK Change Affect OFFYCE?</title>
    <link href="https://offyce.company/blog/does-the-june-2026-agent-sdk-change-affect-offyce/" />
    <id>https://offyce.company/blog/does-the-june-2026-agent-sdk-change-affect-offyce/</id>
    <published>2026-06-06T00:00:00.000Z</published>
    <updated>2026-06-06T00:00:00.000Z</updated><category term="Guides" />
    <summary>From June 15, 2026 the Claude Agent SDK gets a separate credit. OFFYCE drives the native Claude Code CLI, so your hive runs on your plan as before.</summary>
  </entry>
  <entry>
    <title>The Best AI Coding Agents in 2026: A Field Guide</title>
    <link href="https://offyce.company/blog/best-ai-coding-agents/" />
    <id>https://offyce.company/blog/best-ai-coding-agents/</id>
    <published>2026-06-05T00:00:00.000Z</published>
    <updated>2026-06-05T00:00:00.000Z</updated><category term="Comparisons" />
    <summary>A fair 2026 field guide to the best AI coding agents — Cursor, Aider, Cline, Devin, Copilot — by category, plus where a local multi-agent hive fits.</summary>
  </entry>
  <entry>
    <title>Cline vs OFFYCE: In-Editor Agent or Local Hive?</title>
    <link href="https://offyce.company/blog/cline-vs-offyce/" />
    <id>https://offyce.company/blog/cline-vs-offyce/</id>
    <published>2026-06-05T00:00:00.000Z</published>
    <updated>2026-06-05T00:00:00.000Z</updated><category term="Comparisons" />
    <summary>A fair comparison of Cline and OFFYCE — an in-editor BYOK coding agent vs a local multi-agent orchestration hive — and when to pick which.</summary>
  </entry>
  <entry>
    <title>Compressing Agent Memory Without Losing the Original</title>
    <link href="https://offyce.company/blog/compressing-agent-memory/" />
    <id>https://offyce.company/blog/compressing-agent-memory/</id>
    <published>2026-06-05T00:00:00.000Z</published>
    <updated>2026-06-05T00:00:00.000Z</updated><category term="Internals" />
    <summary>How and why to compress an agent&#39;s long-term memory: the toolbox, the lossy trap, and keeping a lossless original beside a compact copy.</summary>
  </entry>
  <entry>
    <title>Generative Engine Optimization: The Techniques the Research Backs</title>
    <link href="https://offyce.company/blog/generative-engine-optimization-techniques/" />
    <id>https://offyce.company/blog/generative-engine-optimization-techniques/</id>
    <published>2026-06-05T00:00:00.000Z</published>
    <updated>2026-06-05T00:00:00.000Z</updated><category term="Concepts" />
    <summary>What the first peer-reviewed GEO study found works to get content cited by AI — statistics, source citations, quotes — and why keyword stuffing backfires.</summary>
  </entry>
  <entry>
    <title>How to Install and Use OFFYCE</title>
    <link href="https://offyce.company/blog/how-to-install-and-use-offyce/" />
    <id>https://offyce.company/blog/how-to-install-and-use-offyce/</id>
    <published>2026-06-05T00:00:00.000Z</published>
    <updated>2026-06-05T00:00:00.000Z</updated><category term="Guides" />
    <summary>Install OFFYCE on macOS, Windows, or Linux and put a hive of Claude Code agents to work on ambitious, long-horizon tasks — start to finish.</summary>
  </entry>
  <entry>
    <title>MCP Tool Poisoning: How to Secure the Model Context Protocol</title>
    <link href="https://offyce.company/blog/mcp-security-tool-poisoning/" />
    <id>https://offyce.company/blog/mcp-security-tool-poisoning/</id>
    <published>2026-06-05T00:00:00.000Z</published>
    <updated>2026-06-05T00:00:00.000Z</updated><category term="Guides" />
    <summary>How the Model Context Protocol gets attacked — tool poisoning, rug pulls, command injection — and the layered defenses that secure your MCP tools.</summary>
  </entry>
  <entry>
    <title>Multi-Agent Orchestration Patterns: Which Topology, and When</title>
    <link href="https://offyce.company/blog/multi-agent-orchestration-patterns/" />
    <id>https://offyce.company/blog/multi-agent-orchestration-patterns/</id>
    <published>2026-06-05T00:00:00.000Z</published>
    <updated>2026-06-05T00:00:00.000Z</updated><category term="Orchestration" />
    <summary>The multi-agent orchestration patterns — orchestrator-worker, pipeline, fan-out, debate, swarm, blackboard — when to use each, and when one agent wins.</summary>
  </entry>
  <entry>
    <title>The Multi-Agent Cost Playbook: Five Levers to Cut AI Agent Spend</title>
    <link href="https://offyce.company/blog/the-multi-agent-cost-playbook/" />
    <id>https://offyce.company/blog/the-multi-agent-cost-playbook/</id>
    <published>2026-06-05T00:00:00.000Z</published>
    <updated>2026-06-05T00:00:00.000Z</updated><category term="Guides" />
    <summary>Caching, batching, model tiering, context discipline, local-first — the five levers that cut a multi-agent fleet&#39;s bill, and how they compound.</summary>
  </entry>
  <entry>
    <title>Running AI Agents Safely: Permission Modes and Sandboxing</title>
    <link href="https://offyce.company/blog/agent-security-and-sandboxing/" />
    <id>https://offyce.company/blog/agent-security-and-sandboxing/</id>
    <published>2026-06-04T00:00:00.000Z</published>
    <updated>2026-06-04T00:00:00.000Z</updated><category term="Guides" />
    <summary>How to run autonomous AI agents safely: permission modes and the bypassPermissions foot-gun, workspace isolation, and what to gate vs. allow.</summary>
  </entry>
  <entry>
    <title>The Agents Rule of Two: A Simple Safety Rule for Coding Agents</title>
    <link href="https://offyce.company/blog/agents-rule-of-two/" />
    <id>https://offyce.company/blog/agents-rule-of-two/</id>
    <published>2026-06-04T00:00:00.000Z</published>
    <updated>2026-06-04T00:00:00.000Z</updated><category term="Concepts" />
    <summary>Meta&#39;s Agents Rule of Two for coding agents: don&#39;t let one session combine untrusted input, private data, and external reach at once — or supervise.</summary>
  </entry>
  <entry>
    <title>OFFYCE&#39;s Architecture: Two Data Planes, One Renderer</title>
    <link href="https://offyce.company/blog/architecture-two-planes-one-renderer/" />
    <id>https://offyce.company/blog/architecture-two-planes-one-renderer/</id>
    <published>2026-06-04T00:00:00.000Z</published>
    <updated>2026-06-04T00:00:00.000Z</updated><category term="Internals" />
    <summary>A walkthrough of the multi-agent harness architecture: a node-pty terminal plane and a hooks/hive event plane feeding one React + Pixi.js renderer.</summary>
  </entry>
</feed>
