원클릭으로
workspace-path-constraints
Work around editor/search tools that only accept indexed-workspace paths.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Work around editor/search tools that only accept indexed-workspace paths.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
A TRefCountPtr/TSharedPtr member in a UE class needs the pointee's full definition, not a forward decl.
When WSL's mirrored networking fails and falls back to "None", plus /etc/wsl.conf has generateResolvConf=false, the distro has no DNS; fix both layers.
When a Windows shell (PowerShell/cmd) feeds a bash script into WSL, CRLF line endings can corrupt the first shell builtin; force LF or pipe via a temp file.
Before "fixing" a recurring error, check git log to see if it was already fixed upstream — the working tree may just be stale.
Always add a space after URL brackets in Markdown to prevent 404 errors with special characters.
Plan a Python 3 modernization sweep (f-strings, super(), type hints) as a series of mechanical PRs, not one mega-PR.
| name | workspace-path-constraints |
| description | Work around editor/search tools that only accept indexed-workspace paths. |
| tags | ["agent","tooling","workspace"] |
You need to create or edit files in a sibling directory the user just
cloned (e.g. ../agent-skills) but the agent's edit_file,
list_dir, codebase_search, or view_code_item refuses it with
路径不在workspace下,拒绝请求 / "path is not in workspace".
Several tools are scoped to the indexed workspaces only (the ones listed in the session's workspace configuration). They won't touch files outside, even if the process has filesystem permission.
Trying to keep inventing ad-hoc cat > file <<EOF heredocs in the
shell is how you get the problems documented in
shell-heredoc-and-multiline-strings.
Pick one based on what the target needs:
One or two short text files → use the agent's terminal tool
with printf / tee, quoting carefully.
Multiple files, or files with backticks / quotes / multi-line
code → write a generator script inside an indexed workspace
(e.g. blade-build/tmp_build_skills.py) that builds a
{path: content} dict and writes every file with standard
Path.write_text. The generator is plain Python source, so
edit_file is happy to create it. Run it once with python3,
then delete.
Read-only exploration (listing, grepping) of the non-indexed
directory → use terminal with ls, find, cat, rg.
Large existing file you need to modify → cat it through the
terminal to inspect, then apply a small sed -i or re-emit via
the generator-script trick.
Generator-script pattern:
# blade-build/tmp_build_skills.py
from pathlib import Path
ROOT = Path("/Volumes/SanDiskSSD/code/agent-skills")
FILES = {
"README.md": "…",
"skills/foo/SKILL.md": "…",
}
for rel, body in FILES.items():
p = ROOT / rel
p.parent.mkdir(parents=True, exist_ok=True)
p.write_text(body)
print(f"wrote {len(FILES)} files")
Then:
python3 /Volumes/SanDiskSSD/code/blade-build/tmp_build_skills.py
rm /Volumes/SanDiskSSD/code/blade-build/tmp_build_skills.py
codebase_search / view_code_item will not see the non-indexed
repo even after files are written; fall back to grep + cat.