Agents, workflows and remote work#

PacketCode can delegate bounded subtasks, run multi-step workflows and place work on registered SSH computers.

Before you start#

• The primary project is a clean Git checkout or its changes are intentionally preserved.
• Tasks have nonoverlapping ownership.
• Background limits and permission policy are configured.
• Remote hosts have verified SSH keys and absolute project paths.

Background agents#

Delegate a concrete, bounded task and choose read-only or write authority. Write-enabled agents can use isolated Git worktrees. PacketCode does not merge or delete those worktrees for you; inspect their branches before cleanup.

Workflows#

Workflows describe ordered or parallel steps in TOML. Use read-only verification steps where possible, cap retries, and avoid parallel steps that own the same files. Treat a verifier's verdict as evidence, not as an automatic merge decision.

Packet Computers#

Register the SSH host, pin its host key and set an absolute remote root. Test the connection before assigning an agent. Remote commands run with the remote account's authority.

Verify#

1. Inspect every agent or workflow result.
2. Run git worktree list and review each produced branch.
3. Run project tests in the worktree that contains the change.
4. Integrate approved commits through the normal Git process.
5. Remove worktrees only after useful commits are reachable from a preserved branch or remote.

If it does not work#