fix: tools plugin uses workspace path instead of cwd (#174) #175
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Competitor
Kind/Documentation
Kind/Enhancement
Kind/Epic
Kind/Feature
Kind/Security
Kind/Story
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Scope/Core
Scope/Cross-Plugin
Scope/Plugin-System
Scope/Single-Plugin
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ultanio/cobot!175
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/174-exec-cwd"
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?
Fixes #174
Problem
ToolsPlugin._base_dirdefaulted toPath.cwd(), so the exec tool ran commands in whatever directory the process started in — not the agent's workspace.Fix
configure()accepts_workspace_pathfrom config (for testing)start()resolves workspace path from registry viaworkspace.get_path()(same pattern as soul plugin)_exec()passescwd=self._base_dirtosubprocess.run()Tests
test_configure_workspace_path— verifies config sets base_dirtest_exec_runs_in_workspace_dir— verifies exec runs in workspace dirLGTM. Clean fix — tools plugin gets workspace path from registry and passes it as cwd to subprocess. Tests cover both config injection and actual pwd verification.
5f0f479f9289c55cc449