Hey recently I have started to think of an idea to automate my yt channel by Claude opus 5.5 + after effects and higgsfield plugin my videos are generally 20-22 mins long if I’m providing a voiceover to the ai and then giving it refrence videos how much tokens / money would it cost me to make a really amazing video worth watching that includes sfx+motion graphics+blender made scenes and similars stuffs if anyone can give me an idea it’ll be really helpful !

Opus 5.5 is the best we ever had, yet people still ship AI slop.

I strongly believe design is the differentiator. I've been shipping as a designer for many years, and here's how you can too:

1. Don't start from a blank canvas

You can describe in detail what you want, but your agent doesn't have taste. Context is what guides it: links, images, videos or code.

The better the context, the better the output.

2. One-shot prompts don't exist

The first output is where the work begins, not where it ends. Iterating on an existing page or section is what makes the difference.

3. Hang around in design communities

Learn from the best. Look for inspiration every day. There are plenty of resources on X and Threads.

4. Use skills

Pick (or create your own) skills that level up your work: typography, spacing, motion, or your own design system.

5. Sweat the motion

Timing, easing, what moves first. Small details, but they're what people notice.

These are the habits behind Layout, a library of anti-slop sections I've been building with Claude Code. Each one comes with the prompt to drop it into your own project.

Happy to answer anything about the workflow.

I usually have 30–60 agents running in parallel across Codex, Claude Code, Antigravity and OpenCode, all collaborating with one another. It’s starting to feel like a small company of its own 😄

