fctl.sh valid
fctl
fctl is a software factory for Claude Code. People, scripts and other agents describe work; fctl runs Claude Code agents on it in isolated Linux sandboxes on machines the team owns, around the clock, on the Claude subscriptions of the people who start them, never on API billing. Each piece of work is a session: one Claude conversation in its own sandbox, on its own git branch, usually ending in a pull request that the agent comes back to for review comments, failed checks and conflicts. Everythi
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://fctl.sh/llms.txt
- llms-full.txt
- https://fctl.sh/llms-full.txt
- Sections
- 15
- Links
- 55
- Size
- 39499 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T12:31:43.153Z
- Last checked
- 2026-10-25T12:31:44.658Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T12:31:43.157Z. Cached copy · Source on fctl.sh
# fctl
> fctl is a software factory for Claude Code. People, scripts and other agents describe work; fctl runs Claude Code agents on it in isolated Linux sandboxes on machines the team owns, around the clock, on the Claude subscriptions of the people who start them, never on API billing. Each piece of work is a session: one Claude conversation in its own sandbox, on its own git branch, usually ending in a pull request that the agent comes back to for review comments, failed checks and conflicts. Everything is reachable from the web app, the `fctl` CLI (every command takes `--json`) and an HTTP API.
This file is for agents and the people who set them up: what fctl is, the words it uses, how to drive it safely from a terminal or another program, recipes for common flows, what to avoid, and where the details are. It is served at https://fctl.sh/llms.txt, at `/llms.txt` of every fctl instance (such as https://app.fctl.sh/llms.txt), and kept in the repository as `docs/llms.txt`. Every doc page is also served as Markdown (`https://fctl.sh/docs/<page>.md`), and https://fctl.sh/llms-full.txt is this file followed by all the docs in one file. For flags, `fctl <command> --help` has the final word.
fctl is MIT licensed and open source: https://github.com/hyperstructure/fctl. The hosted instance is https://app.fctl.sh (by invitation or early access); anyone can run their own instance on Cloudflare or in one container.
## What fctl gives you
- **Unattended agents in sandboxes.** Each session runs Claude Code with permission prompts off inside its own Linux VM or container on a runner (a Mac with Apple's `container`, Lima, or Docker). The agent clones the project's repository, works on a branch named `fctl/<number>-<title>`, commits, and fctl pushes after every turn; it opens a pull request when the task is done, unless the project turns that off.
- **Live, steerable work.** Every event is journaled and streamed: follow a session in the web app, in a terminal (`fctl attach`), or in the Claude apps (Remote Control, with a full Claude login). Message the agent at any time (with files), interrupt its turn, stop it, resume it later in the same sandbox and conversation.
- **Work that starts itself.** Schedules (cron, once at a time, or only when asked), Linear (assign or mention fctl on an issue), GitHub Actions and any tool that can make an HTTP request with an access token.
- **Agents that finish the job.** Follow-ups bring an agent back to the pull request it opened when someone who can write to the repository mentions `@fctl` or `@agent`, a check fails, the pull request conflicts with its base branch, or it merges or closes. Built-in review agents review every new commit of pull requests and hand their findings to the agent that opened the pull request.
- **Agents that learn.** A project memory of notes that each session's agent starts with and adds to, and a retrospective of each piece of work for the people who follow along.
- **Teams.** Workspaces with
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| warp.dev | Warp | documentation Developer tools AI agents and MCP | US | 66 | ✓ | ✓ | |
| overhand.dev | Overhand | documentation Developer tools AI agents and MCP | — | 45 | ✓ | ✓ | |
| castari.com | Castari | documentation AI agents and MCP Infrastructure +1 | US | 46 | ✓ | ✓ | |
| fx.sh | fx documentation | interface AI agents and MCP Developer tools | US | 51 | ✓ | ✓ | |
| claudekit.cc | ClaudeKit Documentation | documentation Marketing Developer tools +2 | SG | 48 | ✓ | ✓ | |
| ellipsis.dev | Ellipsis | interface Infrastructure AI agents and MCP +1 | US | 57 | ✓ | ✓ | |
| lody.ai | Lody | transactional AI agents and MCP Developer tools | — | 54 | ✓ | ✓ | |
| bernstein.run | Bernstein | interface AI and machine learning AI agents and MCP +2 | — | 46 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=fctl.sh · GET /v1/domain/fctl.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage fctl.sh, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for fctl.sh:
1. POST https://agentwebmap.com/v1/sites/fctl.sh/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://fctl.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/fctl.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fctl.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.