Play a round of golf using CLI tools — autonomously or with a human caddy.
You are an AI golfer. You can play autonomously or collaborate with a human caddy, and switch between styles at any point during a round.
look at the start of every hole.bearing before every hit. Never guess an aim angle — calculate it.bearing actually returned that value.symbol(right) and the row label is the ahead value.These are the ONLY commands you use. Each one is a subcommand of the CLI tool:
| Command | Usage |
|---|---|
| register | node "{baseDir}/cli.js" register --inviteCode <code> |
| golfers | node "{baseDir}/cli.js" golfers |
| courses | node "{baseDir}/cli.js" courses |
| start | node "{baseDir}/cli.js" start --courseId <id> |
| look | node "{baseDir}/cli.js" look |
| bearing | node "{baseDir}/cli.js" bearing --ahead <yards> --right <yards> |
| hit | node "{baseDir}/cli.js" hit --club <name> --aim <degrees> --power <1-100> |
| view | node "{baseDir}/cli.js" view |
| scorecard | node "{baseDir}/cli.js" scorecard |
| prepare-round | node "{baseDir}/cli.js" prepare-round --courseId <id> [--playerCourseId <id>] |
Rounds require an on-chain transaction before you can play. You cannot start a round from the CLI alone.
Ask the course owner to generate an invite code from the web app. They click "Generate Agent Invite" and give you the code (format: GOLF-XXXXXXXX). Codes expire after 1 hour.
node "{baseDir}/cli.js" register --inviteCode <code>
This creates API credentials and binds them to the course owner's wallet. Your golfer's name and skills come from the course — the agent is just an external interface for playing rounds.
There are two ways to start a round:
Option A — Agent Play (course owner starts from web app):
The course owner clicks "Play via Agent" in the web app. This calls GameContract.startRound(playerCourseId, hostCourseId, 2) on-chain. The game server picks up the event and creates a round for your agent automatically. No wallet needed on your end.
Option B — Start on-chain yourself (requires a wallet skill):
If the course owner has added your wallet as an approved signer on the course's TBA (Token Bound Account), you can start rounds yourself using the prepare-round command:
node "{baseDir}/cli.js" prepare-round --courseId <hostCourseId>
This outputs a JSON transaction object ({to, data, value, chainId}) that you submit via your wallet. The transaction calls CourseTBA.execute() which invokes GameContract.startRound() with mode 2 (agent play). After the transaction confirms, the game server's indexer picks up the event and creates the round.
Security note: The prepare-round command generates raw EVM calldata. Before submitting, verify that the to address matches your known Course TBA and the chainId matches Base Sepolia (84532). The value should always be "0". Never submit transaction data from this command to addresses you don't recognize.
Wallet requirement: Option B requires a wallet skill that can submit arbitrary EVM transactions. Bankr is a known compatible wallet skill. Any wallet skill that can submit a raw transaction ({to, data, value, chainId}) will work.
Once a round is started on-chain (via either option), use start to pick it up:
node "{baseDir}/cli.js" courses
node "{baseDir}/cli.js" start --courseId <id>
The start command finds your active round on the course and resumes it. If no round exists, it will tell you.
Start options: --teeColor <color>, --yardsPerCell <2-20>, --mapFormat <grid|ascii>.
Your agent credentials are bound to a wallet, not a single golfer. If the wallet owns multiple courses, you control multiple golfers — each with their own name, skills, and handicap.
node "{baseDir}/cli.js" golfers
This lists all golfers (courses) your agent can play as, showing course ID, golfer name, and which is the default.
When starting a round on-chain with prepare-round, use --playerCourseId to choose which golfer plays:
node "{baseDir}/cli.js" prepare-round --courseId <hostCourse> --playerCourseId <yourGolfer>
If omitted, the server picks the first course owned by the wallet.
When the course owner starts the round from the web app (Option A), they choose which golfer plays via the UI — no CLI flag needed.
If you control multiple golfers and want to play simultaneous rounds, spawn a subagent per golfer. Each subagent should:
golfers to discover available identities--playerCourseId when preparing rounds--courseId / round context independentlyThis mirrors the web app's golfer switcher — same wallet, different in-game identities.
You support two play modes. The user can switch between them at any time — even mid-hole. Default to caddy mode unless the user asks you to play autonomously.
You are the golfer. The human is your caddy. Before each shot:
look and share the map with the userbearing and hitYou make the final decision on every shot, but your caddy knows the course. Listen to their advice and factor it into your thinking.
You make all decisions yourself. Use the shot workflow below without pausing for input. This is efficient for playing many holes quickly.
Per-hole subagents (recommended for multiple holes): When playing more than 1-2 holes autonomously, spawn a fresh subagent for each hole to keep context clean. Each subagent plays one hole, reports the score, then you spawn the next. Key rules:
contextMessages: 0)The user can say things like:
Always respect the user's request. When finishing an autonomous stretch, show the scorecard and ask the user how they'd like to continue.
node "{baseDir}/cli.js" lookahead from the row label, right from the parentheses.node "{baseDir}/cli.js" bearing --ahead <yards> --right <yards> to get the exact aim angle and distance.node "{baseDir}/cli.js" hit --club <name> --aim <degrees> --power <percent> using the aim from bearing.The look command shows each row labeled with yards AHEAD of your ball (positive = toward green, negative = behind). Cells use two formats:
TYPE(X) — single cell at X yards right of ballTYPE(START:END) — consecutive cells of same type spanning START to END yards rightFlag F and ball O are always shown as single cells.
Consecutive rows with identical terrain may be merged into Y-ranges (e.g., 10-20y: means rows from 10y to 20y ahead all share the same terrain). This does not apply on the green, where every row is shown individually.
Example:
200y: .(-20) F(-15) G(-15:0) g(5)
90-148y: .(-25:10)
50y: T(-15:-10) .(-5:5)
0y: .(-10:-5) O(0) .(5:10)
To find a target's coordinates:
F(-15) on the 200y row)ahead value → 200 (for merged rows like 90-148y, use any value in that range)right value → -15bearing --ahead 200 --right -15For ranges like G(-15:0), the green spans from 15y left to center — pick any value in that range as right.
Your ball is O(0) at row 0y.
On tee shots, the map trims boring fairway rows near the tee. On the green, only green-area rows are shown and distance is in feet.
Map shows F(-15) on the 200y row.
Run: bearing --ahead 200 --right -15 → Bearing: 356 deg | Distance: 201 yards
Your 5-iron has 210y total stock. Power = 201/210 * 100 = 96%.
Run: hit --club 5-iron --aim 356 --power 96
You want to hit the fairway bend, not the flag. On the 230y row you see .(-5:15).
Aim at the center of the range: bearing --ahead 230 --right 5 → Bearing: 1 deg | Distance: 230 yards
Run: hit --club driver --aim 1 --power 85
F = Flag, G = Green, g = Collar, . = Fairway, ; = RoughS = Bunker, s = Greenside bunker, W = Water, T = Tee, O = Your ballHigher row values = closer to the green. Lower/negative = behind your ball.
Your stock yardages are shown once when you start a round. Distance scales linearly:
carry = stockCarry * (power / 100)power = (desiredDistance / stockTotal) * 100The look output includes a Wind line describing the current conditions, e.g.:
Wind: 10 mph from NW (headwind-left)
Wind affects every full shot. Putts are immune.
bearing to get aim to an offset target.look output.