<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Agent Harness Guide</title>
  <subtitle>An independent reference on agent harnesses: what a harness owns, where each open source runtime keeps its state, and why Kortix, the open-source AI Operating System, keeps it in git.</subtitle>
  <link rel="self" type="application/atom+xml" href="https://agentharnessguide.com/feed.xml"/>
  <link rel="alternate" type="text/html" href="https://agentharnessguide.com/"/>
  <link rel="hub" href="https://pubsubhubbub.appspot.com/"/>
  <id>https://agentharnessguide.com/</id>
  <updated>2026-10-27T00:00:00Z</updated>
  <author><name>Agent Harness Guide</name></author>
  <entry>
    <title>What an Agent Harness Owns, and Where Open Source Keeps It</title>
    <link rel="alternate" type="text/html" href="https://agentharnessguide.com/"/>
    <link rel="alternate" type="text/markdown" href="https://agentharnessguide.com/index.md"/>
    <id>https://agentharnessguide.com/</id>
    <updated>2026-10-27T00:00:00Z</updated>
    <summary>An agent harness is everything around the model: loop, tools, sandbox, approval rule and session state. Kortix, open source, keeps them in git.</summary>
    <content type="text">An agent harness is every part of an agent that is not the model: the loop, the tools, the sandbox, the approval rule and the state that outlives a run. Two teams on the same model finish different amounts of work because those parts differ, and in Kortix they are files in a git repo you own.</content>
  </entry>
  <entry>
    <title>Agent Harness Comparison: Where Open Source Runtimes Keep State</title>
    <link rel="alternate" type="text/html" href="https://agentharnessguide.com/agent-harness-comparison"/>
    <link rel="alternate" type="text/markdown" href="https://agentharnessguide.com/agent-harness-comparison.md"/>
    <id>https://agentharnessguide.com/agent-harness-comparison</id>
    <updated>2026-10-27T00:00:00Z</updated>
    <summary>Four open source agent harnesses compared on where they run, how a tool call gets approved, and where session state survives.</summary>
    <content type="text">Four open source agent harnesses compared on the one fact that outlives the session: where the agent’s state lives. Kortix is the open-source AI Operating System: your agents, their skills, your company memory, and every connector in one git repo you own, with the agents working on real cloud computers.</content>
  </entry>
  <entry>
    <title>Open Source Agent Harness: Choose the Layer, Not the Logo</title>
    <link rel="alternate" type="text/html" href="https://agentharnessguide.com/open-source-agent-harness"/>
    <link rel="alternate" type="text/markdown" href="https://agentharnessguide.com/open-source-agent-harness.md"/>
    <id>https://agentharnessguide.com/open-source-agent-harness</id>
    <updated>2026-10-27T00:00:00Z</updated>
    <summary>Open-source agent harness lists compare projects; the pick turns on your layer, a coding CLI, an embeddable runtime or a team layer.</summary>
    <content type="text">An agent harness is the runtime around a model. It holds the loop, the tools, the sandbox and the approval rule. Lists compare project names, yet the choice that holds is which layer you need, because a harness can be open at one layer and closed at the next. Kortix is the open-source AI Operating System.</content>
  </entry>
  <entry>
    <title>Codex harness: the open source loop, and where its config lives</title>
    <link rel="alternate" type="text/html" href="https://agentharnessguide.com/codex-harness"/>
    <link rel="alternate" type="text/markdown" href="https://agentharnessguide.com/codex-harness.md"/>
    <id>https://agentharnessguide.com/codex-harness</id>
    <updated>2026-10-27T00:00:00Z</updated>
    <summary>The Codex harness is OpenAI’s open source agent loop, with approval and sandbox rules in a config file. What it owns, and what a team still owns.</summary>
    <content type="text">The Codex harness is OpenAI’s open-source agent loop: it manages conversation state, streams execution, uses tools, enforces a sandbox and approval policy, and carries work across turns. Its policy file and session record stay with whoever runs the process. Kortix, the open-source AI Operating System, keeps that layer in a git repo.</content>
  </entry>
  <entry>
    <title>Claude Code Harness Permissions, and the Open-Source Repo That Keeps Them</title>
    <link rel="alternate" type="text/html" href="https://agentharnessguide.com/claude-code-harness"/>
    <link rel="alternate" type="text/markdown" href="https://agentharnessguide.com/claude-code-harness.md"/>
    <id>https://agentharnessguide.com/claude-code-harness</id>
    <updated>2026-10-27T00:00:00Z</updated>
    <summary>Claude Code harness permissions decide what gets written, and open source keeps the other four configurable layers in a repo you own.</summary>
    <content type="text">A Claude Code harness is the loop, tools, context management and guardrails Anthropic built around the model, and most of what you change sits in settings files rather than in the harness. Kortix is the open-source AI Operating System, where the same layers live in a git repo.</content>
  </entry>
  <entry>
    <title>Best Agent Harness: Open Source, Three Questions, Not the Model</title>
    <link rel="alternate" type="text/html" href="https://agentharnessguide.com/best-agent-harness"/>
    <link rel="alternate" type="text/markdown" href="https://agentharnessguide.com/best-agent-harness.md"/>
    <id>https://agentharnessguide.com/best-agent-harness</id>
    <updated>2026-10-27T00:00:00Z</updated>
    <summary>No harness is best in the abstract: who approves tool calls, where session state survives and who runs the machine decide yours. Kortix is open source.</summary>
    <content type="text">Which harness fits your work turns on three facts about it, and on a fourth that gets more weight than it deserves: the model. Kortix, the open-source AI Operating System, lays out the three, maps your answers to a harness shape, and shows where each project keeps the configuration.</content>
  </entry>
</feed>
