9d739dfa5d
- All gsdDir/gsdRoot/gsdHome → sfDir/sfRootDir/sfHome - GSDWorkspace* → SFWorkspace* interfaces - bootstrapGsdProject → bootstrapProject - runGSDDoctor → runSFDoctor - GsdClient → SfClient, gsd-client.ts → sf-client.ts - .gsd/ → .sf/ in all tests, docs, docker, native, vscode - Auto-migration: headless detects .gsd/ → renames to .sf/ - Deleted gsd-phase-state.ts backward-compat re-export - Renamed bin/gsd-from-source → bin/sf-from-source - Updated mintlify docs, github workflows, docker configs
101 lines
3.2 KiB
Text
101 lines
3.2 KiB
Text
---
|
|
title: "SF — Singularity Forge"
|
|
description: "An autonomous coding agent that researches, plans, executes, and commits code while you focus on what matters."
|
|
---
|
|
|
|
SF is an autonomous coding agent. Describe what you want built, run `/sf auto`, and walk away. Come back to working software with clean git history.
|
|
|
|
## What SF does
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Autonomous execution" icon="robot">
|
|
A state machine reads your project state, dispatches work to an LLM in fresh context windows, and advances through research, planning, execution, and verification — all without manual intervention.
|
|
</Card>
|
|
<Card title="Clean git history" icon="code-branch">
|
|
Every task produces a conventional commit. Milestones are squash-merged to main. Your `git log` reads like a changelog.
|
|
</Card>
|
|
<Card title="Cost control" icon="gauge">
|
|
Budget ceilings, token profiles, and dynamic model routing keep costs in check. Use Haiku for simple tasks and Opus for architectural work — automatically.
|
|
</Card>
|
|
<Card title="Crash recovery" icon="rotate">
|
|
Sessions recover from crashes, provider errors auto-retry, and headless mode auto-restarts with exponential backoff. Designed for overnight unattended execution.
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## How it works
|
|
|
|
SF organizes work into a hierarchy:
|
|
|
|
```
|
|
Milestone → a shippable version (4-10 slices)
|
|
Slice → one demoable vertical capability (1-7 tasks)
|
|
Task → one context-window-sized unit of work
|
|
```
|
|
|
|
The iron rule: **a task must fit in one context window.** If it can't, it's two tasks.
|
|
|
|
Auto mode loops through this hierarchy:
|
|
|
|
```
|
|
Plan → Execute (per task) → Complete → Reassess Roadmap → Next Slice
|
|
↓ (all slices done)
|
|
Validate → Complete Milestone
|
|
```
|
|
|
|
Every phase gets a fresh context window with pre-loaded context — no accumulated garbage, no degraded quality.
|
|
|
|
## Two ways to work
|
|
|
|
<Tabs>
|
|
<Tab title="Step mode">
|
|
Type `/sf` inside a session. SF executes one unit at a time, pausing between each so you can review.
|
|
|
|
```bash
|
|
sf
|
|
/sf
|
|
```
|
|
</Tab>
|
|
<Tab title="Auto mode">
|
|
Type `/sf auto` and walk away. SF autonomously researches, plans, executes, verifies, and commits until the milestone is complete.
|
|
|
|
```bash
|
|
sf
|
|
/sf auto
|
|
```
|
|
</Tab>
|
|
</Tabs>
|
|
|
|
The recommended workflow: auto mode in one terminal, steering from another.
|
|
|
|
**Terminal 1 — let it build:**
|
|
|
|
```bash
|
|
sf
|
|
/sf auto
|
|
```
|
|
|
|
**Terminal 2 — steer while it works:**
|
|
|
|
```bash
|
|
sf
|
|
/sf discuss # talk through architecture decisions
|
|
/sf status # check progress
|
|
/sf capture # fire-and-forget thoughts
|
|
```
|
|
|
|
## Next steps
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Install SF" icon="download" href="/getting-started">
|
|
Get up and running in under a minute.
|
|
</Card>
|
|
<Card title="Auto mode deep dive" icon="circle-play" href="/guides/auto-mode">
|
|
How the autonomous execution engine works.
|
|
</Card>
|
|
<Card title="Commands reference" icon="terminal" href="/guides/commands">
|
|
Every command, shortcut, and CLI flag.
|
|
</Card>
|
|
<Card title="Configuration" icon="gear" href="/guides/configuration">
|
|
Models, budgets, timeouts, and preferences.
|
|
</Card>
|
|
</CardGroup>
|