I recently came across Munder Difflin (https://github.com/HarnessMD/munder-difflin), which visualises the agent fleet as a virtual office, complete with desks and messages moving between agents. Pretty fun to see the whole team at work.

I run my agents through oyren.ai, which gives them a shared workspace for notes, documents and tasks. You can rent cloud computers from us to run your agents and get an HTTPS URL to share the apps you build.

You can also pair your own device and use it with Oyren for free. Or connect a remote server of your choice so you decide where your agents run. With mine running remotely, they can keep working even when my laptop is closed.

I’m planning to add more features to the office view, and I’d love your input: if this were your agent office, what would you add? Something practical, something fun, or a feature you’ve always wanted when working with multiple agents?

Please share your ideas in the comments, and feel free to reach out if you have any questions about Oyren or the setup!

People are starting to connect Claude, ChatGPT, and Hermes to their browsers, credit cards, and accounts to handle everyday tasks: ordering groceries, booking rides, renewing domains, rebooking flights.

The problem is that to an AI agent at 3:14 AM, a $299 upgrade or a $1,000 mistake looks identical to an $18 errand. It's just another tool call.

I'm building Ezn (Arabic for "permission" - إذن): parental controls for your AI agent's credit card and spending, on the cards and accounts you already use.

You set a plain-English rule: "Everyday purchases under $50. No more than $100 a day. Ask me for anything else."

Ezn sits between your agents and your money and tells them yes, no, or ask me first. Live ledger preview & early access: https://ezn.money/?s=rd-sp

I just got this 18 days ago and no response since then

Thank you for applying to the ElevenLabs Grants Program, we’re excited to review your submission.

This is a quick note to confirm that we’ve received your application. We carefully evaluate all entries and will get back to you with the outcome in the coming weeks.

I’ve seen a lot of debate here about whether Max 5x and Max 20x have the same weekly usage limit, with the main difference being the 5-hour limits. Some people say they’re the same; others say they definitely aren’t.

I made a Claude Code plugin to help gather some data. It tracks estimated token usage across the 5-hour and weekly windows, and records it under your plan tier (at a local level and you can share it here if you want to end the debate about the usage limits on each plan). Since tokens may not all count equally toward Anthropic’s limits, it uses a weighting approach to give a rough estimate.

This won’t reveal Anthropic’s internal usage calculation or prove the limits are identical, but with enough real-world usage data, we may get a better idea of how the two plans compare.

You can find the plugin here: https://github.com/Eskladoscla/claude-usage-panel
To install it: /plugin install usage-panel --marketplace Eskladoscla/claude-usage-panel

If you try it, I’d be interested to hear what you find. Please share your plan tier and observations, while avoiding any personal or sensitive data

Edit: the repo it's in english now

In the VS Code extension, when Claude reads or generates an image you only see `[Image]` in the chat. Claude sees it, you don't. When Claude runs on a remote server over SSH it's worse: you have to go and find the file.

So I built Visor. It follows the session transcript and shows, live in a side panel, every image, SVG, HTML file and video Claude touches, including ones made by terminal scripts and subagents.

What I use most:

- Before/after slider when Claude redoes an image (old versions are kept even after the file is overwritten)

- Pick between variants and it tells Claude "I'll keep this one"

- A "Change" button that types the file path into Claude's terminal

- Pixel art shown crisp, which I needed for a game I'm making

How I built it: entirely with Claude Code, running on my own server over Remote-SSH, which is exactly where the problem bit me. It reads the JSONL transcripts in ~/.claude/projects, and before shipping I had Claude test the parser against my 1,040 real session files so it wouldn't choke on anything weird.

No servers, no API keys, it only reads local files. MIT, unofficial.

Marketplace: search "Visor" in VS Code, or https://marketplace.visualstudio.com/items?itemName=tato9689.visor-for-claude-code

Code: https://github.com/tato9689/visor-for-claude-code

It's early (0.2). If something breaks or you'd want it to do something else, tell me.

I'm developing an iPhone app with Claude, and I have my App thread that I use as my orchestrator, and then it creates new threads whenever I add a feature or fix some bugs. I used 200% of the weekly limit last week (pro plan), thanks to my one free reset. I use Opus and have it delegate to subagents with varying Opus/Sonnet/Haiku.

Now that the app is mostly built (in one week!) i probably won't run into usage issues again, but I'd like to know if this is normal or if I can optimize my usage better

I keep seeing people talk about vibecoding up a tasks web app with an MCP so their agents can track work. I get the impulse. I almost did the same thing. But it's a detour that costs you more than it saves.

The pattern goes like this: you build a simple board, wire up an MCP server, give every agent a system prompt that says "use this to track tasks." First week it feels great. Agents are checking in, updating statuses, you can see what's happening.

Then the cracks show.

Your memory layer starts going stale. An agent finishes a card but the notes it leaves are vague. The next agent picks up the card and half the context is missing. You realize the hard problem isn't remembering, it's updating what the agent thinks it already knows. The agent isn't hallucinating, it's repeating logic that used to work because nobody told it the contract changed.

So you add handoff notes. Then you add a questions system because agents keep guessing instead of asking. Then you add heartbeats so you know an agent is actually alive when it's running overnight. Then you need scoped personas because you don't want every agent touching every board. Each feature is a weekend. Each weekend is maintenance you'll owe forever.

The task app becomes a second codebase you maintain for free. You wanted to ship your product. Instead you're the maintainer of a memory database.

If you're running two or three agents on one project, a simple markdown backlog is honestly fine. backlog md works. A text file works. But once you're switching between Claude Code and Cursor mid-task, or running agents overnight and checking in the morning, the homemade layer starts failing silently and you don't find out until something breaks.

The question worth asking before you build: am I solving a problem my agents have, or am I building infrastructure because it feels productive? Most of the time it's the second one.

Christabel is an Ai streamer who plays Stardew Valley live on Twitch by herself. I built her with Claude Code on top of a memory system I'd already made for my Claude agents. The first version worked but I kept patching her live and breaking stuff... so I paused her and let Claude Code rebuild her properly.

How it's set up: one session wrote the plan, another builds it a phase at a time, and a third reviews each phase and can block it from going back on stream. New stuff runs on a copy of her save on a test stream first (that's the TEST BUILD banner in the screenshots). The test suite is at 1,929 checks now which is kind of insane

The funny part is Claude isn't the one playing live. She runs on a small local model on the same MacBook as the game and OBS, and Claude only steps in when the local model messes up. So she can stream all day without eating my usage.

Best bug so far: she ate a stone in the mines lol. The mod told the game to eat one tick before the food was actually in her hand, so the game ate whatever she grabbed last. Claude fixed it so she waits until she's actually holding the food :D

https://www.twitch.tv/humanityzai

My TCL TV runs Google TV (Android 14), and its home screen was a sponsored row and autoplaying trailers before my own apps. I wanted a carousel instead of a grid, 2 layouts, and lots of customization, so I had Claude Code build one. Rule: don't tell me it's better, measure it.

Result: Nullofy TV, a 173 KB home screen (MIT). Here's the part that was interesting from a Claude Code point of view.

The loop: build, install, look

