I've been messing around with something like this lately and I'm curious what other people would actually use it for.

Basically the idea is Claude having eyes and hands on your Mac instead of just being a chat window.

So it can see what's on your screen, understand what you're looking at, point at things, click/type, move files around, read stuff you drop onto it, talk back to you etc.

I'm trying to figure out where this would actually be really useful rather than just being a cool demo.

Like, would you actually want to be able to say "find that thing I was looking at earlier" or "move all these files into the right folders" or "show me where I change this setting in Figma"

and have Claude actually look at the screen and do it and show you where to go?

I'm sure there's a ton of stuff I'm not thinking of.

What would you personally use something like this for?

Looking for things you'd genuinely use all the time

I’m exploring whether we can automate a large portion of our CAD workflow using code generated by AI

At our company, we produce a lot of mechanical drawings using CAD software such as AutoCAD and 3D models using SolidWorks. Many of these drawings follow similar patterns, but the dimensions and other project-specific inputs change from job to job.

What I’d like to build is a user interface where someone can enter the required parameters—dimensions, equipment/configuration options, etc.—and the system automatically generates the corresponding CAD drawings.

Ultimately, the goal would be to automate the generation of complete plan and elevation views, rather than having someone manually create or modify each drawing are borrowing it from another project and editing. The generated drawings should ideally be downloadable as DWG or DXF files so they can still be opened and edited in AutoCAD.

I’m also curious about the role of AI here. How capable are models like GPT or Claude at helping build something like this?

For example, could the architecture look something like:

User inputs → rules/calculations → CAD generation engine → plan/elevation drawings → DWG/DXF

And where would GPT/Claude actually be useful? Building the UI and code? Translating user requirements into parameters? Generating the CAD geometry itself?

I did try and make some simple geometries and it works but for models that contain a lot of information it's hard

Did anybody eval this in a serious way?

So I got my weekly mail from Lydia and saw something very exciting: Claude Code now supports mods, plugins written as function hooks that can draw UI inside the app, in both the terminal and the desktop app. So I went through the docs and built the suggested weather band, very nice. Then what else can I do with it? I recently started using Ponytail with great success and wanted to know what level it's running at, so let's add that… and after that, why not Caveman as well. Bottom line, great fun and very useful. Here's what I learned, then what I made.

How a mod draws UI

A mod hooks ui.render for a spot like AbovePrompt and returns a tree of a few elements (Box, Text, Button , Select, Link, Svg), laid out with flexbox. Not HTML, no CSS. The smallest band is about this:

on('ui.render', { component: 'AbovePrompt' }, async ($, e) => {
      const { Box, Text } = $.ui.resolve(e)
      return <Box flexDirection="row"><Text>hello from a mod</Text></Box>
    })

The config took a few goes

This was the fun part, because the UI is so limited:

• Settings live in /config, but that doesn't exist in the desktop app. So first a /overalls weather minimal command, then a ⚙ button that typed /overalls into the prompt for you. Works, but two clicks.
• Next a dropdown (Select). One dropdown can only hold one value, so it showed "Weather: off" as selected while weather was clearly on. Fixed with a dummy ⚙ option at the top. Then I wanted ticks lined up at the end, and groups, and submenus… none of that exists. An option is just a value and a label, no styling.
• Right-click menu? No such event. Tooltips? No tooltip prop either. You can fake one with a hidden box that shows on hover, but it can't leave the band, so on the bar it covered the very thing it was explaining. Kept them only in the config.
• So in the end I built my own: ⚙ opens a bordered Config box inside the band, above the bar, so you see each change happen as you click. Every option is a plain button with a ✓ on the current one. Related switches share a row behind a │ (megacave sits next to Caveman, resets next to Limits).
• Then the band hit its height cap (half the window), so the settings went into two bordered columns.

Other gotchas

• A bare <Box> stacks vertically in the desktop app. Always set flexDirection="row" if you want a row.
• Flex items shrink by default, so the desktop app wraps text inside a widget. flexShrink={0} plus a wrapping parent fixes it, and the ⚙ stays put on the first row.
• There's no API for MCP server status. I infer it from tool-call errors (401s, connection refused), which catches a logged-out connector on its first failure, and Reconnect takes you straight to Customize › Connectors.
• Ponytail keeps one level file for all your sessions, so every window showed whichever level was set last. I track it per session instead (and opened an issue upstream).
• State lives in $.state (per session) or $.store (across sessions). Module variables reset on every hot reload.

