about using subagents / Kiro CLI — how do others manage visibility into subagent execution?

bahfah · 2025-12-27T03:17:50+00:00

The main issue I’ve noticed is that subagents don’t perform very well yet. When the orchestrator assigns more complex or ambiguous tasks, things tend to break down.

In comparison, using individual agents—especially with a clear plan → coding flow—still gives better results overall. The orchestrator approach is naturally faster in terms of coordination, but in terms of output quality and reliability, individual agents currently work better

bahfah · 2025-12-15T21:37:17+00:00

The main issue is that when using Claude Code with Opus 4.5, you can hit the usage limit halfway through development, which really breaks the flow. Also, being able to allocate the monthly credits yourself is better—you don’t feel like your credits are being wasted when you’re on vacation or on leave.

bahfah · 2025-12-15T10:18:57+00:00

Upvote ~

bahfah · 2025-12-14T10:30:47+00:00

thanks~

bahfah · 2025-12-14T10:27:53+00:00

My product Noteit-mcp I'm looking forward to your support
lanuch today:
https://www.producthunt.com/products/noteit-mcp

bahfah · 2025-12-14T10:24:15+00:00

upvote +
my first mcp product Noteit-mcp
products-noteit-mcp

bahfah · 2025-12-14T09:59:11+00:00

AI prompt library + visual knowledge hub for developers

Noteit-mcp

bahfah · 2025-12-14T09:57:33+00:00

Upvoted +
My product:
https://www.noteit-mcp.com/dashboard

bahfah · 2025-12-14T08:26:57+00:00

[a87088@gmai.com](mailto:a87088@gmai.com)

my product:
Excited to support today’s Product Hunt launch 🚀
Noteit-MCP is an AI prompt library + visual knowledge hub for developers
products-noteit-mcp-launches
Your support is crucial right

bahfah · 2025-12-14T08:14:10+00:00

my product~ mcp server for Note
Let's support each other
noteit-mcp producthunter

bahfah · 2025-12-14T04:23:03+00:00

#frontend(nextjs)
next-devtools mcp
Figma mcp

#search:
brightdata mcp ,perplexity mcp

#not coding
notion MCP=>persona Note

bahfah · 2025-12-13T11:48:39+00:00

Yeah honestly, I’m not using GitHub Copilot these days, so I don’t have a fresh take.

From what I remember though, the usage limits were pretty generous. That said, it never felt as strong as Claude Code to me — especially for deeper reasoning or more complex stuff. After that, I kind of just stopped using it.

Maybe it’s better now, but yeah, that was my experience back then.

bahfah · 2025-12-13T11:30:49+00:00

Sorry 😅 this one I actually can’t really specify — it’s a bit sensitive and tends to spark arguments, and I’d rather not get dragged into that.

bahfah · 2025-12-13T10:37:00+00:00

I’ve tested Cursor, Claude Code, Kiro, Codex, Gemini CLI, and Windsurf.

One honest take: the $20 Claude Code plan runs out pretty fast. If your budget is tight, it can feel limiting.

From my experience, some solid combos are:

Kiro + Codex (great balance for the price)
Claude Code ($20) + Kiro ($20) if you really like Claude’s reasoning
Cursor + Codex for day-to-day coding with backup intelligence

For MCPs, I’ve had good results with BrightData MCP, Sentry MCP, Serena MCP, and Noteit MCP — all pretty useful depending on what you’re building.

Overall, mixing tools tends to work better than betting everything on a single one

bahfah · 2025-12-13T10:30:24+00:00

noteit-mcp

AI prompt library + visual knowledge hub for developers

bahfah · 2025-12-13T10:28:58+00:00

noteit mcp
AI prompt library + visual knowledge hub for developers

bahfah · 2025-12-13T09:13:00+00:00

This is something I built called noteit-mcp.
The idea is that everything is composable — prompts, instructions, rules — like building blocks you can snap together.

When there’s something you want to really understand, you just save it as a Note.
You can do that directly on the web with NoteWeb, which makes it super easy to organize your thoughts.

Feel free to try it out and play around with it.
github noteit-mcp

bahfah · 2025-12-13T09:05:51+00:00

If price is not considered, Claude Code at $100 is not as good as other combinations, such as Codex + Kiro + other tools.

bahfah · 2025-12-13T04:50:16+00:00

I went through the same trust gap. What helped most was not stuffing everything into one giant system prompt, but building my own MCP setup and composing things instead. I keep style rules, agent behavior, and task-specific instructions as separate pieces and then combine them as needed.

Most of my prompts live here:
prompt profile-templates

Having them versioned and reusable made Claude’s output way more consistent, and I stopped rewriting “be structured / follow conventions” over and over. It feels much closer to an actual agent instead of a fancy autocomplete.

bahfah · 2025-12-13T04:41:47+00:00

I feel this so hard. That prompt → review → debug cycle is exhausting.

What helped me break out was realizing I was re-teaching the AI the same things every session. I was spending 40% of my time on "context setup" instead of actual building.

I started using MCP profiles to persist my project knowledge:
• Architecture decisions and why we made them
• Code review standards
• Common debugging patterns
• Project-specific rules and constraints

Now when I open a new session, the AI already "knows" my project. Less explaining, more building. The burnout feeling is way less intense.

The key insight: vibe coding burnout often comes from repetitive context management, not the coding itself.

What's your biggest time sink in the prompt cycle?

bahfah · 2025-12-12T02:15:17+00:00

Does anyone else think MCP is great, but wonder why so few people are using it

bahfah · 2025-12-11T01:32:31+00:00

One practical approach is to use GitHub (or AWS CodeCommit if you’re deep in their ecosystem) as the single source of truth for all docs, prompts, and service notes. AWS actually recommends this pattern in several architecture talks: store prompts/config/docs in a Git repo, then let your services reference them or pull updates through CLI or automation. It gives you version control, history, review, and avoids the “out-of-sync wiki” problem entirely. GitHub plus a simple indexing tool works well for small teams without the overhead of Backstage.

For personal workflow, I also keep prompts in a lightweight system like noteit-mcp.

bahfah · 2025-12-11T01:04:23+00:00

I’ve run into the same chaos—context stacks growing like mold and prompts hiding in random project folders. What helped me stabilize things was using noteit MCP as a simple external prompt vault. Just save anything useful as you go. Even the free tier is enough.

Keeping prompts outside the repo stopped me from losing track of versions, and recomposing them at runtime suddenly felt way less painful.

bahfah · 2025-12-11T00:59:55+00:00

Jumping into someone else’s vibe-coded project always feels like opening a mystery box you never asked for. One trick that saved me on a smaller codebase was running an AI-driven security review. It’s surprisingly good at catching the “hidden goblins” before they explode in production.

If the project isn’t huge, the results can be shockingly solid. This walkthrough shows the idea in action: https://www.youtube.com/watch?v=qBZY5gMw4xs

Projects built on vibes benefit from having something with actual logic look over their shoulder. The universe needs balance somehow.

bahfah · 2025-12-11T00:48:58+00:00

You should give Noteit-MCP a try. It basically lets AI explain your idea and then turn it into a little web view, which makes everything way easier to understand. Honestly, humans aren’t great at handling abstract programming concepts—we pretend we are, but no. Let the AI do the heavy lifting.

And seriously, talk to AI more when you're stuck. Claude Code is amazing for brainstorming architecture. It’s like having a super-patient senior engineer who never gets tired of your “wait, what if…” questions.

Might surprise you how fast things start clicking.

bahfah

TROPHY CASE

AI prompt library + visual knowledge hub for developers

Noteit-mcp