Docs

Build, remix, and ship agents in minutes.

AgentForge mirrors the GitHub workflow: star what inspires you, fork a manifest, comment on ideas, and submit JSON diffs. This guide walks you through the end-to-end loop.

Sandbox window

30s

Default model

Claude Sonnet 4.5

Official templates

1. Create

Click New Agent, describe the mission, and paste a .agent.json manifest.
Assign tags such as research, translator, coding, support.
Use the Change Summary field to keep version history readable.

2. Test

Run the agent inside the sandbox (Claude Sonnet 4.5 by default).
Inspect latency + tokens in the Recent Runs panel.
Iterate until the manifest behaves deterministically.

3. Publish

Hit Publish Update to log a new version snapshot.
Share the detail page—stars, forks, and comments are now enabled.
Run history, PR diffs, and version timeline update automatically.

4. Collaborate

Fork any agent via the Fork button; we snapshot the parent version.
Submit JSON diffs in the Pull Request panel and discuss via comments.
Stars push agents onto the Trending board.

Manifest anatomy

Manifests live inside agent_json. They describe the model, prompt, tools, and examples.

{
  "name": "Polyglot Translator",
  "model": "claude-sonnet-4-5",
  "prompt": "You are a precise translator. Provide only the translation.",
  "tools": [
    { "type": "memory", "config": { "max_items": 3 } }
  ],
  "examples": [
    { "input": "Hello", "output": "Hola" }
  ]
}

FAQ

Is everything public?

Yes. Private repos arrive in a later release. Avoid pasting secrets into manifests.

Do I need an API key?

Only the site runner needs an Anthropic key (managed server-side). You can still author manifests without one.

How do forks work?

Click Fork to clone a manifest into your namespace. We append a slug suffix and create a version snapshot referencing the parent.

How do I delete an agent?

Submit a PR removing the manifest or email support@agentforge.one with the slug.