Agents: run an agent inside a container sandbox

Aberta
#54 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
docker, rust
Domínio
devops, security

Direção de pesquisa

No files are named, so start from where an agent preset is defined and where the agent CLI is spawned for a terminal tab, since container mode changes that launch step. Read the existing runtime rules referenced under 'Proposed behavior' before touching any Docker/Podman calls, then trace how agent state hooks reach Atlas. Done means the three acceptance criteria hold in tests: an in-container agent cannot read outside the worktree, hooks still fire, and a missing container runtime produces a clear error, with the image and requirements documented.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area: desktop status: needs-triage type: feature

Problem

Running agents with auto-approve on the host is risky (they can touch anything in HOME). Users want auto-approve speed with a blast radius limited to the worktree.

Evidence

From research on parallel-agent desktops and worktree tools, this is a recurring user request:

A recurring request across agent-workspace and parallel-agent tools, with high upvote counts in their public trackers. Public examples: https://github.com/stravu/crystal/issues/178 (run without --dangerously-skip-permissions); https://github.com/winfunc/opcode advertises sandboxed background agents.

Proposed behavior

  • Per-agent-preset option Sandbox: none | container. Container mode runs the agent CLI in Docker/Podman/OrbStack with only the worktree mounted rw, agent config mounted ro, and network policy (on/off/allowlist).
  • The terminal/agent tab works the same (PTY via docker exec -it); hooks still reach Atlas.
  • Never restarts or tears down the docker daemon (keeps the existing runtime rules).

Acceptance criteria

  • An agent in container mode cannot read files outside the worktree (test).
  • Agent state hooks work from inside the container.
  • Documented with the image/requirements; clear error when no container runtime is present.
Linguagem predominante
Rust
Estrelas
3
Forks
1
Merge médio
8h 45min
PRs com merge (30d)
351

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de codeatlasdev/atlas

Todas as issues de codeatlasdev/atlas

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.