fullsend agent
Manage agent registrations in fullsend config. Add, list, update, and remove agents, or migrate legacy customized/ overrides to config-driven agents.
Commands
| Command | Description |
|---|---|
fullsend agent add <url-or-path> | Register an agent in config |
fullsend agent list | List registered agents |
fullsend agent update <name> [sha] | Re-pin a URL agent to a new commit SHA |
fullsend agent remove <name> | Remove an agent from config |
fullsend agent migrate-customizations | Migrate customized/ overrides to config-driven agents |
agent add
Register an agent in config by URL or local path. URL sources are automatically pinned to a specific commit SHA and annotated with an integrity hash. The URL prefix is added to allowed_remote_resources if not already present.
fullsend agent add https://github.com/my-org/agents/blob/main/harness/lint.yaml --fullsend-dir .fullsend
fullsend agent add harness/custom-review.yaml --name my-review --fullsend-dir .fullsendFlags
| Flag | Default | Description |
|---|---|---|
--fullsend-dir | Base directory containing the .fullsend layout (required) | |
--name | derived from filename | Explicit agent name |
Behavior
- GitHub URLs are resolved to a pinned
raw.githubusercontent.comURL with a#sha256=...integrity hash. - Non-GitHub URLs must already contain a commit SHA in the path.
- Local paths must be relative and must not contain path traversal (
..). - If an agent with the same name already exists, the command fails.
agent list
List all agents registered in config, showing each agent's name and source.
fullsend agent list --fullsend-dir .fullsendFlags
| Flag | Default | Description |
|---|---|---|
--fullsend-dir | Base directory containing the .fullsend layout (required) |
Read-only. Displays a table with NAME and SOURCE columns.
agent update
Re-pin a URL-based agent to a new commit SHA and recompute the integrity hash. If no SHA is provided, the default branch HEAD is resolved automatically.
fullsend agent update triage --fullsend-dir .fullsend
fullsend agent update triage abc123def456... --fullsend-dir .fullsendFlags
| Flag | Default | Description |
|---|---|---|
--fullsend-dir | Base directory containing the .fullsend layout (required) |
Behavior
- Only URL agents can be updated — local path agents have nothing to pin.
- Non-GitHub URL agents require an explicit SHA argument.
- The integrity hash is recomputed by fetching the content at the new SHA.
agent remove
Remove an agent from config. If the removed agent was the last one using a given allowed_remote_resources prefix, that prefix is also cleaned up.
fullsend agent remove triage --fullsend-dir .fullsendFlags
| Flag | Default | Description |
|---|---|---|
--fullsend-dir | Base directory containing the .fullsend layout (required) |
agent migrate-customizations
Scan the customized/ directory and migrate each override to a config-driven agent. Changes are committed to a branch and delivered via pull request. Use --dry-run to preview changes without creating a PR.
fullsend agent migrate-customizations --fullsend-dir .fullsend --dry-run
fullsend agent migrate-customizations --fullsend-dir .fullsend --repo owner/repoFlags
| Flag | Default | Description |
|---|---|---|
--fullsend-dir | Base directory containing the .fullsend layout (required) | |
--repo | Target repository (owner/repo) for the migration PR (required unless --dry-run) | |
--dry-run | false | Show what would change without creating a PR |
Override classification
The tool classifies each override and takes the appropriate action:
| Override type | Detection | Action |
|---|---|---|
| Dead | Agent already registered in config | Delete customized/ files |
| Custom | Not in upstream scaffold | Move files to regular directories, register local path in config |
| Modified | Standard scaffold agent, not yet in config | Generate a base: composition harness with the minimal diff, register in config |
For modified agents, the migration produces a thin base: harness containing only the fields that differ from upstream.
See also
- Bring Your Own Agent — building custom agents and configuring existing ones
- Default, derived, and custom agents — terminology and classification
- Configuring with skills — extending agents with skills