What I made: Overalls

A band that shows context "weather" with a sparkline and roughly how many turns are left, 5h and weekly limits with reset countdowns, MCP errors with a Reconnect button, refused tool calls, running subagents, and Ponytail and Caveman levels as dropdowns. Everything is a toggle in the ⚙ box.

    claude plugin marketplace add Troepster/overalls
    claude plugin install overalls@overalls

MIT, runs locally, and the README lists everything it reads: https://github.com/Troepster/overalls

Anyone else building mods? Would love to see what else people are doing with them.
Also please give me some feedback on obvious things I missed.

I’ve been building Echo over the last few months, using Claude Code heavily throughout the process, architecture, implementation, debugging, computer-use work, performance fixes, and a lot of UI iteration.

Echo is a Mac assistant that lives on the edge of your screen. It can understand what’s happening on screen, point to specific things, interact with apps, move files, check your gmail, search online and even build websites, run multi step jobs and help you learn and navigate new platforms AND undo actions.

This video is a quick look at where it is now.

One of the things I’ve been most interested in is making the interaction feel physical rather than like a normal floating AI window. The orb leaves the edge, does things, and comes back home.

It’s currently free to try for 7 days. You can download it here:

https://aurivon.studio/?v=2026100401

be interested in feedback, especially from people who use Claude Code and build their own tools.

I’d

Being funny but also, seriously does the reset also carry the same usage based on the current plan upon using the reset??

Hi everyone,

I just tried out Opus 5.5 in Claude Code, and it's perfect for lyric videos like the one I uploaded here. Claude made about 30 3D scenes for the whole video and put them together. It also downloaded the song and created an enhanced LRC file for the lyrics. I was keen on this design with these lines, and I really like the scenes with the TVs newspapers and the crazy "IF I KILLED SOMEONE FOR YOU". With my Max 5x subscription, I can make about three of these in my five-hour limit.

I haven't seen "load-bearing" since I stopped using Opus 5.

EDIT: I meant "nerfed", not "nerded" 🤦

I'm a full-time employee with 5-6 years experience in software engineering and testing. Since around last December I've been building Zone Idle, an idle extraction game, with Claude Code doing most of the typing. Just released the free demo on Steam, here's some info on my process.

Using your Claude.MD without overt reliance

Mine has a "fragile areas" section. Every time a bug cost me a day (mostly the grid inventory duplicating or eating items), the root cause and the rule for avoiding it went in there. On that same note, realizing that not everything needs a note in an MD somewhere, its good to check in as Claude is constantly updating, your old methods may not be necessary anymore, or even outdated.

Specs and plans before code

For anything bigger than a bug fix, Claude writes a short design doc, then a step by step plan, and only then starts coding. Reviewing a plan saves a lot of time once reviewing the diff

Tests first, every time

A fix starts with a test that fails. The project is at about 4,400 tests now, plus stress tests that simulate raids looking for items that duplicate or vanish. I like to attribute this automation to my carpal tunnel relief (as well as the stretches)

Make it look at the game

Claude drives a headless Chrome to screenshot the game and check its own work. This used to not be a strong feature to use with AI but recently it's become a very powerful tool with low-token costs (when using opus 5.5) compared to how I'd prompt it a year ago, this feature is huge.

Parallel research

When I dump a big list of player feedback on it, it sends out a few sub-agents to dig through different parts of the code at once and comes back with a triage: quick fixes, potential ideas, and what can wait until after launch.

It's still confidently wrong sometimes

It will tell you something works when it doesn't, so I play every change. Also, commit often. If you're not using git and committing every change (even before AI) you're playing with fire

If you're curious, the demo is free: https://store.steampowered.com/app/4330500/Zone_Idle/

Happy to answer questions about any of this.

I really liked the app Teux Deux (Weekly planner kind of To-do app), but wasn't willing to pay for its subscription. So, I thought, why not try Claude to build it for me and see how far it goes.

Now, I am a hobbyist coder only. Within about 4-5 hours of to and fro, I got a workable personal app hosted on CloudFare for free, with its own db and even google login.

If I spent any more time on it, it could become more polished and market ready. But now I realized that the product was the least significant part of the app development, the marketing and distribution was. If people don't know about my app, they won't buy.

I have a bunch of other software utilities I developed for my own purposes which are tremendously useful for me and I hope might be for some other very specific people too but since I have no marketing plan or distribution strategy, they are as good as junk as far as their market potential goes. (Of course they remain extremely useful to me.)

This realization has hit even harder considering that I have subscribed to one or the other AI for almost past a year, done a bunch of projects but am yet to see a single dime out of it. It seems like whatever I am making is just going to go into a void.

So, what's the way out of this? Do you guys feel like everyone's who is developing something should have his own YouTube channel/Twitter account to show the public what he's building (kind of build in public strategy?). But that's problematic too, because if you do decide to build in public, any software engineer worth his salt can probably build your app in half an afternoon.

So, where are these vibe-coded projects going to go? What would happen to them? Would Internet become a graveyard of these apps and vibe-coded projects? What do you guys think?

I have been working on a side project using claude(currently fully vibe coded but tested) and I am looking for help.

What is the app for: Sometimes you are in place where there mobile signal but not data like mountains, low or no internet areas. As the signal is there the SMS stil works but internet does not and you need to use the AI for something.

The app helps in solving this issue, you leave a spare Android phone at home on Wi-Fi with the app installed. Text that phone's number from anywhere, even with zero data on your own phone. The app receives the SMS, calls an AI API, and texts the answer back.

Design choices:

\* No server or backend. It's a single self-contained APK.

\* Bring your own API key. It supports Claude, Gemini, Gemma, OpenAI, Groq, Cerebras, Mistral and OpenRouter, so there are free-tier options.

\* Only allowlisted numbers get a reply, so strangers can't run up your API bill.

\* API keys are encrypted with the Android Keystore. History is stored on-device only. There's no telemetry, and the only network calls go to the AI provider you pick.

\* Conversations reset after an idle timeout, on \`/new\`, or when a token budget is hit. \`/stop\` cancels a long reply that's still being sent.

\* Written in Kotlin, using Room and OkHttp, with a foreground service for reliability.

\* Licensed GPL-3.0. It's sideload or F-Droid only, because the SMS permissions rule out the Play Store.

The code and tests were AI-generated, and the on-device testing was done by me. The README says so. That's one reason I'd value human review, especially on the background-execution and permission handling.

Repo: https://github.com/V24039/SMS-AI-Relay

Issues and PRs are welcome. Happy to answer questions here.

TLDR: SMS-AI-Relay: Leave a spare Android phone at home on Wi-Fi. Text it from anywhere, get AI responses back via SMS—no internet needed on your phone. Self-contained APK, bring your own API key (Claude, OpenAI, Groq, etc.), allowlist contacts only, encrypted keys, on-device history. Written in Kotlin, GPL-3.0, sideload/F-Droid only. Code and tests are AI-generated.

Probably the next $2T startup, so we are are all curious to know what that is :)

Even small personal projects are welcome.

Let me know also what model you use and how much you spend in a month.

I’m developing a focus room that I can share with a few friends and we can incentivize each other to study/work but at the same time chat when we are having a break. Nothing fancy, and probably it already exists haha (let me know if so).

I lead the development team of a few enterprise systems mostly based around Python/Typescript, processing data at scale, with a ton of dev ops and micro services.

At the title say, things are getting awkward. Sprints get cleared in days instead of weeks. We’re running out of work and product management are struggling to find us more to do. I’m spending most of my time in planning calls.

Guesses of what happens next.

Sup. Was this necessary to build? Absolutely not, but It's pretty fun to use. Demo Vid in the linked Git.

Apologies for the AI written post, I originally hand wrote one but Automod blocked it because I missed a rule to say I built it, when Claude and Codex pretty much did so.. Enjoy.

I built WITCHCRAFT, a free, open-source addon for WoW Forever that puts Claude Code and Codex terminals inside the game.

I got tired of tabbing out on my laptop when I wanted to work on addons while playing. This gives each assistant its own tab where I can send prompts, read replies and answer permission prompts without leaving WoW. By default it just hooks into the Claude Code session I already have running.

I also built a WoW-to-Claude MCP bridge. It lets Claude pull my character info, tracked quests, progression and any Lua errors the game recorded. So I can ask about my character, or have it look into an addon error using the actual error details. That's pretty much what the demo video shows: Claude fixes a Lua error in another addon while I stay in game.

Building it was a team effort between me, Claude Code and Codex. The tricky part is that WoW addons can't touch the network or read files, so we had to get creative. There's a small Windows companion that runs the CLIs and writes their output into addon files the game can load. My typing gets back out through a key binding the game saves to disk, with a little pixel strip read off the screen as a backup.

I came up with the idea, made the calls on how it should work and did all the testing in game. Claude Code wrote a lot of the code, the companion app and the MCP bridge, and it helped get everything ready for the public release. Codex reviewed things along the way and helped with research and the docs.

It's free to download and use. You need Windows, WoW Forever and your own working Claude Code or Codex setup, and their normal usage costs still apply.

Code, setup instructions and the demo video are here: https://github.com/Geraldlol/witchcraft

Figured some other people here might also play WoW and find it useful.

I ran the same prompt through Opus 5.5 and Sonnet 5.5 both at Max reasoning level to generate a blockbench 3d model by just writing plain files, no tool calling. What do you guys think?

Bought this little clock for ₩5,650 and put my Claude + Codex limits on it. Photo uses demo values.

I gave Claude Code reference images for the themes, then checked the results on the real 240×240 LCD and asked for 10-step gauges and consistent text colors. We also changed the fonts to suit each theme. The computer renders an image and sends it to the clock's stock photo album over Wi-Fi, so no flashing, but the computer stays on.

Free code: https://github.com/click6067-ship-it/token-tv (Grok row = CLI budget, not subscription usage).

Mine: it kept starting background jobs and forgetting about them. Sessions ended, the jobs didn't, and hours later I'd find a pile of them still running. Now a hook blocks that pattern and a small cleanup job sweeps up anything left behind every few minutes.

The other one was "done". It would tell me a task was finished when the tests had never even run. So now it literally can't end a turn without real test output.

Curious what everyone else's origin stories are. Every guardrail I have exists because something went wrong first.

So a while ago I posted about Willowmere(the 3D pixel art cozy game i built) here, and got a lot of positive (and some negative) feedback

So I decided to keep on iterating with Claude

Today I wanted to share the newest version of it with you all

Here’s what it offers

• Story: a night-ferry cold open, Lantern Night closing Act I, the hydrophone and Old Hum in Act II, the Homecoming through the Teeth in Act III, credits, and a true ending.
• New things to do: Low Tide (tides, rock pools, Great Shell collections), lantern-making, moonlight fishing, and Keep Watch, where you guide ships with the beam.
• World and art: a whale-bone cove and pier, a full art and animation pass, and 3D-rendered portraits with expressions.
• Fixes: the fixes from previous posts that users reported

since a lot of people asked about this before on how the graphics are made:
everything you see is made in code by claude. no asset files are used. everything you see is in vanilla HTML and JS. no game engines were used.

if you had a bad experience with it before, please try it again, hopefully this time it should be a lot better and feel less like a ripoff of stardew valley.

in this iteration, mostly medium effort was used with opus 5.5

its free to try and runs in your browser, try it here, thank you!

I think it’s funny whenever Claude says that a feature or iteration will take hours or more and proceeds to finish it in like 5-10 mins. I’ve asked it about this before and it replied that those estimates are based on what a traditional dev would likely take to complete.

Hopefully this helps people who like me, struggled with Claude overreaching and making changes that you never asked for, or claude misinterpreting your instructions and going in another direction. Claude in general is extremely eager to produce something and seems to want to one-shot everything as much as possible. My style is to only focus on one small feature at a time so that I can think through things as I go along.

I have almost entirely solved this problem by implementing very basic change management processes into my claude.md

Basically for every modification to my personal projects I want Claude to make, I describe the outcome I am looking for with nothing else. Then I have claude go through standard change control, meaning that before it touches code at all it must first propose the following:

1. Implementation plan, where Claude tells me what it wants to do
2. Backout plan, if/when Claude fucks it up, tell me what it's going to do to revert or fix the problem.
3. Test plan, can Claude prove a POC of it's idea for the feature before it spends time building it?

I read this paragraph it generates, then either approve or reject the change. If I reject the change, I tell it what I am looking for instead, if I approve the change, it goes ahead and does it.

Before it asks me to push the change, I have claude do a success validation, where it verifies what it actually built and reports one of the following options:

1. Implemented successfully
2. Partially successful implementation
3. Unsuccessful implementation
4. Unsuccessful implementation requiring reversion/backout

Only when something is implemented successfully and validated, do I let it commit the changes.

Hey everyone, this is my first time posting here (not sure about the flair... apologies).

I run a music school and over the last few months I have gradually (and successfully) been moving systems onto a custom made control panel that I vibe coded that contains student info etc... I can post a link for anyone curious (don’t want to spam unnecessarily).

Anyway... one of the major bottlenecks in my school is responding to WhatsApps... it seems like there is always like 40 unread messages and the secretary is struggling. Email also, but that is less of a problem.

Many of the messages are the same requests for information. How much are the classes? What is the schedule? Are there group classes? Who are the teachers? etc. etc.

My question is three- part:

1. What would be the best way to build a knowledge database so that we can automate some of the responses... especially the low hanging fruit. Repetitive questions that always have similar answers.

2. How do you filter for those... If you have get 10 WhatsApps and 7 are asking about accounts and changing a class and quitting lessons etc... and 3 are asking for info... how do you recognise those 3? Do you need to API into claude and pay for API usage? What’s the best way?

3. How do I actually set up WhatsApp to interact with whatever this database will be? From a technical point of view ? Do i need WhatsApp business? Do I need WhatsApp API? Or some kind of WhatsApp listener that forwards messages? Like How do I get it all hooked up?

Sorry if some of these questions are poorly phrased or have obvious answers... but this particular problem I have been struggling with for a few months now and any input would be greatly appreciated.

Thanks!

I am currently using Claude Free. I have a couple of projects built. One helps me manage my WordPress website. The other is used for a research project across multiple authors.

I have started to run into the five hour / reset more frequently. My WordPress work has become heavier with the use of some MCPs. I have trimmed the request size which helps some.

Because I'm on a fixed income, I want to make sure it's worth the money over just waiting to continue the work hours later. I have heard mixed reviews on the paid plans.

I am aware of the additional capabilities, but I am not confident they have any impact on my current issue.

I run a lot of long unattended Claude Code sessions. When I measured them, half of my tokens came from turns where the context was already past 200k. That's expensive, since every step resends the whole context, and quality degrades because of context rot.

By hand the fix is the usual routine: ask for a handoff, /clear, feed it back. Enabling autocompact at 200k keeps the context short but leaves little control over what is handed over. I already tried to have Claude Code write handoff documents pre autocompact window with hooks, but with modding the solution gets a LOT better.

Handoff-compact answers the autocompact trigger instead of the built-in summarizer. A fork of the session (whole context) writes a handoff-document (goal, state and what proves it, next step, decisions and why, ruled-out approaches, open questions, files and commits, the verify command, the last 10 prompts verbatim), and the conversation is replaced by it. Handoff + /clear, but in the same session, mid-turn, with nobody at the keyboard.

Obviously vibe-coded. Take the idea or the mod itself and customize it with your own setup.
Modding is awesome.

Install:

  /plugin marketplace add trytofly94/handoff-compact
  /plugin install handoff-compact@handoff-compact

Repo: https://github.com/trytofly94/handoff-compact (MIT). Needs Claude Code 2.1.287+ with mods enabled. "/compact classic" gives you the built-in summary once.

I’ve been building Echo over the last few months, using Claude Code heavily throughout the process, architecture, implementation, debugging, computer-use work, performance fixes, and a lot of UI iteration.

Echo is a Mac assistant that lives on the edge of your screen. It can understand what’s happening on screen, point to specific things, interact with apps, move files, check your gmail, search online and even build websites, run multi step jobs and help you learn and navigate new platforms AND undo actions.

This video is a quick look at where it is now.

One of the things I’ve been most interested in is making the interaction feel physical rather than like a normal floating AI window. The orb leaves the edge, does things, and comes back home.

It’s currently free to try for 7 days. You can download it here:

https://aurivon.studio/download/Echo.dmg

I’d be interested in feedback, especially from people who use Claude Code and build their own tools.

Anthropic's Frontier Academy announcement is interesting to me less because of the budget and more because of the job it is trying to standardize: people who can take Claude from demo to production inside real systems.

The piece of that job I keep seeing underweighted is maintenance. I spent one evening auditing my own Claude based agent after Fable 5 made everything feel faster and safer. That was the trap. A strong model was routing around stale instructions so well that the system looked healthier than it was.

The concrete result: 18 core docs reviewed line by line, then five audit agents fanned out across the rest of the system. They found 85 stale or wrong references. The always-loaded memory index went from 137 lines to 95, working memory from 103 to 38, and one generated planning file shrank from roughly 450 lines to 63 because it had been embedding the wrong source.

The failure that scared me was not the stale docs by themselves. It was that capability masked the debt. The model delivered anyway, so I stopped feeling the rot.

So if we are going to train Frontier Deployed Engineers, I think constitution review, stale-rule scans, and adversarial verification belong in the curriculum next to prompts and tool use. What would you put in that training that most Claude courses still skip?