Judge the file body when a command runs an interpreter on a session-written script
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by tracing the command-classification entry point for interpreter invocations and the existing heredoc-body handling; no implementation file or test is named. Review the evidence in ~/.omp/agent/dreams/2026-09-16.md and the stopgap in ~/.omp/agent/AGENTS.md. Done means bounded body reads fail closed, import behavior and L1 coverage are decided, and tests show path or filename changes no longer alter the verdict.
Written by the indexing model from the issue text.
Description
A headless worker can run any code it wrote, as long as the file sits in the worktree and not in /tmp. The gate judges the command text (python3 .scratch/x.py), not what x.py does, so where a script lives decides whether it runs, and renaming it can flip the verdict.
Evidence from the 2026-09-16 autodream run (~/.omp/agent/dreams/2026-09-16.md, open question 2):
- ~28 sessions had a session-written
/tmpscript refused as unverifiable provenance. - The byte-identical script inside the assigned worktree ran. Workers found that independently ~8 times.
P4Carriersgot a refused file through by renamingcleanup_row.pytors3_remove_import.py.
Trusting session-written files would be a straight bypass: the model writes whatever it wants, then runs it. The fix goes the other way. When a command invokes an interpreter (python, node, bun, bash, sh, ruby, php, ...) on a readable file, read the file and judge its body as part of the command, the same way heredoc bodies are handled now. Then path and filename stop mattering, in both directions.
Things to settle:
- Size cap on the body read, and what happens past it (fail closed).
- Files that import siblings: judge only the entry file, or refuse when the entry pulls in session-written modules.
- Whether L1 critical patterns run over the body too, or only Jev.
Stopgap in place since 2026-09-19: ~/.omp/agent/AGENTS.md tells workers to write probes under <worktree>/.scratch/ and never rename a refused script.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 20m
- Merged PRs (30d)
- 32
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from STRML/omp-classifier
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
STRML/omp-classifier#81 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
STRML/omp-classifier#80 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
STRML/omp-classifier#78 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
STRML/omp-classifier#84 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
STRML/omp-classifier#82 ·
All issues in STRML/omp-classifier
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·