marketing-screenshotlisted

# Marketing screenshot Use the native macOS app with fictional project data. Confirm consent and a small turn budget before starting `runtime = "pty"`: creating each bot starts a real, billed Claude Code session. Use `double` for a free layout rehearsal; it cannot demonstrate genuine agent behavior. Keep the installed app and daemon untouched. Never assume their port or data location; use a fresh daemon home and an unused test port. Requirements are in `CONTRIBUTING.md`; the driver additionally requires Node 22+. A real run needs an authenticated `claude` executable on PATH. Do not print credentials, raw process command lines, or real session transcripts into shared reports. ## Setup Run from the repository root, in a dedicated terminal. These examples use 49888 for the daemon and 1420 for the frontend. Check both are free first; choose other ports consistently if occupied, without stopping their owners. Keep shell tracing off when loading credentials. ```bash umask 077 SHOT_DIR=$(mktemp -d "${TMPDIR:-/tmp}/gravity-shot.XXXXXX") SHOT_DIR=$(cd "$SHOT_DIR" && pwd -P) # canonical paths also avoid transcript aliases export GRAVITY_HOME="$SHOT_DIR/daemon" export GRAVITY_WS=ws://127.0.0.1:49888/ws mkdir -p "$GRAVITY_HOME" "$SHOT_DIR/shots" CLAUDE_BIN=$(command -v claude) cargo build -p gravityd ./scripts/prepare-sidecar.sh cat > "$GRAVITY_HOME/gravityd.toml" <<EOF home = "$GRAVITY_HOME" bind = ["127.0.0.1"] port = 49888 negotiate_port = false runtime = "pty" claude_bin = "$CL