Kenon

Context protocol and concurrency coordination layer for coding agents. Keep them working continuously without losing state, boundaries, and evidence.面向 Coding Agents 的上下文协议与并发协调层,让 Agent 在真实工程里持续工作而不失去状态、边界和证据。

Install in 2 minutes. Stop letting your Agents understand the repo from scratch every time.2 分钟装上,让你的 Agent 不再每次都从零理解仓库。

Deps
Time
dns SPACE
Intent
Quality

Agents don't just need code context.
They need state, boundaries, evidence, and continuity.
Agents 需要的远不止代码上下文。
它们更渴望状态、边界、证据与连续性。

Stateless Context无状态的上下文交互
radio_button_unchecked

Broad codebase scanning泛化的代码库检索

Information density dilutes core instructions.过高的信息密度容易导致模型偏离焦点。

radio_button_unchecked

Unbounded execution scope隐晦的执行边界

Agents may unintentionally process ignored or generated files.Agent 容易对配置、自动生成产物等非目标文件进行处理。

radio_button_unchecked

Late-stage validation滞后的验证回路

Errors cascade through the project before detection.错误往往在整个工作流执行完甚至提交后才暴露。

Kenon ProtocolKenon 协议模式
check_circle

Scoped context loading按作用域精准加载

Load exactly what matters for the scenario.精确抽取对当前任务唯一且绝对相关的最小集合。

check_circle

Explicit boundaries强制的硬性边界

Rigid exclusion rules enforced via grounds.通过内建的 grounds 原则强制阻止所有无效操作。

check_circle

Narrowed impact收紧变更影响面

Verify downstream effects before committing.在代码弄脏之前,验证它的所有潜在下游涟漪。

One anchor, four faces.

The dimensional model of agent context.

Space空间(Space)

Paths & Anchors路径与锚点

The foundational map of your repository. Defines where code lives, what it depends on, and the physical limits of an agent's workspace.代码仓库的基础地图。定义了代码位置、依赖关系以及 Agent 能够触碰的物理边界。

.kenon/space/modules.jsonl scan-baseline.json
Time时间(Time)

Sessions & Continuity. Track history beyond the chat prompt. Know what was tried and why.会话与连贯性。追踪提示词之外的全局历史,记住尝试过什么以及原因。

history
Quality质量

Verification & Findings. Grounding truth in execution.验证与发现。以真实执行结果为基础的事实对齐。

verified
Intent意图

Decisions & Exclusions. Explicit goals and forbidden paths.决策与排除。明确的目标约束与禁止触碰的红线。

track_changes
Dependencies依赖图

Dependency Analysis. Seeing the ripple effect.影响面分析。洞悉任何一次修改所引发的连锁反应。

account_tree

A short loop for real work. 主导真实工作的极简循环。

The standard lifecycle for agent interaction. 规范化 Agent 交互的标准生命周期。

fact_check
check
hub
impact
all_inclusive
download
load
verified
verify
save
save
done_all
finalize

3-Minute Fast Track 三分钟快速上手

Do it yourself, or just hand the keys to your agent.亲自操作,或者把钥匙直接交给 Agent。

Do It Yourself手动集成
bash — 80x24
$ npm install -g @kenon-ai/cli
+ @kenon-ai/cli@0.1.0
added 1 package in 1s
$ kenon run onboard
[kenon] Indexing workspace...
[kenon] Found 12 main modules, writing to .kenon/space/modules.jsonl
$ kenon load auth-service --scenario edit
Context loaded: 4 files primary, 12 secondary dependencies.
Read-only boundaries enforced for /shared/lib.
$ kenon check --diff
_
Delegate To Agent委托代理

Prompt Drop-in注入提示词

Drop this straight into your agent. It will install and configure Kenon.直接粘贴这段提示词发给 Agent 进行原生初始化。

请先在这个仓库里安装并初始化 Kenon。
1. 运行 `git clone https://github.com/kenon-ai/kenon.git` 
2. 运行 `kenon run onboard`
3. 运行 `kenon load --global --scenario edit`
4. 告诉我这个仓库最值得先看的模块和原因
5. 后续在变更前默认先经过 `check --diff`
Please install and initialize Kenon in this repository first.
1. Run `git clone https://github.com/kenon-ai/kenon.git`
2. Run `kenon run onboard`
3. Run `kenon load --global --scenario edit`
4. Tell me which module in this repository is most worth looking at first and why.
5. In future changes, always pass through `check --diff` by default.
Humans can start with the short path. Agents navigate via kenon help --json. 人类可以通过简短路径起步,Agents 通过 kenon help --json 导航。
Apache-2.0

One protocol layer. Multiple runtimes. 单层协议,多重运行环境组合。

