Forkr is designed for agent-assisted setup. Give your coding agent the hosted quickstart prompt and let it install 4kr, collect the required GCP/domain/TLS values, deploy your environment, and prove it works.

​
Start with a prompt

Full prompt: https://forkr.sh/quickstart.md For Claude Code: 
curl https://forkr.sh/quickstart.md | claude
For Codex from the CLI: 
codex "$(curl -fsSL https://forkr.sh/quickstart.md)"
For Codex in the desktop app, start a new session and paste: 
https://forkr.sh/quickstart.md
The prompt tells the agent to install the CLI from forkr.sh, load 4kr setup agent, use the deploying-forkr and forkr-cli skills when available, start the setup UI on a local computer, and keep going until your environment is deployed.

​
Install the agent plugin

You can also install the Forkr plugin so /quickstart and the Forkr skills are available in future sessions. Clone the plugin source: 
git clone https://github.com/loopwork/forkr ~/.forkr/forkr
Install for Claude Code: 
claude plugin marketplace add ~/.forkr/forkr/agent-plugins/forkr-marketplace
claude plugin install forkr-plugin@forkr
Install for Codex: 
codex plugin marketplace add ~/.forkr/forkr/agent-plugins/forkr-marketplace
codex plugin add forkr-plugin@forkr
Then start a new agent session and run: 
/quickstart

​
What the agent will ask for

You need:
  • A GCP account with billing enabled.
  • A Forkr domain, for example 4kr.dev.
  • A publish domain or subdomain, for example 4kr.ai or apps.example.com.
  • DNS access for <forkr_domain>, api.<forkr_domain>, ssh.<forkr_domain>, *.<forkr_domain>, and *.<publish_domain>.
  • TLS certificates for those domains, or DNS/API access so the agent can help issue wildcard certificates.
The agent will use the setup UI and CLI commands such as: 
curl -fsSL https://forkr.sh | sh
4kr setup ui
4kr setup check
4kr setup deploy
The agent verifies that the selected GCP project is active before deployment, updates the ADC quota project when using GCP KMS/SOPS, and asks before mutating cloud resources or DNS records unless you are running a disposable verification. After deployment, it exports the runtime profile, creates a fork, runs a command in it, copies in an HTML file, starts a small web server, publishes it, and gives you the URL.

​
Try Forkr after setup

Once the agent finishes, your local CLI should point at the deployed profile. These commands create a fork, run Linux commands, copy in a page, and publish it: 
4kr health
4kr project current
4kr create hello-forkr
4kr exec hello-forkr -- cat /etc/os-release

cat > /tmp/forkr-hello.html <<'HTML'
<!doctype html>
<html>
  <head><meta charset="utf-8"><title>Hello from Forkr</title></head>
  <body><h1>Hello from Forkr</h1><p>This page is served from a fork.</p></body>
</html>
HTML

4kr cp /tmp/forkr-hello.html hello-forkr:/root/index.html
4kr exec hello-forkr -- sh -lc 'mkdir -p /srv/hello && cp /root/index.html /srv/hello/index.html'
4kr service start hello-forkr hello-web --port 8080 --publish hello -- sh -lc 'cd /srv/hello && python3 -m http.server 8080 --bind 0.0.0.0'
4kr service status hello-forkr hello-web
The published page is usually at https://hello.<publish_domain>. Useful follow-up commands: 
4kr list
4kr exec hello-forkr -- pwd
4kr service logs hello-forkr hello-web --lines 50
4kr service list hello-forkr
4kr delete hello-forkr --force