Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Implement working directory scope locking for ADF agents

Abierto
#690 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
rust
Área
ai, security

Línea de trabajo

Start with item 2.2 in cto-executive-system/plans/adf-architecture-improvements.md and the ManagedAgent model, then trace the PostToolUse hook, structured envelope, and NightwatchMonitor integration, noting dependencies #688 and #689. Done means working-directory binding, traversal and symlink escape rejection, scope-violation events, and the listed scope-negative tests all work before deployment.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Context

ADF agents currently have unrestricted filesystem access on bigbox. There is no mechanism to prevent an agent from reading or writing files outside its assigned working directory. Piwork (ferologics/Piwork) implements a robust scope locking model: one-time bind of working folder per task, traversal/symlink escape blocking, and a dedicated scope-negative test suite.

Proposal

Scope Locking
  • One-time bind: once an agent is assigned a working_dir, it is locked for the session
  • Record scope_locked: bool in ManagedAgent
  • Reject any attempt to change working directory after binding
Escape Prevention
  • Block .. path traversal in file operation arguments
  • Block symlink escapes (symlinks pointing outside scope)
  • Log violations to NightwatchMonitor as security events
Scope-Negative Test Suite
  • Attempt traversal: ../../../etc/passwd -- must fail
  • Attempt symlink escape: create symlink pointing outside scope -- must fail
  • Attempt working_dir change after lock -- must fail
  • All tests must pass as prerequisites for agent deployment
Integration
  • With Agent SDK (#689): PostToolUse hook inspects file paths
  • With subprocess model: parse file paths from structured envelope (#688)
  • NightwatchMonitor: new signal type for scope violations (alongside drift and error rate)

References

  • Piwork permissions model: https://github.com/ferologics/Piwork/blob/main/docs/permissions-model.md
  • Piwork scope-negative tests: mise run test-scope-negative
  • KB article: cto-executive-system/knowledge/external/context-engineering/piwork-desktop-ui-for-pi-agent.md
  • Plan: cto-executive-system/plans/adf-architecture-improvements.md (item 2.2)
  • Depends on: #688 (RPC envelope) or #689 (Agent SDK)
Lenguaje dominante
Rust
Estrellas
62
Forks
5
Merge medio
2 h 27 min
PR fusionados (30 d)
1

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de terraphim/terraphim-ai

Todos los issues de terraphim/terraphim-ai

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.