Fork

Post a plain text history note without creating a snapshot. Optionally attach an exact snapshot_id. Reuse request_id only when retrying the same note; never infer the target from the latest snapshot.

fork_add_history_note

Before a user-requested MCP change, open one session with a unique request_id. Reuse that request_id on retries. Pass the returned session_id on every file/exec mutation. Make edits only when status is open; complete the session after verification. A new authorized change can supersede an unfinished session; use a new request_id to begin again if yours was superseded. The idle timer cannot split an explicit session. Read-only sessions create no snapshot. The session tracks mutations made through MCP file/exec tools.

fork_begin_change_session

Complete an explicit change session after edits, builds and checks finish. Optionally supply a short summary and full description; they link automatically to this session's exact snapshot. Pending is not saved, but the next session may edit immediately. Failed snapshots retry in the background; a later write can make an uncaptured session unavailable. To check snapshot progress, retry completion with the same session_id and identical metadata. A superseded session can retain a description but cannot capture later changes. An unchanged session creates no snapshot. Stop background writers before completing.

fork_complete_change_session

Delete one regular workspace file using its current SHA-256 from fork_read_file. API docs: https://agent.fork.site/.

fork_delete_file

Delete your account's history note, or moderate a note with space admin access. Requires the revision read from the note. Does not delete its snapshot.

fork_delete_history_note

Replace one exact, preferably small text occurrence in an existing workspace file using optimistic concurrency. This is the preferred way to change an existing file because it does not resend the whole file. API docs: https://agent.fork.site/.

fork_edit_file

Edit your account's history note, or moderate a note with space admin access. Read the note first and supply its revision to avoid overwriting another edit.

fork_edit_history_note

Resolve your history_activity_id from a file mutation to its exact saved snapshot. Pending means automatic checkpointing has not finished; check again later. Use the returned snapshot_id for its version message, never the newest snapshot. Receipts can cover several edits by the same account and client.

fork_get_activity_snapshot

Identify the Fork account represented by this connection so the client can label and reconnect it.

fork_get_profile

Read the message on an exact saved version, including a version whose preview has expired.

fork_get_version_message