Your first Golf workflow

Explore the browser simulations

Open the local / Docker simulation or the Cloudflare simulation in a new tab. Both use Golf’s actual interface with sample source, issues, pull requests and reports. No account or backend is required.

These are browser simulations. No Git writes, tests, AI calls, email or deployments occur. Unsupported actions show a simulation notice. There is no public hosted demo currently.

For real work, install the portable core or deploy the native Cloudflare profile. An owned Cloudflare deployment requires an operator-enrolled Access identity and a current repository role. Access login proves identity; it does not create a Golf user or repository permission.

Work through a change

1. Open an accessible repository. Select a branch or exact commit and inspect its source/history.
2. Open an issue or a same-repository pull request using the available actions. Review the description, comparison and requested reviewers.
3. Request an authorized test against the current PR source. Inspect the actual terminal result and retained report; do not equate admission with success.
4. If configured, request optional Clef advice or a code proposal. Read the patch and tests before accepting its conclusions.
5. After passing approved tests, publish an allowed protected preview. Check its exact source and expiry.
6. Use only the merge operations supported by the installation. The native first slice supports an ancestor-base merge commit; broad protected merge and production promotion remain open.

You can also run the portable core. Ordinary portable repository work needs neither Cloudflare nor AI.

Read current availability

System status reports the running installation. Disabled, unconfigured, degraded and ready describe that setup; engineering qualification describes the evidence for each bounded implementation. Search/sort over loaded inventories does not imply full-server search.