Show your carnival

[hamzaoza]

Everyone starts from the same water cannon. Show us where your carnival ended up.

Reply with:

• Your carnival's link, for example https://<your-username>.github.io/tessl-carnival/. If you haven't turned on GitHub Pages yet, ask your coding agent to Set up my fork.
• What your factory built: which games or changes it shipped, and the issues you labeled.
• One thing it got right and one thing it got wrong, so everyone learns from both.
• A screenshot, if you like.

New here? The README explains what the carnival is, and WORKSHOP.md walks you through building a factory on it.

[kwancheng]

https://kwancheng.github.io/tessl-carnival/

[clovis1122]

Link: https://clovis1122.github.io/tessl-carnival/

• Put my name on the carnival and painted the sky at sunset.
• Added Failing Objects, a survival game where you dodge stuff falling from the top.
• Added Bumper Cars, where you bump other cars out of the arena and try not to get knocked out yourself.
• Added High Striker, where you time your hammer swings and try to ring the bell.
• Set up a maintenance loop

Also, do I get anything for getting the highest score here 👀

[steffennissen]

https://steffennissen.github.io/tessl-carnival/

[kuhupandey5]

https://kuhupandey5.github.io/tessl-carnival/#/

[asoong-94]

https://asoong-94.github.io/tessl-carnival/

[kumar-d]

https://github.com/kumar-d/tessl-carnival.git

[hnipps]

https://hnipps.github.io/tessl-carnival/

Added:

• "Play again" and "back" buttons to water cannon game end screen - #1: Add Play again and Back to the midway buttons to the water cannon's round-over screen hnipps/tessl-carnival#2
• Pres "n" to transition to night and see a fireworks display

[Gillinghammer]

🎡 My carnival: http://tessl-carnival.gillingh.am/

What the factory built: A Picture.Repair blimp that slowly floats above the midway and links to https://picture.repair/. It also removed the top banner and sky widgets to give the carnival more open sky. Water Cannon is still playable.

What it got right: The finished blimp fits the illustrated carnival and stays still for reduced motion.

What it got wrong: In the first PR, the blimp sat mostly behind the awning and its keyboard link overlapped the header. A follow-up issue led the factory to fix both before the final deployment.

[tbonezx11-dev]

Sean-staggs.github.io/tessl-carnival

[javierInspiren]

https://javierinspiren.github.io/tessl-carnival/#/

[vishaalsc]

https://vishaalsc.com/tessl-carnival/

First change shipped by the factory: my name on the entrance sign and the browser tab, from issue to merged pull request without writing code. A sunset sky is on its way.

[jhoncorrea]

🎪 Feria de Jhonnatan

https://jhoncorrea.github.io/tessl-carnival/

What my factory built: I labeled issues jhoncorrea#1, jhoncorrea#3, and jhoncorrea#5 with tessl. The factory personalized the entrance sign and browser tab title, added local review lenses including the carnival’s house rules, and built Ring Toss with tests and instructions.

What went right: I completed the issue → agent → pull request → review → human merge → deployment workflow. Ring Toss is playable, and my first score of 10 appeared on the midway scoreboard.

What went wrong: I haven’t identified a concrete bug during my initial playthrough. Further gameplay testing is still needed.

My main takeaway: Tessl coordinates the agents and workflow, GitHub keeps the changes traceable, and I review and decide what to merge.

Greetings from Lima, Peru! 🇵🇪 Happy to be learning and building with you at AI DevCon NYC.

[crowjonah]

Here's Crow's Carnival.

My factory shipped:

• Crow's branding on the entrance, masthead, and browser title.
• ArcGIS-inspired topography with stacked terraces, risograph textures, restrained inks, atlas typography, and a geological cutaway with roots, plumbing, and buried relics.
• Ring Toss, Whack-a-Mole, and Hook a Duck, all with shared score storage.
• Water Cannon's shot counter, low-water gauge, rail rewards, themed shots, aim guide, and last-hit feedback before the final score.
• Corrected Water Cannon options and Ring Toss landing instructions.
• Five local review lenses, CODEOWNERS, and a tested validation runner that preserves evidence when reviews fail.
• Monday-morning doc gardening. Its first run found three stale documentation issues.

One thing it got right: the games registered themselves without loader edits. Real Ring Toss and Hook a Duck rounds each saved exactly one score, and replay worked.

One thing it got wrong: Whack-a-Mole passed CI but still showed 15 seconds remaining after 30 seconds at 10 FPS. We reproduced that and a spawn-timing bug, had the factory fix both, and reran the failures successfully before merging.

[ChrisKornaros]

Here's my carnival: https://chriskornaros.dev/tessl-carnival/#/

Just about everything went right, things went smoothly as well. I liked how seamless the github integration worked with Claude in the terminal. There were some initial bugs related to timing and some stale docs, both of which the agent caught and fixed.

[kmbaker]

https://kmbaker.github.io/tessl-carnival/

Most everything went right. Initially, I didn't realize I couldn't comment on a failed run or restart a run in the Tessl interface, but those are easy to do within Github.

[gendev1]

My carnival: https://gendev1.github.io/tessl-carnival/

My factory built eight new games from labeled issues: whack-a-mole, ring toss, hook a duck, balloon darts, high striker, skee-ball, shooting gallery and plinko.

[gaberger]

Link: https://gaberger.github.io/tesslio/

A Star Trek themed carnival. This is a fan project: the carnival now takes
place aboard the USS Enterprise, in orbit around Earth, with Captain Picard
strolling the deck.

[mhalpert]

Mike's carnival: https://mhalpert.github.io/tessl-carnival/

Set up a factory on my fork (mhalpert/tessl-carnival) with the Tessl CLI. Started with the Hello world "put my name on the carnival" issue: label → run → PR in about 4 minutes, review clean, merged. Then labelled all three New game issues at once.

One thing it got right: three parallel runs added ring toss, whack-a-mole and hook a duck, each self-contained in its own folder — CI green on all three and no merge conflicts. Code Review also caught a real (if minor) contract mismatch on the hook-a-duck PR: a lastCatch state field its renderer never used.

One thing it got wrong / had to be told: on a public repo a review finding alone doesn't start the fixer, so I had to leave a comment. Once I did, it removed the unused field rather than rendering it, explained the choice, and re-ran npm run check — then the re-review came back clean with "1 earlier finding addressed".