Fork Project
fork_projectFork a project (main or any fork) into a new branch with its own database branch and test keys, when the user asks to fork, branch, or try changes away from the project.
Forks at once; no confirmation.
copyFlootDb (default "full"): "full" the parent's data. "schema": same tables, no rows. "pointInTime" + databaseAt (ISO 8601 with zone): the parent's database as it was then (code, files, keys stay current), to recover older data.
isolated true (only if asked): empty tables; no real data, keys or stored files (the /_cdn/static assets still show).
scratch true: a throwaway branch (QA run, rehearsal, backup copy): cannot be merged, deleted after 7 idle days unless kept.
ref: your own text for the branch (≤200 chars, e.g. a task link); list_branches shows it.
Output: fork project id and preview link. Merge back with compare_branches, then start_merge. Code that breaks on a fork: get_guides("fork").
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>",
"name": "<name>"
},
"name": "fork_project"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ref | No | ||
| name | Yes | ||
| scratch | No | ||
| isolated | No | ||
| projectId | Yes | ||
| databaseAt | No | ||
| copyFlootDb | No | ||
| suggestedCopyFlootDb | No |