[P0] Executor over-engineers small tasks — creates venvs / pip-installs deps #33
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_shrimp#33
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
For a self-contained task ("build a small unittest library") the executor ran
python3 -m venv .venv+pip install pytest+ wrotepyproject.toml, dumping ~300 dependency files into the workspace and burning ~2 min. It should write a stdlib self-test and never create virtualenvs or install packages for self-contained work unless explicitly asked.Evidence
c_1779571735407_…created.venv/**(all of pytest/pip/setuptools).crates/hero_shrimp_engine/src/orchestration/autonomy/prompt_builder.rs(AutonomyMode::Execute).Proposed fix
Add an Execute-mode rule: don't create virtualenvs or install packages for a self-contained library/script; verify with the stdlib or what's already present. (UI now hides vendored paths, but that only masks the symptom.)
Filed from a comparative audit of Hero Shrimp vs Qwen-Code / kimi-cli / picoclaw (2026-05-23). Severity in title: P0=correctness/trust, P1=reliability/UX, P2=cleanup.