Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Bug]: Project-boundary gate hard-codes /root/.local/ and /root/.claude/, so a non-root account cannot read its own tools, and there is no setting to allow a path

オープン
  • 何か問題がありますか？
#104 コメント 4 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
1〜2日
初心者へのやさしさ
54/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
bash, linux, shell
領域
cli, security

調査の方向性

Read agents/context/check-project-boundary.sh, especially READ_ALLOWED_PREFIXES around line 753, and trace how ~ paths are expanded and checked. Reproduce the non-root case from the issue using ls ~/.local/bin/fw or grep -n x ~/some-tool; done means the account’s own configured read paths are handled as expected without weakening the boundary gate. The issue describes broader configuration and executable-tool requests that may need scope decisions.

索引モデルが issue の本文から書いたものです。

説明

area:governance bug severity:medium status:in-progress triaged
Bug Description

agents/context/check-project-boundary.sh, READ_ALLOWED_PREFIXES (around line 753) contains '/root/.local/' # user shim install dir and '/root/.claude/' # Claude Code state. On a non-root account, $HOME/.local/ and $HOME/.claude/ are refused, although the comments describe exactly those directories.

Since 1.8.11 the gate expands ~ as bash does (T-3768), so every ~/... argument outside the project is now refused. Under the 1.8.6 hooks, ls -la ~/.local/bin/fw and cmp ~/.local/bin/fw <file> passed in the same session.

Cases met on this host after the upgrade, all read-only or the operator's own cross-project tool:

  • ~/passer --help (the operator's script for leaving a message to another project);
  • grep -n FW_ROUTED_FROM ~/.local/bin/fw;
  • reading a shared conventions file and another project's message file under $HOME.

The gate gives no way to allow a path: READ_ALLOWED_PREFIXES and READ_ALLOWED_EXACT are literals, and no environment variable or fw config key is read. Meanwhile Claude Code's own Read tool still reads the same files, so the gate does not protect them; it only blocks shell use.

Steps to Reproduce
  1. Non-root account, project under $HOME/<project>.
  2. Ask the agent to run ls ~/.local/bin/fw or grep -n x ~/some-tool.
  3. PROJECT BOUNDARY BLOCK — Command Targets Another Project, Reason: Outside-path argument /home/<account>/.local/bin/fw (not in read-side allowlist).
Expected Behavior
  1. $HOME/.local/ and $HOME/.claude/ (expanded) instead of /root/....
  2. A project or host setting for extra read-only paths (for example fw config set BOUNDARY_READ_ALLOW "<path>:<path>"), and ideally one for named operator tools that may be executed.
Actual Behavior

The account's own tools and shared read-only files are unreadable from Bash on any non-root install, with no supported way to allow them.

fw doctor output
AI Agent

Claude Code

Operating System

Linux

Additional Context

1.8.11 (e42aa41bf), vendored consumer, Linux (Ubuntu 20.04), non-root account, Claude Code. Also found independently by another consumer project on the same host; its reproduction was re-run here on 1.8.11.

主要言語
Shell
スター
16
フォーク
6
平均マージ
6時間 24分
マージ済み PR（30日）
5

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

DimitriGeelen/agentic-engineering-framework のほかの issue

DimitriGeelen/agentic-engineering-framework の issue をすべて見る

似ている issue

Shell/Bash の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。