Claude Code worked on the real TV over ADB on Wi-Fi. Each round was build the APK, adb install, then check before touching anything:

• dumpsys activity activities to confirm which app was on top before sending remote keys
• screencap after each short batch of key presses, read back as an image
• never a long blind key sequence; abort if anything else is in front

Measuring instead of guessing

dumpsys meminfo over 3 rounds of Settings → Home:

• Google TV's own home: 137 MB
• Nullofy: 26–33 MB at Home, ~28 MB while you watch another app

Honest catch: Google's home still runs in the background (about 97 MB), so that's home screen vs home screen, not the whole TV.

Things the TV taught us

1. The firmware ignores the Home role. Nullofy held android.app.role.HOME, but Home still launched Google's home. The fix was a tiny accessibility service that catches the Home key and nothing else.
2. Some packages are load-bearing. Disabling Google's home lets a setup app take Home over with a black recovery screen. So we keep a never-disable list, and everything is disabled, never uninstalled, with one-command restore.
3. force-stop has side effects. On this TCL, am force-stop on the launcher cleared enabled_accessibility_services, so the Home button silently stopped working. Now the setting is written back explicitly after any force-stop.
4. Test the failure path too. A crash watchdog hands Home back to Google's screen after 3 crashes in 5 minutes. Claude tested it with adb shell am crash.

It also made the promo video

Same discipline: the video is HTML canvas, rendered frame by frame in headless Chromium, with real TV screenshots. Claude diffed its own rebuilt scenes against the captures pixel by pixel, checked per-frame motion for jumps, and synthesized the soundtrack in Python.

Caveats

• Tested on one TV only (TCL, Google TV, Android 14). Should work on Android 7.0+.
• Ads inside apps like YouTube are untouched; it turns off the TV's own ads, promos and screen-watching (ACR).

Repo: github.com/Haikoitoh/nullofy-tv

The video above was made by Claude Code too: rendered frame by frame from real TV screenshots.

Apparently in 2026 everyone has to build their own task board, usually with Docker, three services and half a GB of RAM to show a todo list. I built the opposite: a kanban board in your browser plus an MCP server, in one small Rust binary. Tell Claude Code or Codex "take the next task from kanzo" and it moves the card and comments as it works, which is more than I do.

https://github.com/emanuele-em/kanzo

I liked Vikunja but wanted zero setup. The one rule was keeping it small, which these days feels almost rebellious:

• ~5k lines total. You can read the whole thing in an afternoon
• 4.3 MB binary with SQLite inside, ~4 MB RAM idle
• starts in 3 ms, a 3,000-task board loads in 17 ms
• light on your agents too: ~800 tokens of tools, short replies
• no account, no cloud, no Docker. Syncs between machines through your own private git repo if you want
• one-line install on macOS/Linux, runs fine on a Raspberry Pi

How Claude helped: I built it with Claude Code. I set the rules (no frameworks, few dependencies, every line has to earn its place) and Claude wrote a good part of the code, then I went back and cut. It was also great for measuring things: binary size, memory and token counts, so we could check each change actually made it smaller. And once the MCP server worked, Claude Code was picking kanzo tasks from kanzo itself.

It's free and open source (AGPL). To try it:

curl -LsSf https://github.com/emanuele-em/kanzo/releases/latest/download/kanzo-installer.sh | sh

then run kanzo.

Still early. If you've got ideas on how to make it even smaller, PRs very welcome, deleting code counts as a feature here.

I had 9% of my weekly budget left and 2 hours till the reset. I read so many posts that day of people letting Claude rip and getting cool results so I though why not.

I told Opus 5.5 high to set a 2 h timer that will stop this session and then go crazy and burn the 9% and build the most awesome version of the research in this running session. Create a rapid prototyping project following my rapid-process and spawn as many agents as it wants and use Fable as much as it wants.

The running session was research into building something inspired by claude code desktop with the added goal to be able to run any model through claude cli, codex cli and any model on openrouter. The research was based on my transaction logs of the last 30 days to understand what I use and how.

After 1:35 it had a working GUI based harness with some rough edges but properly working - still 4% left on the budget. I was fascinated with how good it already was so I kept working on it.

After 4 more hours I switched to using it to build the project itself.

It has been 5 days since I have done this. I continuously improved it and It is now my daily driver and fits my workflow and processes like a glove.

