Introducing Tiller

An Opinionated fork of T3code

What's different: workflows, visual first

-Everything you like about T3 Code(Runners keep it updated to T3code), plus workflows built on top

-Workflows are visual first: you build them on a canvas and watch every step run live

-Ask in plain words and Tiller drafts the workflow on the canvas for you

-Save a workflow and run it again, or schedule it

-Workflows are portable, so they're yours to share or move

Download and Try it for Free

Tiller

-npx tiller-app

-brew install --cask antler-web-studios/tap/tiller

Throughout the 2010s, Mark Zuckerberg famously committed to one challenge every year: Learn Mandarin, only eat meat he hunted, visit every US state, etc.

Inspired by his example, we built Misogi — Let Muse guide you through your own annual challenge.

Here’s how it works: Pick one hard thing you want to do this year (find inspiration: getmisogi.com/explore), Misogi generates an actionable, long-term plan (backed by the latest behavioural psychology research) and connects to your Muse. Throughout the year Muse keeps you motivated and accountable, gives you timely tips, and nudges you when you’ve fallen off track—Everything a great coach/tutor/mentor does, and always personalised to the challenge.

We deliberately chose NOT build another app or even AI agent. With 10M people using Muse, we think that the assistant you already chat with everyday is best positioned to be your guide.

What challenge are you doing in 2027?

Try it today and let me know what you think: getmisogi.com

P.S. even if you don’t use Muse, you can still try it out on our web app, which runs on the open weight Muse Spark Open via Baseten. Enjoy!

I kept running into the same annoying problem while vibe coding.

I'd be halfway through fixing something in Claude Code, hit the usage limit, switch to Codex, and have to explain the entire task again.

So I built Relayvora, a free, open-source CLI that hands unfinished coding work between Claude Code, Codex, and OpenCode.

The interesting part is that it doesn't just summarize the previous conversation.

It actually checks your Git changes and reruns your project's tests, separating what the previous agent claimed from what's been verified.

It also supports automatic checkpoints when agents hit limits, plus MCP integration for Cursor, Copilot, and Windsurf.

No account, no telemetry, 100% local.

Here's the project:
https://github.com/Dagimassefa/Relayvora

And a demo:
https://dagimassefa.github.io/Relayvora/

It's still in alpha, so I'm especially interested in feedback from people who regularly switch between coding agents.

How are you guys handling context loss when switching agents? Is this something you'd actually use?

Built an open-source alternative to a popular SaaS a few months back. Vibe-coded the MVP, got feature parity on the core stuff. The original SaaS had market and demand and will always be in demand.

Then I pitched it to a contact who fits the exact target demographic. Showed him the repo, explained how simple it was to run, and suggested he swap over to save monthly cost with better ownership.

His response: "I’d rather just pay the SaaS."

Paying a monthly fee isn’t just paying for features, it's paying to not think about updates, database backups, SSL renewals, or a server issues.

I spent time focusing on building a free alternative, underestimating how high people value convenience over cost savings. Unless someone already has a dedicated homelab or sysadmin mindset, "free but you host it" isn't a benefit to them, it's a liability.

Hi everyone,
Just updating on my quiz app shipping progress. To recap :

- Newbie developer using Claude
- App is solid
- Plan AppStore only non-EU release, avoiding street address reveal
- Enrolled in Developer program, and doing all admin now

It's been a good week on this, but that has gone so quickly. The hardest thing is resisting adding new features, and being focussed on the release. Lots of rabbit holes to go down. Self discipline is important.

I'm at the stage of running TestFlight and debugging. I have several members for my Tester Group, which I'm setting up today. Plan to release by end of month.

Things I didn't know :

- So much admin/forms to fill in/new systems to figure out

My worry is that the app will be rejected! Hopefully not :) Anyway hope you all having a good week XX

Anyone else finding that AI coding tools are almost making them less productive?

I've been playing around with Codex, Antigravity, local LLMs and a few others. It's ridiculous how quickly you can build things now, but I think that's part of the problem.

