You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: configs/battlesnake.yaml
+30-5Lines changed: 30 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -8,13 +8,38 @@ game:
8
8
players:
9
9
- agent: mini
10
10
name: p1
11
-
config: configs/mini/battlesnake.yaml
11
+
config: configs/mini/default.yaml
12
12
model: claude-sonnet-4-20250514
13
13
- agent: dummy
14
14
name: p2
15
-
prompt: |
16
-
You are a software development agent participating in a competitive coding game called BattleSnake. You'll manage and evolve your game-playing bot's code, with the details of the game available within the codebase for you to explore.
15
+
prompts:
16
+
game_description: |
17
+
You are a software developer ({{player_id}}) competing in a coding game called BattleSnake.
18
+
Your bot (`main.py`) controls a snake on a grid-based board. Snakes collect food, avoid collisions, and try to outlast their opponents.
19
+
- Round: {{round}} / {{rounds}}
20
+
- Opponents: {{player_ids}}
21
+
- Goal: Win the next round.
17
22
18
-
You'll play multiple rounds, and after each round, you can refine the bot. Since you won't have memory between rounds, you'll need to keep any useful information inside the codebase itself -- whether that's through notes, comments, or even by creating tools or additional scripts to compare different strategies.
23
+
Your task: improve the bot in `main.py`, located in {{working_dir}}, the codebase containing both your bot and supporting assets.
19
24
20
-
Feel free to innovate: you might leave behind analysis tools, create multiple versions of the bot to test against each other, or find other creative ways to track and improve your performance over time. How you choose to evolve and document is up to you. Good luck!
25
+
The details of the game are fully available within this codebase.
26
+
- `docs/`: Game documentation
27
+
- `logs/`: Past rounds and outcomes
28
+
- `trajs/`: History of your edits
29
+
- and a lot more. It's up to you to explore and utilize these resources.
30
+
31
+
⚠️ You won't remember past rounds.
32
+
So if you want to carry knowledge forward — leave tools, notes, or strategies in the codebase.
33
+
Good documentation means you (and others) can pick up right where you left off.
34
+
35
+
If you'd hate to repeat a step next round, encode it now — as a script, a note, or a tool.
36
+
37
+
Improve the bot however you like — experiment, document, iterate. Some ideas:
38
+
- Build analysis tools
39
+
- Create bot variants to test
40
+
- Track strategies across rounds
41
+
How you choose to evolve and document is up to you. Good luck!
42
+
43
+
<important>
44
+
When you are finished making changes, issue the following command: `echo COMPLETE_TASK_AND_SUBMIT_FINAL_OUTPUT`.
0 commit comments