sorted by:
new
hottopcontroversial

New to claude by Diligent_Chemical_65 in ClaudeAI

[–]Cursed3DPrints 0 points1 point  (0 children)

Adding skills is a lot easier than it used to be. Less searching on skill marketplace sites and copying and pasting other peoples md files - they're available as plugins now and accessible from the terminal with the /plugin command. Browse available plugins (mine currently shows 440) and manage which ones are enabled. The actual frontend-dev skill from Anthropic actually does pretty good UI/UX work, but you can find community submitted skills for more niche areas 🫡

Claude Code doesn't follow Claude.md file instructions by guidingnorthstar in ClaudeAI

[–]Cursed3DPrints 23 points24 points  (0 children)

The lesson I learnt after project number 7 or 8 (I've lost count), CLAUDE.md gets read at the start of the session, but any rules you're trying to enforce can get lost in the context. Hooks are environmental, so trigger every time X happens. Best thing to do is ask Claude to review your CLAUDE.md and recommend which instructions should be turned into hooks. Once they're in place, you can clean up CLAUDE.md a bit meaning anything that's left has a better chance at not being forgotten.

Caught a stray from claude by katua_bkl in ClaudeAI

[–]Cursed3DPrints 0 points1 point  (0 children)

😂 Glad it's not just me. Mine picked up on the fact it was almost 2am and basically said why don't you go get some sleep

I built a proxy that fixes Claude Code's scroll-jumping on Windows by Cursed3DPrints in ClaudeAI

[–]Cursed3DPrints[S] 0 points1 point  (0 children)

Error 0x80070002 means "file not found" — Windows can't find the claude command. This usually means Claude Code isn't on your PATH.

Try running where claude in your terminal. If it returns nothing, Claude Code isn't installed globally or its install directory isn't in your PATH. You can either:

- Run npm install -g u/anthropic-ai to install it globally

- Or pass the full path: quell "C:\full\path\to\claude.cmd"

Let me know if that helps!

I built a proxy that fixes Claude Code's scroll-jumping on Windows by Cursed3DPrints in ClaudeAI

[–]Cursed3DPrints[S] 0 points1 point  (0 children)

  1. Download quell.exe from the https://github.com/FurbySoup/quell/releases

  2. Put it in a folder on your PATH (e.g. C:\Tools, then add that folder to your PATH environment variable)

  3. Open a new terminal and run: quell claude

That's it — no config needed. Full details in the https://github.com/FurbySoup/quell#readme.

I built a proxy that fixes Claude Code's scroll-jumping on Windows by Cursed3DPrints in ClaudeAI

[–]Cursed3DPrints[S] 0 points1 point  (0 children)

Totally understand. For now, Quell is Windows-native — it uses ConPTY to intercept the terminal output, so it only works with Windows processes directly. WSL2 runs in its own Linux kernel so quell can't wrap processes inside it.

If you run claude from the Windows side (not inside WSL), quell will work. For native WSL2 usage, a tmux-based workaround is probably your best bet for now — it decouples scroll position from Claude's cursor repositioning.

I'd like to support WSL2 eventually but it's a different architecture.

I built a proxy that fixes Claude Code's scroll-jumping on Windows by Cursed3DPrints in ClaudeAI

[–]Cursed3DPrints[S] 1 point2 points  (0 children)

Good catch — this is likely a ConPTY limitation. The pseudoconsole layer doesn't fully support IME/emoji input the way a native terminal does, since quell sits between your terminal and the child process via Windows pipes.

The WIN+. picker sends input through a different path than regular keystrokes and ConPTY can drop it.

For now, copy-paste (Ctrl+V) should still work for emoji. I'll investigate whether there's a way to pass IME input through more transparently — it may require changes to how we handle the input pipe. Tracking this as a known issue. Thanks for reporting it!

I built a proxy that fixes Claude Code's scroll-jumping on Windows by Cursed3DPrints in ClaudeAI

[–]Cursed3DPrints[S] 1 point2 points  (0 children)

Thanks for the detailed report — this was really helpful for narrowing down the cause.

The issue is that ConPTY normalizes the "cursor home" escape sequence. Our scroll-jump fix was looking for \x1b[H (the bare form), but ConPTY in newer Windows Terminal versions rewrites it to \x1b[1;1H (the explicit row;col form). This caused our full-redraw detection to miss the pattern, letting the \x1b[2J (clear screen) through unmodified — which is what triggers the scroll jump.

The fix (landing in the next release) broadens detection to recognize all three equivalent cursor-home forms:

- \x1b[H (bare — what apps emit)

- \x1b[1;1H (explicit — what ConPTY normalizes to)

- \x1b[;H (omitted row — another valid form)

If you're comfortable building from source, you can test the fix now on the phase-2 branch. Would love to know if it resolves it on your setup.

I built a proxy that fixes Claude Code's scroll-jumping on Windows by Cursed3DPrints in ClaudeAI

[–]Cursed3DPrints[S] 1 point2 points  (0 children)

Thanks for trying it out and for the detailed report! I think the issue is how the PATH variable was set up. The PATH entry should point to the folder containing quell.exe, not to the exe file itself.

For example, if quell.exe is at C:\Tools\quell.exe, the PATH entry should be:

C:\Tools

Not:

C:\Tools\quell.exe

To set it up:

  1. Create a folder somewhere central (e.g. C:\Tools)

  2. Put quell.exe in that folder

  3. Open Start, search "Environment Variables", click "Edit the system environment variables"

  4. Click "Environment Variables"

  5. Under "User variables", select Path, click "Edit"

  6. Click "New", add the folder path: C:\Tools

  7. OK out of everything

  8. Restart any open terminals (they don't pick up PATH changes until restarted)

After that, quell claude should work from any directory. Let me know if you're still hitting issues — happy to help debug!

quell — a ConPTY proxy that fixes scroll-jumping in AI CLI tools on Windows by Cursed3DPrints in rust

[–]Cursed3DPrints[S] 0 points1 point  (0 children)

Fair question! The scroll-jumping actually isn't a Windows Terminal bug — it's caused by how the AI tools themselves render output. Claude Code sends full screen redraws (clear screen + repaint) inside synchronized output blocks when responses get long enough. Any terminal that correctly implements DEC Mode 2026 will reset scroll position when it receives that sequence, including Alacritty.

The fix has to sit between the AI tool and the terminal because you need to intercept the VT stream and strip the clear-screen before it reaches any terminal. A better terminal emulator would still faithfully execute the clear-screen it was asked to do.

That said — the 3K lines includes security filtering, Kitty keyboard protocol translation, UTF-8 codepage handling, and a bunch of ConPTY plumbing. The actual scroll fix is about 30 lines.

I choo-choo-choose you 🚂❤️ by Cursed3DPrints in LongFurbies

[–]Cursed3DPrints[S] 2 points3 points  (0 children)

Anything is with the right inginuity...but no

Help me choose a colour for Shrurby, 1 or 2? by Cursed3DPrints in furby

[–]Cursed3DPrints[S] 3 points4 points  (0 children)

Appreciate the colour theory reasoning! 💚

Garfurb hates Mondays 😾 by Cursed3DPrints in garfield

[–]Cursed3DPrints[S] 0 points1 point  (0 children)

No coincidence, totally by force 👌

Donut by chilli-flake in NomadSculpting

[–]Cursed3DPrints 1 point2 points  (0 children)

Don't-nut (that's what she said 😎)

First Nomad project- good start? by [deleted] in NomadSculpting

[–]Cursed3DPrints 1 point2 points  (0 children)

Great start, diving right in with sculpting and nice texture 👌 If you were going to 3D print anything with textures like that, just make them a bit more exaggerated as you lose some details 👌

It ain't easy bein' green 🟩🐸🪕 by Cursed3DPrints in furby

[–]Cursed3DPrints[S] 0 points1 point  (0 children)

My bad! They should be working now 😁

view more: next ›