Skip to content

forge: add local runtime and harden forge execution#670

Open
arsenyinfo wants to merge 4 commits intomainfrom
forge-opencode-support
Open

forge: add local runtime and harden forge execution#670
arsenyinfo wants to merge 4 commits intomainfrom
forge-opencode-support

Conversation

@arsenyinfo
Copy link
Collaborator

Summary

  • improve forge run visibility and control by adding trajectory logging for plan/work calls and strengthening review/config handling.
  • extend forge setup with richer mount support and runtime reliability improvements (install caching, decomposition/timeout-related workflow hardening).
  • add a new --runtime local backend that runs without Dagger, keeps per-run isolated workspaces for concurrency, supports two-repo generation via shared workdir, and enforces workspace-safe mount mapping with mounts.local_target overrides.
  • update edda_forge CLI help and README so runtime-specific behavior (auth, mount semantics, env usage) is documented consistently.

Test plan

  • cargo fmt --package edda_forge
  • cargo check -p edda_forge
  • cargo run -q -p edda_forge -- --help

Made with Cursor

arsenyinfo and others added 4 commits February 17, 2026 15:57
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…warn on parse errors

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Support running edda-forge without Dagger by adding a host-local sandbox and runtime selection, while preserving isolated per-run workspaces for parallel execution. Harden local mount behavior with workspace-scoped mapping and explicit local_target overrides, and align CLI/README docs with runtime-specific semantics.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant