Add sandboxed code execution capability (currently none exists)

Aperta
#25 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@devarshishimpi ci sta già lavorando.

Dal 4/7/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement good first issue help wanted
Is your feature request related to a problem?

Codra has no way to actually execute code, it only reads diffs and sends them to an LLM. There's no sandboxing, isolation, or subprocess execution anywhere in the codebase today. This blocks any future feature that needs to run something (lint/test verification, validating AI-suggested fixes, etc.).

Describe the solution you'd like

Add a pluggable execution provider that can run untrusted commands in a real sandbox, designed to stay free by default:

  • Default: delegate to GitHub Actions on the target repo (already installed via the GitHub App), real isolated execution on GitHub's free runner minutes, zero added cost to Codra's own infra.
  • Optional: in-Worker WASM sandbox for trivial, dependency-free scripts, staying entirely inside the free Cloudflare Workers runtime.
  • Leave room for operators to plug in a paid sandbox (Cloudflare Containers, E2B, etc.) if they want one, but never require it by default.
Architectural constraints
  • Codra runs entirely on Cloudflare Workers (V8 isolates), which have no subprocess/filesystem/shell APIs, execution can't happen in-process and must be delegated somewhere.
  • The natural "real" sandbox option, Cloudflare Containers/Sandbox SDK, requires a paid Workers plan, which conflicts with keeping a self-hosted Codra instance free.
  • Any execution surface must treat the command/input as untrusted, the sandbox boundary itself needs to be the actual security guarantee, not operator trust.
Lingua principale
TypeScript
Stelle
125
Fork
23
Merge medio
2g 13h
PR unite (30g)
12

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di devarshishimpi/codra

Tutte le issue di devarshishimpi/codra

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.