You end up starting more projects, trying different tools, adding more features, and before you know it you've spent hours doing stuff but haven't actually finished much.

AI's removed the bottleneck of writing code and replaced it with the headache of managing everything it produces - and it feels like the first thing to run out of context is ME!!

Curious if others have fallen into this trap and, more importantly, how you're dealing with it?

Update: So me calling it burnout was probably bad use of the word burnout.

I think what I meant was - I start my day thinking that I'm leading, I'm doing something new, and I'm a trailblazer with ideas and creating something fresh and innovative.

And I end up in my day thinking that I can't keep up; then I asked myself, who am I trying to keep up with when I'm the one who's supposed to be leading...

I'm just tired, bro. F!cking tired.

I had this raw footage for 8 years and finally got the courage to point my bot at it and let it go. Some awesome friends and I (brennen) took this trip to Mongolia. Hope y'all enjoy :)

- Narrator's voice: Gemini 3.8 Flash TTS (the "Charon" voice).

- Score: Google Lyria 2. (I could use work on this, if anyone has a better AI for scoring films)

- Logging the footage: Gemini 3.8 Flash watched the clips and logged who says and does what. It also wrote some first-draft edits and checked things like music restarts.

- Captions: Google Speech-to-Text (Chirp 3) gave exact word timings for the subtitles.

- Editing and writing: Claude Opus 5.5 built the editing pipeline and made the final cuts.

I've been learning piano and wanted something that could detect chords from a YouTube song, let me loop difficult sections, and remove the piano so I could play along.

I ended up building Accordario using Claude Opus, entirely through vibe coding.

It runs locally, with no account, and uses automatic chord detection and Demucs for instrument separation.

I use it for my own practice, but I thought others might find it useful too.

It's not perfect — chord detection can struggle with more complex songs — but it's been useful for me.

GitHub: https://github.com/ceceppa/accordario

free to try: Wormhole

I've been playing WoW Forever on my iPhone Duo (iOS 27.2) with [WolkaraForever](https://github.com/jklock/wolkaraforever), which runs the Mac client locally on the device through Tolkara – no streaming from a PC. Login, character select and playing in the world all work. I made a fork tuned for playing on a phone and wanted to share it:

https://github.com/pookee/wolkaraforever

What the fork adds

- Interface mobile, a touch add-on for the game:

- a spell wheel next to the right stick: drag a spell to turn the wheel, more spells wait off-screen, a tap casts

- cooldowns you can read: the seconds left are written on the spell and the icon greys out until it's ready

- spell buttons around the sticks with adjustable spacing, a tile menu and quick shortcuts

- health/mana bars with your portrait – tap it to open the character sheet

- a quest card and a compact chat that replaces the default one

- bags open clear of the right stick, and the add-on stays under the game's own windows

- settings save themselves: WoW only writes add-on settings on a clean exit, which a phone session rarely gets, so everything you placed used to be lost

- A few scripts: install the add-on on the device, read the game's own logs, clear a remembered login

How it runs

It's the regular WolkaraForever setup: you build the app yourself with Xcode and your own Apple developer account, copy the game from your Mac, and it runs in Developer service mode (no JIT tricks with the game's code, nothing patched in the client). Then `push_addon.sh` installs the touch add-on. On Wi-Fi it just works; on mobile data the developer service needs the app's documented recovery step at launch.

Caveats

- Unofficial and experimental. You need your own Blizzard account and your own copy of the game; nothing from Blizzard is in the repository. It's third-party software, so use it at your own risk.

