WhyBuddy: Instructions file for Kiro

.kiro/steering/2026-04-15-runtime-current-state.md

WhyBuddy 2026-04-15-runtime-current-state.md is an instructions file for Kiro from xiaojilele-glitch/WhyBuddy. It costs 689 tokens per session, scanned A, original, MIT.

A runtime status note describing how the project behaves with Docker available, Docker unavailable, or on GitHub Pages. It documents real, native, and mock execution modes, as well as the browser-only limits of GitHub Pages.

In plain words
What is it for?
Use it when starting the project locally, selecting an executor mode, or describing deployment behavior. It also identifies the main source files that implement these runtime choices.
Why use it?
It prevents developers from assuming every environment has a server, Docker, or an executor. The distinctions explain why local startup can fall back to a host process while GitHub Pages only runs the frontend.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is xiaojilele-glitch/WhyBuddy's own configuration. It tells Kiro how to work on WhyBuddy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything WhyBuddy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xiaojilele-glitch/WhyBuddy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/xiaojilele-glitch/WhyBuddy/main/.kiro/steering/2026-04-15-runtime-current-state.md
Clone the repo
git clone --depth 1 https://github.com/xiaojilele-glitch/WhyBuddy

Made for: Kiro.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for WhyBuddy 2026-04-15-runtime-current-state.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/2026-04-15-runtime-current-state/github.svg)](https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/2026-04-15-runtime-current-state)
Your own site
<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/2026-04-15-runtime-current-state"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/2026-04-15-runtime-current-state/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for WhyBuddy 2026-04-15-runtime-current-state.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/2026-04-15-runtime-current-state"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/2026-04-15-runtime-current-state.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 689 This file is loaded in full into every session.
When invoked 689 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00689 $0.00689
Opus 5.5 $0.00276 $0.00276
Sonnet 5.5 $0.00138 $0.00138
Haiku 4.5 $0.00069 $0.00069

Measured 1mo ago against content hash 71f2eba7c4ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

WhyBuddy 2026-04-15-runtime-current-state.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.kiro/steering/2026-04-15-runtime-current-state.md · 77 lines

What it actually says

2026-04-15 当前运行时补充

这份文档用于补充 2026-04-15 之后的当前真实运行时状态,不替代旧的 README、ROADMAP 与 steering 历史文档。

核心结论

当前仓库必须按 3 类环境理解:

环境 前端 服务端 Executor 实际行为
Local + Docker reachable 有 有 real DockerRunner 真容器执行
Local + Docker unavailable 有 有 native NativeRunner 宿主进程执行
GitHub Pages 有 无 无 Browser Runtime + IndexedDB + preview/demo

关键边界

1. 本地无 Docker 不再直接启动失败

  • scripts/dev-all.mjs 会先探测 Docker
  • 如果显式指定 LOBSTER_EXECUTION_MODE=mock 或 native,会保留用户选择
  • 如果默认请求 real 但 Docker 不可用,会回退到 native

2. Executor 当前是三模式

  • real
    • DockerRunner
  • native
    • NativeRunner
  • mock
    • MockRunner

3. GitHub Pages 不属于 executor 模式

  • GitHub Pages 没有本地服务端
  • GitHub Pages 没有本地 executor
  • GitHub Pages 不是 native
  • Pages 下只应被描述为 Frontend Runtime / Browser Runtime

与当前代码对应的落点

  • scripts/dev-all.mjs
    • 本地启动时的 Docker 探测与 native 回退
  • services/lobster-executor/src/index.ts
    • real 请求在 Docker 不可用时切换为 native
  • services/lobster-executor/src/runner.ts
    • DockerRunner / NativeRunner / MockRunner 分发
  • client/src/lib/deploy-target.ts
    • GitHub Pages 下禁用 Advanced Runtime
  • client/src/lib/store.ts
    • Pages / frontend-only 时强制 frontend runtime
  • client/src/lib/api-client.ts
    • API 不可用时退化到 preview/demo 行为
  • client/src/runtime/browser-runtime.ts
    • Browser Runtime 执行链路

当前产品表面

  • /
    • 办公室主壳,承接 OfficeTaskCockpit、Scene3D、统一发起区与共享任务操作
  • /tasks
    • 全屏任务工作台与深链详情页
  • Executor
    • 与 Mission / Workflow 桥接,负责真实执行、日志、工件与事件回传

相关归档

  • .kiro/specs/sandbox-native-executor-compat/
    • 归档了本地 native 兼容层、启动回退策略与 Pages 边界

配套图示

  • docs/architecture-runtime-2026-04-15.svg
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 77 lines · 689 tokens per session scan A 71f2eba7c4ca

Subscribe to this mod's changes

WhyBuddy 2026-04-15-runtime-current-state.md is an instructions file published in the GitHub repository xiaojilele-glitch/WhyBuddy (380 stars, last pushed 1mo ago), licensed MIT. It adds 689 tokens to every session, about $0.0028 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-23.

Related

WhyBuddy 2026-04-15-runtime-current-state.md compared with instructions from other repositories

WhyBuddy 2026-04-15-runtime-current-state.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
WhyBuddy 2026-04-15-runtime-current-state.mdxiaojilele-glitch/WhyBuddyInstructions file3801mo agoMITA689Kiro
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode