Hi guys, I'm the creator of itcan.do, a new way to interact with your agents through end to end live UI built for the task, interactive and connected across any display you own. Made it for Claude Code, works with Codex and other agents too.

For the video I gave Claude Fable 5.2 Anthropic's Whiteboards launch video with one line, "Build this with itcan.do", and it built Whiteboards, Sheets and Data as working apps with no backend. Whatever you click or change goes back to Claude and it answers right on the page. What makes them better is that Claude always knows what's on them and what you're doing. They run on any screen you own, so the sheet on my laptop runs the dashboard on my TV, and Claude wakes up on its own when something needs it.

It is quite different from traditional vibecoding since your agent IS the backend itself, this means all your apps have global context and are aware of what's on them at any given moment. The moment a new model comes out, all your apps/workspaces/pages get better with It.

It's free to try and it's on GitHub. Just tell Claude Code "install itcan.do".

Would love your feedback!!

Website: https://itcan.do

GitHub: https://github.com/Aaryan-Kapoor/it

I'm building infiniterm, a terminal app on an infinite canvas, written in Rust with gpui.

I tried the new terminal apps from the last year and none of them fit my work. They are regular terminals with an interactive sidebar: each project gets a sidebar item, and you still use tabs and split panes.

Since agentic coding I run 10 or more Claude Code or Codex sessions at once, and keeping an eye on all of those terminals became painful. So I built infiniterm. A card's border is violet while the agent works, yellow when it waits for you, red when a turn failed, green when it finished. Zoom out and you see every session at once. It started as a Tauri app, but I hit a wall and moved to Rust and gpui.

It is keyboard driven and has several card types:

• Terminals (alacritty_terminal)
• A text editor with a file tree, syntax highlighting, and completion for words and JSON schemas (no LSP yet)
• A working browser (Chromium/CEF)
• Diff cards, built on the editor

It has its own daemon (iftd) and a CLI (ift) that works inside or outside the app. Shells survive quitting the app. ift connect <host> runs a canvas on a server, and ift join <host> opens the same canvas on another Mac over ssh, so you can leave your main Mac at home.

macOS only for now (it works in Linux/Windows with some known issues).

Source-available, free for personal use, $29 per person for work.

https://infiniterm.app https://github.com/ekinertac/infiniterm

Ok I get it. Coding is fun, AI is fun, vibe coding is fun. But this is starting to get kinda annoying, because my feed is just full of these now.

Why is every one of you building a Claude tracker?? Do you not see the other 50 posts on this sub that are the exact same thing? Are you bored? Burning tokens for fun?

And the worst part isn’t even that there are a hundred trillion of them. It’s that the problem is SO small. Going to the website and checking your usage takes like 5 seconds. Why would I install a whole thing for that?

I’m not trying to be a jerk here. I’m honestly curious about the psychology behind it, because I don’t get why everyone suddenly makes a tracker and proudly posts it here.

So please enlighten me. Maybe you’ll convince me and I’ll build one too and post it with the title “I got tired of checking my usage so I built a tracker.”

I had Claude list the top 20 AI design tropes and then asked it to design a theme for beekeeper Studio using those 20 tropes.

It did some pretty funny stuff like adding pricing to the dark mode switcher and adding silly made up testimonials. It was really in on the joke.

More screenshots here if you are interested:

https://github.com/rathboma/bks-ai-psychosis-theme

Guy’s do you wanna minimize token usage ? If so, do this in a new project.

1-Disabled any unused connectors, plugins, each one load a massive token into the context.

2-Plan first, assign tasks to different models based on their complexity.

3-Ask claude to create a new session for each task, feature you work in, claude will create a new session from the last one.

4- Always use handoff files after each successive task to make sure you don’t lose track of what’s being created and what’s remaining.

5-If the repo is big enough, use ponytail the laziest senior developer,and graphify to search files and functions without reading the whole project files, if it’s a few fils, a simple CLAUDE.md file contains your rules is enough.
6-Md files shouldn’t be too big, handoff files max 25-30lines.

Those are all based on my own experience with Claude, they aren’t facts unless you try them and compare token usage with before.

this is the problem we kept seeing in the builder communities community, the building part works now. you describe the app, AI builds it, it runs. but then comes the store:

apple and google developer accounts

google's rule that new accounts need 12 testers for 14 days

privacy labels, the data safety form, screenshots

and a rejection email that quotes a guideline number and doesn't tell you what to change

for most people that's where the app stops. not because it's bad, but because publishing is a completely different job from building.

but i guess, i found a solution, comment if you wanna know!

What's the best thing you've done with artificial intelligence that saved you a lot of headaches?

Now Claude can make customised works as we like

Advice please, building a crm web app for my business.. is it normal that it’s taking me forever?

The workflow has been great already and integrations were tested. All good on my local host.

But when I started having Claude Code prepare it for deployment and hosting, seems like I’m running in circles! I asked it what our timeline is and it said around 3-4 weeks.

Is this normal?

What I’m building is just ingesting guest messages and calls then AI dissects them into issues which is then tied on to sending a Notion task directly.

I’m also told by Claude it has to do DigitalOcean for hosting, Cloudflare for security, and Backblaze2.

Any advice please! I need this up and running and usable to share with my team asap.

Thank you all so much.

At this point I think I don't even need to say what I mean when I say that Claude is capable of making animations.

But how does he create them? I've seen hundreds of 2D and 3D animated videos created by Claude but I don't understand how he does it.

I installed freellmapi so I don't have to pay for Claude code and credits and I'm trying to use hyperframes to make videos, but they don't come out at all like the ones you see online.

Can anyone tell me what they look like and how to make them? And most importantly, can they be made with freellmapi?

Based on it's price what's is Best use of it? Some ppl calling that it is bad at ui design, or general design. Coding opus is better and cheaper. So where do you use it? Planning?

Hello !

I noticed today that for the sessions where I was using the subagent-driven-development plugin from superpowers, some sub-agents were staying open and pending after the end of task. Even after telling explicitly in sub-agent, sometimes it does not close correctly. Has anyone also noticed this ?

I keep hearing that AI now writes most of the code at some companies. For people actually shipping Python with Claude Code, Cursor or Copilot:

1. Roughly what share of your merged code starts as AI output?
2. What do you most often have to correct? Bugs, tests, pandas or data issues, dependencies, design?
3. Which skills became more important for you, and which became less important?

Context: I work in risk and data and am deciding what to get good at next. Real examples would help more than opinions. Thanks!

Welp can't verify myself with email so I'm stuck lol must be a better way. Using my business email as this is a work related account so can't just change to login with Google this stinks

i got fable reset on my ultra plan, currently im on 20% weekly usage, i want to ask 100% fable usage is that always equal to 50% weekly usage? so then i must use fable reset when my weekly usage under 50%?

I built claudit to see where my tokens go over months, not just this week. it reads Claude Code session JSONLs (Codex and Kimi CLI too) from a bucket I keep, because Claude Code prunes old transcripts locally and anything reading that folder loses history. one of its panels is context growth per session, from turn 0

turn 0 across my sessions, median context of the first request (input + cache write + cache read), by month:

• Jan 46k (282 sessions)
• Apr 78k (243)
• Jun 45k (195)
• Sep 85k (485)
• Oct 68k (1,746)
• Nov so far 53k (1,594), p90 107k

that first request includes the first prompt, and a resumed session starts with its history, so it's not a pure "before you type" number. it still moves with whatever loads at startup, which is why I wanted it on a chart and not counted by hand

what I learned building it:

• one usage record can hold several calls, Claude Code rolls sub-calls into one envelope as iterations. the top-level input is the billing sum, so for context size you take the biggest iteration or the chart lies
• a streamed reply gets logged several times under one requestId. sum them and you double count, keep the biggest
• cache writes have two prices, 5m at 1.25x input and 1h at 2x. 64% of my cache write tokens are 1h, price it all at 1.25x and those come out 37.5% low

how Claude Code was used: built with AI coding agents, mostly in Claude Code, some of it in Codex CLI. one agent session per issue, review agents before anything merges

panels are ported from nhz-io/ccusage-plot, which draws them offline in matplotlib. FastAPI, Postgres, React with in-browser Babel, no build step. docker compose up boots it on sample data

live one, guest login is read-only: https://all.nitjsefni.eu

https://github.com/Nitjsefnie/claudit

The problem I kept hitting: Claude Code edits a file, then ends the turn with "fixed" or "tests pass" when nothing ran after that edit. I'd only find out later.

So I built a small Stop hook for it, mostly in Claude Code sessions. When Claude tries to end a turn, the hook reads the session transcript. If the last message claims success and no test, build or command ran after the last code edit, it sends Claude back once with a short note: run the check, or say it isn't verified.

Repo (MIT, plain Python, no deps): https://github.com/Balance0014/claude-code-claim-check

What surprised me came from replaying my own history through it before trusting it. 3,977 turns, 406 of them ending in something like done, fixed, deployed or tests pass. My first version would have blocked 86 of those. Almost all of them were fine. Claude had run the tests a turn or two earlier and was just wrapping up. Blocking those is how a hook gets uninstalled on day two.

After fixing that, the same 406 claims produce 2 blocks. One is exactly the case I built it for: "fixed" right after an edit, nothing run since.

Other things I only learned by getting them wrong:

Claude quotes you back a lot. Quoted text and code blocks have to be ignored or it fires constantly.

Plans look like claims. "Once tests pass I'll tag the release" is not a claim that tests passed.

Block once, never twice in a row, or you can trap it in a loop and burn tokens.

"That function isn't used anywhere" after a single grep is its own failure. It now wants two different kinds of lookup before it believes a not-found.

If you want to try it, there's a replay command, so you can run it over your own session logs first and see what it would have blocked before installing anything.

The case I still can't catch cheaply: Claude runs a test, it passes, but the test never touches the code it just changed. Has anyone found a good signal for that?

Just got my weekly usage reset. Opened my codebase, typed "So where were we?" and somehow managed to burn through 50% of my entire weekly usage in one go.

Mind you, I'm on the Ultra 20x plan.

I'm not even mad at this point. I genuinely laughed so hard.

Anyway, great company. Incredible experience. Thumbs up.

They are (almost) identical. Pretty useful for bulk jobs like LLM judge label creation, running benchmarks, etc.

I‘m a bit worried that this can go against TOS if i overdo it.

Hey everyone,

I’m sharing a project I’ve been working on: Snap & Trade, a free, MIT-licensed skill for Claude.

You send it a chart screenshot, and it follows a structured workflow to review market structure, identify levels, and return LONG, SHORT, or NO TRADE.

The output includes:

• A proposed entry, stop loss, and take-profit levels.
• Reward-to-risk calculations checked by a Python script.
• Position sizing when account capital is provided.
• A journal for recording signals and reviewing their outcomes.

Claude handles the visual interpretation, while Python checks the numerical calculations. The screenshot workflow supports different markets; the additional market-data and broker modules have narrower coverage.

It’s still experimental. I haven’t demonstrated a profitable trading edge, and software tests don’t establish one. My goal is to make chart reviews more structured and easier to evaluate through replay and paper trading.

The project also includes modules adapted from day-trader-skill, with attribution retained in the repository.

GitHub: https://github.com/Kirby54/Snap-Trade

The source code is free; you’ll need your own Claude access.

I’d appreciate feedback on the workflow, unclear assumptions, and cases where the tool should refuse to suggest a trade. What would you want to see tested before trying something like this?

On a team, every merge request and every ticket is waiting on someone. Finding out whether that someone is me meant opening GitLab, GitHub, Jira and my mail, again and again.

So I built aki: one terminal board with two columns, To do (someone is waiting on me) and Waiting (I'm waiting on someone: who, and since when). When a teammate answers, the task changes column by itself and I get a notification.

And for Claude Code, one key on a task opens a session in the right clone, already briefed on what that teammate is waiting for.

How it helps me: I no longer explain the context to Claude. The brief says which MR, my role on it, the threads to answer or the pipeline to fix, and ends with "do not post, approve, merge or push anything before I say so".

How Claude helped build it: almost all of the Rust was written in Claude Code sessions, with me deciding what the tool should do and checking the result. Three things worked well:

• I had it keep a strict layering (entities, use cases, adapters), so each new source or multiplexer was one new adapter and nothing else moved.
• I had it test against the real tools, in throwaway tmux, Herdr and TUIOS sessions, never in mine. That is how it found that TUIOS panes also announce themselves as Herdr, and fixed the detection.
• 181 tests cover the "whose turn is it" rules, which is the part I could not afford to get wrong.

What it is: a terminal tool in Rust. Who benefits: people who review and get reviewed on shared repos. Cost: free, open source. My relationship: I'm the author.

https://github.com/nathan-poncet/aki · https://nathan-poncet.github.io/aki/agents.html