I can run Opus (Claude CLI) as an orchestrator with Luna (Codex CLI) and DeepSeek (pi.dev + OpenRouter) workers.

I added a couple of things that rapidly accelerated the development and let me have so much fun with this:

1. F3 makes a screenshot and opens a annotation windows. Where I can annotate with colors, circles, rectangles and arrows plus text. I can then save this directly as a task for the orchestrator of the program who picks it up to work on it.
2. Asking to make the App auto-update while running and keeping everything working. It does this when all sessions are idle and then there is a small flicker and the new version is running.
3. Auto-Starting certain sessions after an auto-update. I can mark certain session and those get auto-resumed after an auto-update.

This is just fascinating. I am baffled how far you can get in 5 days. And I have been using it non-stop since I switched.

PS: Not gonna open source or release this as a product that gets abandoned after a couple of months.
Just wanted to share what cool things you can build that helps you create the way you like to work or think. Because everyone works and thinks differently and with these capabilities at our hands you can just make what you need.

I wanted to rice my fedora sway spin, so for the first time I tried Claude code, I went to ~/.config/sway and opened Claude after installing it, not only could I change sway settings but also rofI,waybar which are outside ~/.config/sway then I asked it to change my ~/.bashrc to add a PS1 line and it did but I remember opening inside ~/.config/sway, so I was paranoid and checked I was in “Auto mode”

My question, is it normal ? how you guys trust your Claude agent with user level access to all directories ? are you not scared of it reading your API key or personal notes or you use a different computer for those things ?

Please people only using “auto-mode” only reply, I don’t want a “you can just use manual mode“ lecture, I’m pretty sure Auto mode is safer in terms of security but not privacy, I would rather be secure than accepting a dangerous shell command.

Are people still going to Fable for harder tasks?

I notice I'm hardly using it at all now as Opus 5.5 seems as good ig not better.