Claude Code Cursor Codex GitHub Copilot OpenCode Pi
Atomon (Not yet open sourced) (暂未开源)

Why Kenon? 它解决了什么?

Stop letting your coding agents fly blind. Kenon prevents context drift, historical violations, and collision during parallel execution. 不再让你的 Agent 每次从零读代码。Kenon 防止上下文漂移、设计越界以及并发协作时的态势踩踏。

close Without Kenon没有 Kenon

Lacking a stable project state entry point before starting work. 开工前缺少稳定的项目状态入口。

check With Kenon有了 Kenon

load returns a folded, minimal relevant context instead of a full dump. load 返回折叠后的最小相关上下文,而不是整个 dump。

close Without Kenon没有 Kenon

Excluded paths and discarded options are hard to reuse. 已排除路径难以复用。

check With Kenon有了 Kenon

Explicit excluded makes discarded paths and conditions retractable and reconsiderable. excludedgroundsreconsider_when 让排除路径及其生效条件可重审。

close Without Kenon没有 Kenon

Changes easily cross historical design boundaries unguided. 变更极易无意越过项目的历史设计边界。

check With Kenon有了 Kenon

check --diff intercepts overstepping before commit. check --diff 在合入前拦截并预警越界行为。

close Without Kenon没有 Kenon

Verification scope balloons out of control after code changes. 代码改完后验证范围容易扩散且失控。

check With Kenon有了 Kenon

impact / verify shrinks scope & drives evidence-based acceptance. impact / verify 缩小验证范围并以证据驱动流转。

close Without Kenon没有 Kenon

Engineering semantics are scattered across sessions and prompts. 工程语义零散分布在各个会话记录和 prompt 补丁中。

check With Kenon有了 Kenon

save / finalize writes decisions & evidence back to the repo ledger. save / finalize 把决策、边界和证据写回长青仓库。

close Without Kenon没有 Kenon

Concurrent Agents clash over context, workspace, and the final say. 多个 Agent 并发时容易抢夺上下文、工作区与最终解释权。

check With Kenon有了 Kenon

Append-only truth + isolated execution = safe merge without collisions. Append-only 真源 + 隔离执行,并行追加与合流而不互相踩踏状态。

close Without Kenon没有 Kenon

Agents rebuild state from scratch every round using logs and diffs. Agent 每轮都需自己从零去读取日志和 Diff 拼凑当前态势。

check With Kenon有了 Kenon

load returns minimal, highly consumable state summaries and next steps. load 仅返回高度折叠后的态势摘要、异常分级与下一步明确导航。

close Without Kenon没有 Kenon

Heavy tasks like batch audits and debugging lack controlled execution channels. 做批量审计、深层次联调等重操作时,缺乏系统级的受控通道。

check With Kenon有了 Kenon

invoke provides a controlled multi-backend environment. invoke 提供多后端的系统级无缝跨平台受控执行层。

close Without Kenon没有 Kenon

Every Agent runtime builds its own fractured ecosystem. 每一个 Agent runtime 平台都在试图自己搞一套孤立生态。

check With Kenon有了 Kenon

One native protocol connects to 6 major coding agent runtimes universally. 底层一套协议栈,原生无缝挂接打通 6 个主流的 Agent 运行环境。

Workflow Tools vs Kenon. Workflow 工具 与 Kenon 区别。

It's a repo-local semantic ledger beneath the workflow layer. Kenon 是一层嵌入在工作流之下的本地工程语义账本。

Primary Consumer 第一消费者
Workflow Tools Human + Agent dual-read workflow assets 人类 + Agent 共读的工作流资产
Kenon Agent-first runtime state, boundary and evidence protocol Agent-first 的运行时状态、边界与证据协议
Core Objective 核心目标
Workflow Tools Organize AI coding collaboration workflows 组织 AI coding 协作流程
Kenon Keep Agents working continuously without losing semantics 让 Agent 在复杂工程中持续工作而不失真
Core Abstractions 主要抽象
Workflow Tools specs / tasks / journals / integrations
Kenon intent / deps / quality / space / time
Context Logic 上下文方式
Workflow Tools Document orchestration and injection 文档编排与注入
Kenon Dynamically tailored by module, scenario, deps, and history 按模块、场景、依赖和历史决策动态裁剪
Task Loop 任务闭环
Workflow Tools PRD, checklists, and review flows PRD、checklist、review 流程
Kenon load → check → impact → verify → save/finalize
Boundary Control 边界控制
Workflow Tools Relies more on conventions and manual flows 更多依赖规范与流程
Kenon Explicitly models boundaries, excluded paths and conditions 显式建模边界、排除路径和重审条件
Project Memory 项目记忆
Workflow Tools Human-readable workflow assets 可读的工作流资产
Kenon Retraceable structured semantic ledger 可回溯的结构化语义账本