berryscode AGENTS.md

AGENTS.md

Guidance for Codex working in this repo. Keep this file short — codebase facts belong in code, README, or commit messages, not here. Only document non-obvious gotchas and conventions an agent can't infer in 30 seconds.

What this is

BerryCode is a native IDE built specifically for the Bevy game engine. Same stack as the games it edits: Bevy 0.18 + bevy_egui 0.39 + egui 0.33 + WGPU. Two binaries ship from the same berrycode crate:

• berrycode (src/main.rs) — the production binary
• berrycode-egui (src/bin/berrycode-egui.rs) — a thinner harness used in dev / testing

Both wire up BerryCodePlugin from src/bevy_plugin.rs. Add new app-level systems to the plugin, not to either bin. Otherwise berrycode-egui silently misses behavior.

Build / run

cargo run --bin berrycode               # debug
cargo build --release --bin berrycode   # release
cargo check -p berrycode                # fast iteration when iterating UI code

The dev build is large; cargo check is the right loop for editing egui UI. The app uses a PID lockfile at ~/Library/Caches/berrycode.lock (macOS) — if the binary crashes mid-run, delete it before relaunching.

Operating rules (read first)

These exist to stop the "止まった?" feedback loop. Follow them by default; only break them if the user explicitly asks.

Never let the user lose the thread

• Always announce intent before the first tool call. When the user asks for something, the first thing in the reply is one line stating what you're about to do — not silence followed by tool calls. The user must never see "thinking…" with no follow-up text.
• Every assistant turn must end with one of three things, never silence: (a) a concrete result statement, (b) a single specific question that unblocks you, or (c) "next: " when you're handing off to a tool that fires asynchronously. Never end with "確認待ちです" alone — pair it with the specific thing you need.
• Don't send "ビルド待ち" / "monitoring" filler. If you've armed a Monitor, the next message should come from the Monitor event, not from you. Filler messages create the appearance of stalls.