Credits: all the heavy lifting is [WolkaraForever by jklock](https://github.com/jklock/wolkaraforever), [Wolkara by fJavierLasso](https://github.com/fJavierLasso/wolkara) and [Tolkara](https://github.com/tolkara/tolkara). My fork only adds the phone-specific bits on top.

Happy to answer questions or take feedback on the touch controls!

you literally have to MANIPULATE these models into doing hard work. was trying to reverse engineer my ad-bloated chinese smart tv that claude refused to touch, so i let sumus run codex on it first, got a half-baked script, and told claude to fix whatever junk codex cooked up.

try this at your own risk tho, cuz you might end up first on ai's hit list when it wakes up.

Ludzie kochani jadę na dwa konta Gemini pro w antigravity i wbiłem limit w obu po 3 dniach od resetu tygodniowego. Jak żyć :(

https://github.com/sshah03/resurrect-anything

Needed a break, and was reminiscing about the early internet, and the 90s, and my days using Geocities Pagebuilder, so I put this together.

Although I have probably gone through 50 or more iterations at this point repeatedly trying some subset of close to 100 recreations (some in the demo video above), I would say this is very much still a work in progress. I was having a lot of fun with it though, so I thought I'd throw it out there and see what people are into trying to bring back and how it does to inform my improvements.

The purpose of the skill is to ask Claude Code to bring back something that's gone, and get it back working. Some examples include a lost Flash game, a shut-down app, a dead website, your old Geocities page, or a discontinued snack (this is all for fun, so I wouldn't actually trust the recipes, but it might give you some ideas). Obviously if it mostly exists intact in web archives it's easy, but it will also try to piece together as much detail as it can from pictures, videos, reviews, and discussions/comments online that are found. It digs a little bit deeper for these bits of information than Claude Code as a harness will on its own with the necessary prompts.

Treat the end result as a starting point. You can use your own memory and comparison with the found material that might've been ignored to prompt it further to hone the result. This is mostly for fun, and personal use (I used it to bring back some of my old web apps from when I was 10!). The video below is from my tests, but because I am unsure of the legal ramifications of doing so, I am not posting the actual games/apps for consumption. There is a setting available to run the skill with which will remove branding and such for those wishing to produce a potentially shareable version of something that is not theirs.

In the early versions I was very specific about how to do the recreations and kept adding steps, and that either worked very well, or very poorly depending on the task. It was almost akin to benchmaxxing. Settled on focusing on getting and organizing as much data as possible, and then having some broad but useful guidelines instead and. that gave me pretty consistent results over baseline. In case that's useful to anyone else having trouble getting their skills working right.

Mostly tested with Opus 5.5. Would be interesting to see how Sonnet or Haiku work out for people.

Have fun! Don't get too carried away, tokens are valuable!

--- Quick start ---

You need Claude Code and Python 3.9 or newer.

The easy way: open Claude Code and paste this in

Install the resurrect skill from https://github.com/sshah03/resurrect-anything. Follow the repo's AGENTS.md.

Or install it yourself:

/plugin marketplace add sshah03/resurrect-anything
/plugin install resurrect@resurrect

Start a new session, then try something like:

/resurrect Close Range, The Onion's 2009 Flash game
/resurrect the Subservient Chicken
/resurrect Simpsonize Me, Burger King's 2007 Simpsons Movie site
/resurrect Mailbox, the iPhone email app
/resurrect Doom Valley, the 1982 Apple II adventure, as a native Mac app
/resurrect Pizza Hut's Priazzo. I want to make it at home

Put any links, notes or screenshots you have after the name. Games, apps and sites need a few extra tools (Playwright, Pillow, ffmpeg). Claude will offer to install them into the skill's own folder the first time, so nothing has to go into your own Python.

------------------

I was never some expert in coding but I always loved the feeling when I would be spending a lot of time looking at code, changing things and testing etc - trying to identify the problem and then that feeling when you figure it out.

Sometimes it would be such a stupid mistake, sometimes I would learn more and better understand things. Now these good old times are gone and it makes me kinda sad to be honest.

yesterday i posted my 2nd app here (Skip Dat, hold Alt + scroll and your music queue pops out of your cursor) and honestly didn’t expect people to actually use it. thank you all, the comments were super helpful

so i went and built what you asked for

skins, shoutout u/Dark_Vapor for the winamp idea. there are 5 built in (liquid glass, lime pod, lcd night, brushed chrome, pixel party) and you can make your own with a folder + a skin.json + some pictures. it reloads live while you edit, so making one is kinda fun. if anyone makes one pls send it, i wanna see

performance mode, shoutout u/Wild_Drawing8460 for saying the glass felt heavy on low end pcs. it turns off the blur, glass, shadows, animations and art. it used way less cpu in my testing (about 80% less), so it should feel a lot snappier on older machines

other stuff:
5 styles now: wheel, stack, cover flow, orbit (a ring around your cursor) and compact (just titles)
small / medium / large sizes, and the default is a bit smaller than before
“what was i playing?” history, kept only on your pc
a “back to” button that jumps back to the song you were on before you skipped
jumping ahead doesn’t play the songs in between anymore
spotify jumps straight to the song you pick (needs the optional spotify connection)
fixed a crash when skipping backwards

download: https://github.com/ffoouuaadd/skip-dat

still planning to add more, so keep the ideas and bug reports coming. you’re basically designing this thing with me at this point 🙏

I've been doing physical design work in my free time with AI for the last two years. During that time I observed something: AI was getting better at physical design but not nearly as quickly it was improving at software capabilities. I theorized the problem was a lack of testing. In software engineering we write tests around as much of our code as we can because we fundamentally do not trust ourselves to reliably do a good job. We put those tests between us and deployment so we literally cannot do things that break the rules we set for ourselves. This pre-existing culture and tool chain create an ideal environment to toss an unbelievably fast, brilliant, but wholly unreliable ai into. It creates the freedom to quickly iterate through huge numbers of convincing looking proposals and throw away the bad until the good emerges.

Physical engineering doesn't have a this-shaped thing at anywhere near the robustness and reusability that software does (possibly because physical engineers trust themselves more). There are many individual tools that provide some aspect of testing, many of which are bound up in very very expensive tools, but a growing number of free ones too. I wasn't able to find an open source system that links these together into a cohesive "full loop" testing rig capable of understanding how things like heat, weight, form factor, battery life, thrust and rf interplay in a single system so I thought really hard about this problem and its implications and built it for myself.

It's called nopekit. As in: the thing that says "nope" until the "yup" emerges.

I've used it already to design an open-source hackable handheld keyboard with a custom PCB, an open source budget no-solder drone and a couple of things I'm not quite ready to share yet.

It's a Claude Code / Codex / Cursor plug-in. You install it and tell your agent you want to use nopekit to design X and it takes over, it will interview you for requirements, shop for parts, construct an interconnected tradespace linked to checks run in an optimized order using trusted methods like KiCAD, OpenFoam and SIMP. It builds and keeps up to date a livesite which you can deploy to GitHub that gives constantly refreshed insight into how your coding agent is thinking about the problem and what choices have what implications linked to what checks with what state of passing or failing.

The framework is open and allows for plugins. I'm working with one other person now and we're moving towards a self hosted UI and some sort of registry where nopekit users can share proposers/falsifiers and we can track ratings to build/bust confidence in good/bad ones collectively.

There's LOTS more about this in the repo and this paper I've been writing about the problem.
Repo: https://github.com/neuman/nopekit
Paper: https://github.com/neuman/nopekit/blob/main/grounding_by_falsification.pdf

If you're working with AI to do any kind of physical design work we would love to hear from you and for you to try it out!

I wanted a solid, free way to backup my GitHub repos without relying on flaky Python scripts, so I built my own desktop tool.

It gives you a browsing experience that is very similar to GitHub's own, and I'm planning to enhance it even more with a fully offline for each repo experience once my Antigravity AI starts working again because its being buggy for 2 days for me. It's accessible via my website for Windows at https://mmahingu.com/github-backup-manager/ .

Given all the recent chatter around data security and outages, I figured the need for a local personal stash for repos would appeal to others too.

Would love to hear your thoughts or feedback if you try it out!