stoneforge
A web dashboard and runtime for orchestrating AI coding agents
Source#
- Repository: stoneforge-ai/stoneforge
- Last source update: 2026-04-19
- Last verified: 2026-04-19
Tags#
Integration notes#
Framework-level abstraction; derive bounded worker contracts from concrete tasks and APIs in docs/examples.
worker.md example#
Starter worker.md contract mapped from this registry entry. Copy this file and adapt schemas, constraints, and statuses for your task.
---
id: stoneforge-repo-derived-worker
name: stoneforge Repo-Derived Worker
version: 1.0.0
source_registry_url: https://worker.md/registry/stoneforge/
source_repository: https://github.com/stoneforge-ai/stoneforge
repository_default_branch: master
repository_language: TypeScript
repository_license: Apache-2.0
repository_updated_at: 2026-04-19
worker_mode: agent-orchestration-worker
derivation_method: github_repository_metadata_plus_raw_readme
derivation_confidence: 0.95
derived_on: 2026-04-19
tags:
- agent-framework
- agents
- ai
- ai-agents
- event-sourcing
- llm
---
# stoneforge Repo-Derived Worker
## Repo-derived summary
- Registry summary: A web dashboard and runtime for orchestrating AI coding agents
- Repository description: A web dashboard and runtime for orchestrating AI coding agents
- Stars (snapshot): 125
- Primary language: TypeScript
- Worker mode classification: agent-orchestration-worker
## Extracted from
- https://github.com/stoneforge-ai/stoneforge
- https://github.com/stoneforge-ai/stoneforge/blob/master/README.md
- https://docs.anthropic.com/en/docs/claude-code/agent-teams
- https://cla-assistant.io/stoneforge-ai/stoneforge
## Evidence notes (from repository text)
- README summary paragraph: A web dashboard and runtime for orchestrating AI coding agents
- A web dashboard and runtime for orchestrating AI coding agents
- If a single coding agent handles your workload today, you probably don't need this yet. It'll be here once you start running multiple agents in parallel.
- Running one AI coding agent is simple. Running several in parallel — a planner, coders, a reviewer — breaks down fast:
- - **Merge conflicts** — agents edit the same files on the same branch
- - **Wasted work** — two agents grab the same task, or one starts on work that's blocked
## Installation hints found in README
- `npm install -g @stoneforge/smithy`
- `npm install && sf init`
- `npm install @stoneforge/core @stoneforge/storage @stoneforge/quarry`
- `npm install @stoneforge/smithy # Agent orchestration`
## worker.md contract (derived starter)
Purpose: Execute one orchestrated agent task as a bounded worker step.
### Input schema
```json
{
"type": "object",
"additionalProperties": false,
"required": [
"run_id",
"task",
"context"
],
"properties": {
"run_id": {
"type": "string"
},
"task": {
"type": "string"
},
"context": {
"type": "object"
}
}
}
```
### Output schema
```json
{
"type": "object",
"additionalProperties": false,
"required": [
"run_id",
"status",
"result"
],
"properties": {
"run_id": {
"type": "string"
},
"status": {
"type": "string",
"enum": [
"ok",
"retryable_error",
"invalid_request",
"invalid_output"
]
},
"result": {
"type": "object"
}
}
}
```
### Constraints
- timeout_seconds: 30
- max_attempts: 2
- idempotency_key: run_id
- status_enum: [ok, retryable_error, invalid_request, invalid_output]
- notes: adapt to concrete APIs/classes documented in this repository before production use
## How this should be used
1. Treat this file as a repo-derived starter profile, not a claim of an official repository API contract.
2. Replace schemas with exact interfaces from code/docs you adopt.
3. Keep execution bounded and auditable using worker protocol constraints.
How to use#
- Save this as a worker spec file (for example:
stoneforge-my-task.worker.md). - Replace the input/output schemas and purpose with your real bounded task.
- Enforce schema validation + timeout + retry policy in your runtime before production use.
Citation#
Reference URL: https://worker.md/registry/stoneforge/
Source URL: https://github.com/stoneforge-ai/stoneforge