Repository Issue Activity (beta)

#238 guardrail: .env.example / .env.template being denied as "secret or credential file" — please exempt template files

#231 skills/harness-work/SKILL.md still hardcodes Japanese output templates, violating the i18n language contract (en default)

#149 Consider listing in awesome-codex-plugins

#172 Trigger ( This request triggered cyber-related safeguards )

#219 PostToolUse cleanup deletes the approval on every commit, so in `harness-release`'s multi-commit flow (work + bump) the later commit is blocked by the commit guard

#200 Skill listing budget overflow: 28 skills sent to LLM = 9,089 chars (6,000 budget)

#173 English version

#218 `harness-review` and `harness-release` do not persist the review verdict to `review-result.json`, so an APPROVE produced outside `harness-work` cannot pass the commit guard

#208 P35 footer literal ignores i18n.language (hardcoded Japanese)

#207 [Windows] `harness mem status` / `harness mem doctor` fail: fork/exec of harness-mem .js ("%1 is not a valid Win32 application")

#201 Setup hook init doesn't create harness.toml — breaks auto-bootstrap flow

#154 Some of the output are in Japanese language in terminal

#193 cursor-do: 初回利用の摩擦4点（Composer 無 commit で空振り / plugin-root 解決 / 4.13.2 scripts 欠落 / worktree 相対パス）

#170 Scaffolder Agent is defined but never spawned by any skill or hook

#171 Bug: --no-verify and --no-gpg-sign detection bypassed by shell metacharacters

#155 [Security] Path traversal, command injection, and latent code injection in v4.12.3

#146 English version

#140 R02/R03 protected-path guardrail に project-level opt-out / per-rule bypass を追加してほしい

#131 codex-loop: runner can exit after launching a background task, leaving an orphaned active job

#147 Status Marker Localization Issue

#124 Prevent release tag opencode mirror drift

#67 Hi, Can it support multiple Plans?

#123 codex-loop background start can become state_stale while foreground run succeeds

#126 broadcast.md inbox check が新規セッションで stale な過去メッセージを永久に表示する

#128 WorktreeCreate hook stdout JSON is treated as a literal worktree path on macOS (v4.8.1)