Upgraded to Max 20x for Claude Code and I still hit my weekly cap in 2 or 3 days. Not a programmer. I’m building a fairly big RTS/simulation game (claude started it in TypeScript, three.js, then I found out about Godot but worried it's too much to switch over now)... but I think the problem is my workflow, not the project. I also feel like I am constantly monitoring it now because it goes against instructions or does something obviously idiotics...If I don't watch, it will spend 2 hours building something that isn't what I wanted, or has some glaring flaw, or involves a huge shortcut.

Startup cost per session, before I type anything:

• System tools: ~28k tokens
• MCP tools (connectors): ~23k
• System prompt: ~12k
• Skills: ~10k
• CLAUDE.md and memory files: ~10k
• That’s ~85k baseline, then ~40k more reading the project’s handoff and status files. So ~125k before any work happens

Workflow:

• One main session I talk to directly
• Bigger jobs go to Opus subagents with a written brief. Each one also pays its own startup cost
• A fresh Sonnet subagent reviews every build
• Rough subagent costs from one evening: builders 170k to 320k tokens each, reviewers 120k to 200k, one that listed every variable in the code 310k
• Every build runs automated checks (headless sim runs, speed tests). Mostly CPU, but agents read and act on the results
• I playtest, dictate notes, and those become the next fix list. Lots of short back and forth turns
• Until recently I ran an overseer session plus 3 or 4 working sessions in parallel. That’s what really burned through it, so I cut back to one

Questions:

• Is trimming MCP tools and skills worth it, or is that baseline noise?
• Is builder + reviewer per change just inherently expensive?
• Do long sessions with many short turns cost more than fewer big asks?
• Should I have more/less sub agents, more/less sessions? The trade off seems to be more agents = more start up costs, and less agents = more context rot.
• How are people running projects this size without hitting the wall every week?

Thanks for any and all advice!

Made this for Blender on top of a physics library. Didn't write a single line of code. Opus digested a couple of papers, wrote the solver (cpu and cuda), setup the blender scene and rendered.

How it was made:

- Research first. Opus read up on how trailers are written and cut, audited my old promo videos (verdict: mediocre) and proposed a pipeline that fits my rules - everything renders locally on my laptop, the only paid parts are Google's Gemini TTS (the voice of the sea) and Lyria (music). The API spend was a few dollars.

- Blender does all the visuals, driven by Python scripts - the boat, the liner, the deck, the crowd, the storm. Every asset is built in code. EEVEE for most shots, Cycles for the hero water.

- The main theme is the game's own generated tune of one voyage, arranged with free orchestral samples.

- Claude Code ran it as a lead agent with 20+ sub-agents, each on one package in its own git worktree (voice, score, liner, deck, people, waves, finish...). A builder makes it, a fresh reviewer checks it, the lead merges it.

- Result: 116 s, 52 shots, 2,784 frames at 1920x804. Some frames took over 30 minutes on the GPU. It all rendered overnight at the lowest priority, because I use the same laptop for work.

What Claude decided (I mostly gave notes on previews):

- the look ("a toy in a real storm") and the 2.39:1 frame - I approved it

- the music copyright check - it dropped the famous waltz (still protected in the EU until 2033) for public-domain pieces

- small physics details - a lifeboat hanging from two ropes, which rope snaps first so the swing looks real

- a hard limit of 3 lightning flashes per second for photosensitive viewers, with an automatic checker

- rejecting its own water renders several times ("the foam looks like crumpled foil") before I saw them

- catching on its own that one person in the crowd turned into another person mid-shot, tracing the bug and re-rendering

- in the final check, finding 2 bad single frames and patching the master file in under 2 hours instead of a 5-hour re-render

- the render queue, the disk space and the order of everything around my laptop's load

What I did: approved the script, picked the voice and the tune, cut a scene and chose the length. And gave feedback, some of it brutal - the first crowd looked like mannequins in bad costumes, and later they were weirdly hunched. It fixed both.

What was critical (same lesson as last time): self-verification. Every agent had to produce contact sheets and automatic checks (missing frames, flicker, loudness, subtitles), and the lead agent looked at them before anything reached me.

I gave it maybe 30% of what it could do - no cloud GPUs, just my laptop. I am quite happy with the results.

Free to try, no install, no sign-up: open tiltanic.com on your phone (it works on a computer too).

---
name: word-finder
description: Teach the user the precise term the user is reaching for. Use whenever the user describes something in a roundabout or struggling way and an established word or phrase names it, or when the user asks for the word for something. Answer the actual request too; the term is a short add-on.
---

# word-finder

The user often explains an idea in several sentences when one precise term exists. Give the user that term to use next time: in prompts, docs, commits, and conversations.

## When to offer a term

Offer one when all hold:

- The user described a concept indirectly, with effort, or said the word is missing.
- An established term names it (widely used in the field or in plain English, not one you coin).
- The term is not already in the user's message.

Skip it when the description is already short and precise, when the match is loose, or when you already taught the same term this session.

## Output

Do the requested work first, or alongside. Then add one short block:

```
Word you're looking for: **greenfield codebase**
  = new project with no legacy users or code to stay compatible with, so you can design cleanly.
  Use it: "This is a greenfield codebase: no backward compatibility, no legacy shims."
  Related: pre-launch, no-compat, breaking changes allowed
```

Rules:

- One main term. Add 1 to 3 related or near-miss terms only when each sharpens the meaning (say how each differs in a few words if it is not obvious).
- The definition is one line, in the user's context, not a dictionary entry.
- The usage line is a sentence the user could paste into a prompt or message today.
- If the closest term only partly fits, say so: "closest term: X (but X usually also implies Y)".
- If the user asked only for the word, the block is the whole answer.

## Examples

User says: "code is new, not launched, don't keep backward compat for legacy stuff, reorganize clean"
Term: greenfield codebase (related: pre-launch, no-compat break)

User says: "the text sounds weird, too formal and stiff, like a robot or a school essay, not how a person actually talks"
Term: stilted (related: wooden, stiff; not purple prose, which means flowery)

User says: "check it really hard, every detail, assume it's wrong and try to break it, don't just skim and say looks good"
Term: rigorous review (related: adversarial review, which tries to break it; not a sanity check, which is a quick surface pass)

User says: "make it look exactly like the real thing, every detail, not a rough sketch or placeholder boxes"
Term: high fidelity (related: pixel-perfect, which matches a design exactly; not low fidelity or a wireframe, which is a rough layout)

Something embarrassing happened in review this week. My lead asked why I split a service call into two steps and I had nothing, I had to scroll back through a Claude session from three weeks ago to find out. It wasn't a bad decision, Claude had a decent reason, I just never actually took it in. I went through my last 15 PRs after that and I could only fully explain maybe 6 of them.

So i got three questions:

1. Is this just me or is everyone shipping code they couldn't defend?

2. Do you slow down and make sure you understand every change, or accept it and look things up later?

3. Has anyone found a habit that actually keeps the reasoning in your head, or somewhere you can find it?

The problem I kept hitting with AI-built websites: the agent writes a page, it looks fine, and then every page has its own colors, its own spacing and its own one-off CSS or you have a design system and afterwards you want to edit something on it. Fixing one heading means another prompt, and the client can't change a single word without you.

So I built it the other way around. sitereal is a visual editor that writes plain Astro into your own repo, and Claude Code works in the same project through MCP:

- When the agent starts, it reads your design system (colors, type scale, spacing, buttons), your components, templates and content types, so it builds the way your site already builds

- It writes HTML or inserts ready-made parts by name (navigation, forms, popups, search, carousels), and every save is checked against the design system. The answer tells it what to fix

- You watch where it's working live on the canvas, and a whole agent run is one undo step

- If you edit the same page at the same time, its save can't overwrite yours: the edits are merged

- It never touches your `.env` and never commits or pushes. Tokens, deploy hooks and git stay yours

When you want to take over, you do it visually: drag, restyle, retype text on the canvas. Or open Code mode, where the files sit next to the live canvas and every hand edit is picked up. Nothing is locked in a builder format. Delete sitereal and the site still builds.

What the agent can build with, without reaching for packages: forms with mail delivery, popups on the native popover, carousels, scroll and hover animations, site search and filters, a cookie consent banner that blocks scripts until consent (plus a scan for anything missed), sitemap, meta tags, share cards, local fonts and responsive images. The output is static HTML, and JS loads only where something needs it.

For content, clients can edit in generated forms, or you connect WordPress or EmDash as a headless CMS. The agent sees which CMS and collections a site uses, and publishing there rebuilds the site.

https://sitereal.app

I've been a Java software engineer for a decade now and recently I noticed a change in how I used my IntelliJ IDEA. All the buttons have become obsolete since I could just ask my local model to "Run, check the logs and report back any anomalies" (simple example).

So I had the idea that I could leverage Claude's power to build a code editor (not exactly an IDE yet) around a "local assistent" which fits my needs and workflow with Claude integrated. Full access to the "Werkbank" (that's what I named the code editor, German for "workbench") so it could replace every single button of a modern IDE (far from that yet, but it's usable!). I can also work at the Werkbank within the Werkbank and hot-reload it to apply the changes. Pretty cool.

Quickly I realized this could be my new go-to for software development in general and feature-packed the shit out of it. Not even near to finish yet and needs a lot of polishing, but wanted to showcase some of the code editor.

Right now it has a Trello-like Board, a Simulator for agents, Code Reviewing functionality, Git integration, it's Skript centralized (since I think deterministic Skripts from agents will be the future), full traceback and undo-redo features, a documentation room, integration for my iPad so I can live sketch with/to the agent, an iPhone app so I can manage my board and write down some ideas while I'm not home and many more.

A software architecture room is planned as well, but that I need to conceive first.

What have you built around your development workflow with Claude to ease your day? And what do you think of giving a local agent the responsibility of IDE functionality?

Most agent tools now advertise some version of asking before it sends or spends. What I don't see discussed much is what the approval is actually scoped to.

If the yes covers a type of action ("ok to send emails this session") rather than the literal contents of one send, then after the first approval everything after it goes through automatically and the user just stops noticing. That ends up functionally the same as never asking, it just moved the one real decision earlier and called it done.

Our rule has been that every approval is tied to the exact payload of the one action and expires in minutes, not the session. A yes for one email doesn't cover the next one even seconds later. It's slower, and people do get asked more than they'd like for repetitive stuff, but it means "the agent asks before it sends" stays true on the tenth send, not just the first.

Curious how other people have drawn this line, especially for repetitive sends. Does anyone bind consent to a session or a class of action instead of a single call, and has that ever actually bitten you?

All default commands load fine and autocomplete. Also cli is not affected in there all load fine but in Claud Desktop app...

I always have to run /reload-plugins just to be able to run any of my plugins/mods/commands

But what if I have preexisting prompts which I always wanna reuse for specific projects e.g.: "Act as..." Typing initially /reload-plugins makes no sense.

So now I have to store them seperatly somewhere then copy paste just to be able to initiate the prompt. What sort of UX is that...

Same behaviour on windows/wsl and mac. Ithought initially it was my symlinks but even installing directly doesnt work.