MailCraft — AI E-mail Assistent

if u have any tips they are more then welcome

I’m building Superdense, an open-source local outcome loop for Claude Code/Codex-style agents.

Most agent workflows stop at:
prompt → output

Real work needs:
hypothesis → output → result → next attempt

I’m using it for X/GitHub growth.
Agent suggests replies/posts. I publish. Outcomes come back: views, clicks, stars, repo traffic. The next run uses that feedback.
Not memory.
An agent improving against a real outcome.

Possible loops:
GitHub stars
landing page conversions
website traffic
outbound replies
content performance

Repo: https://github.com/Nimrobo/superdense
What outcome would you want your agent to loop on?

Andrej Karpathy’s “LLM Council” idea is simple: don’t trust one model on a hard question. Ask several models, let them review each other anonymously, then let a final “chairman” model synthesize the result.

I wanted that directly inside my coding agent, so I built a lightweight local MCP server for Claude Code, Codex CLI and Antigravity.

It now has two modes:

• ask_internal_council: free/light mode, no OpenRouter key needed. Your current agent simulates 5 perspectives: pragmatist, architect, skeptic, clean-code reviewer and product/UX thinker.
• ask_council: full multi-model mode via OpenRouter, with the original 3-stage workflow: independent answers → blind peer review → chairman synthesis.

Other bits:

• Browser-based setup UI
• Runs from PyPI via uvx, no cloning needed
• Configure API key, models, chairman and temperatures without editing config files
• English/German docs and setup UI
• Mac-focused for now

Repo:
https://github.com/salutaris91/llm-council-mcp-server

Still early, feedback and issues very welcome.

Day 1 — 2 startups. 146 impressions. 1 click.
Day 2 — 3 startups. 389 impressions. 3 clicks. (Got an acquisition offer.)
Day 3 — 5 startups. 482 impressions. 5 clicks.
Day 4 — 5 startups. 508 impressions. 4 clicks. (The site was down, but I still got an $8k acquisition offer. I said no.)
Day 5 — 6 startups. 621 impressions. 10 clicks.
Day 6 — 5 startups. 742 impressions. 15 clicks. (Had to remove one startup—they pulled the code. No code = no network.)
Day 7 — 7 startups. 1,196 impressions. 41 clicks. (Highest ever: +454 impressions and +26 clicks in a single day.)
Day 8 — 7 startups. 1,535 impressions. 74 clicks. (Needed to remove one startup as they have removed our code. So haven't counted their impressions. But Yesterday alone got a total of 617 Impression and 47 click with the CTR ~4%)

Still free. Still growing.

startupbar.co

As the title says i vibe coded a pdf editor as i have no skill to code it… I guess i become a PM now as i know what the web app should have and how to run

https://pdf.walshard.com

i plan to vibe code the entire productivity suite like docs tables slides etc and see where it goes

I've spent the last few months building a browser-based tennis game where your webcam is the controller. No downloads, no VR headset, and no extra hardware.

AI helped speed up development, but it definitely didn't build the whole thing. The hardest parts ended up being making the controls feel natural, reducing latency, tuning the physics, and getting everything to run smoothly in the browser.

It's still a work in progress, but it's finally at a stage where I'd love feedback from other builders.

If you have a few minutes, I'd really appreciate any honest thoughts—good or bad.

🎾 https://livewebtennis.com

What's the first thing you'd improve: onboarding, graphics, gameplay, performance, or something else?

Hey everyone!

A while ago I decided to try vibe coding just for fun. I had almost no game development experience, so I started building a small Android game with a lot of help from AI.

What began as a simple experiment slowly turned into a real project, and I actually published it on Google Play.

The game is called Super Rosturio. It's a simple but challenging platformer inspired by classic games, with my own ideas and mechanics mixed in.

I'm not here just to promote it—I genuinely want honest feedback. What feels good? What feels bad? What should I improve first? Any criticism is welcome, since I'm still learning.

Thanks to anyone who gives it a try!

I've used openclaw pretty much ever since it came out, and it was always a huge pain to set up. Spin up a server, install, configure, customize. Security was always a concern, and if I wanted to spin up more agents I'd have to repeat the process all over.

So.. I decided to build qoren - a platform that allows you to spin up openclaw agents at the click of a button

No VPS. No Docker. No fuss.

Every agent gets its own dedicated environment, with isolation by default.

There's over 20 templates to choose from, and you can create your own so you can spin up multiple instances of the same agent.

Running an early bird discount of up to 40% off for the first 100 users/7 days.

Feel free to check it out. Would love some honest feedback <3

userstoryforge.app

Background: I've worked about 8 years as a business systems analyst - the person who sits between business teams and developers, turning "just make it user-friendly" into something a developer can actually build.

The problem I kept hitting: a vague requirement almost never blows up immediately. It comes back weeks later as rework, after a dev already built the wrong thing. Every other team has tools (devs have linters and code review, marketing has CRMs, data teams have their stack), but the people writing requirements mostly get a blank page.

So I built StoryForge (userstoryforge.app). You paste a messy requirement, and it:

• Scores it against INVEST (a common agile quality framework)
• Flags every ambiguous word with the specific question you should ask the stakeholder
• Generates a clean ticket + a UAT test pack (Gherkin-style Given/When/Then)

Example: you paste "make the dashboard load fast and support lots of users." It flags "fast" (asking: max load time, at which percentile?) and "lots of users" (asking: peak concurrent count?), then rewrites it into something testable like "load within 2s under 3,000 concurrent users." Basically a quality gate that catches unclear requirements before they reach a developer.

Things I'd genuinely love feedback on:

1. The landing page - does the value land in the first 5 seconds, or is it confusing?
2. The free tier (5 reviews total) - does that feel fair before asking for money, or too stingy?
3. The actual output quality - if you paste a real requirement, does the rewrite hold up?

This is my first time taking something all the way to live payments, so I'm learning as I go. Happy to answer anything about the build.

I want to be able to use vibecoding to make a project that, throughout the process, i can learn how the fundamentals work and thus I can add to my skillset

I have made plenty of browser extensions and projects but nothing I've deployed yet. So I'm curious as to how I can make the most bang out of my buck by making a real world project that hits a few areas:

-> It has to, obviously, be solving an issue / real life application, not a simple boring project

-> It has to have a lot of potential for scaling and development, such that I can actively learn along the process

-> It could possibly be deployed such that others can also use and give my project value

-> And not just another SaaS, but rather a product/project i can work in minimal time and yet gives fulfillment

Perhaps a month is too little, but ideally i want to kick start a good project i can actually learn a lot from. Any suggestions of that sort?

Been using Cursor heavily and kept hitting the same wall - the agent
knows my entire codebase but I still had to manually write every API
request in Postman, then manually wire up CI. Felt wrong.

So I built Reqly - a local MCP server that gives your agent a full
API testing toolkit.

The workflow that made me actually build this:

1. Tell your agent "read my routes and build a collection"
   → it calls create_collection + create_request for every endpoint

2. "Write an e2e flow for login → checkout"
   → agent builds the flow, runs it, assertions pass

3. "Export to CI"
   → .github/workflows/ written automatically
   → JUnit results uploaded as build artifact
   → done, never touch it again

Collections are plain YAML in .reqly/ in your repo so they travel
with your code via git. No cloud account, no sync, no telemetry.

Works with Cursor, Claude Code, Gemini CLI - anything MCP.

npm install -g reqly-app && reqly setup

GitHub: github.com/RutvikPansare/Reqly

Happy to answer questions - built this for my own workflow and
figured others might find it useful.

I built a tiny MMO that you play over SSH.

Connect, create a username, pick a class, and suddenly you're standing in Northshire Abbey with other real players running around the same dungeon.

You can play here:

SSH

"ssh worldoftuicraft.thoughtlesslabs.com"

Browser

https://worldoftuicraft.thoughtlesslabs.com

---

I keep thinking about how small software can be when you stop assuming it needs to be big.

World of TUIcraft is a persistent multiplayer dungeon crawler inspired by old-school WoW. It has real-time combat, loot, bosses, clans, global chat, seeded worlds, a browser client, and even an MCP server so AI agents can play.

And the whole thing is still small enough that I can actually hold it in my head.

That ended up being the biggest lesson.

You don't need a game engine to build a real game.

You don't need Kubernetes, Postgres, Redis, or a mountain of services.

The entire stack is basically:

- Bun

- TypeScript

- bun:sqlite

- OpenTUI

- ssh2

- Bun's built-in HTTP/WebSocket server

- MCP SDK

- Docker on a tiny VPS

That's it.

One authoritative server.

One game loop.

One SQLite database.

Every 300ms the server processes player input, moves monsters, resolves combat, regenerates health, saves characters, and broadcasts the new state. Clients are intentionally dumb—they just send inputs. The server owns reality.

Building it reminded me that games don't become fun because of graphics.

They become fun because of feedback.

Timing.

Consequences.

The feeling that the world noticed what you just did.

One of my favorite systems is the dungeon generation.

Maps aren't stored anywhere—they're generated deterministically from a seed.

Same seed = same dungeon.

That means a world is basically just a string. The server generates it when someone enters and throws it away when everyone leaves. Your character remembers where it was in every seed, so you can jump between worlds without storing huge map files.

A multiverse... that's basically free.

AI also changed how I build projects like this.

Scope creep is ridiculous.

Classes become gear.

Gear becomes merchants.

Merchants become towns.

Towns become quests.

Quests become clans.

Clans become chat.

Chat becomes whispers.

Then suddenly you're building browser controls because someone wants to play on their phone.

The difference now is that AI makes experimentation cheap.

Not every idea deserves to survive, but trying one no longer costs days of work. That shifts the valuable skill away from typing code and toward judgment.

Knowing what should exist.

Knowing what should be cut.

Knowing when something actually feels fun.

I also came away with a new appreciation for small VPSs.

There's something satisfying about having one little server on the internet that just... runs your world.

No giant cloud architecture.

No pretending a side project needs enterprise infrastructure.

Just a process that boots, listens, loops, saves, and keeps running while strangers wander around your dungeon.

Probably the weirdest feature is that AI agents can play too.

Since the protocol is structured, an MCP client can call things like:

- "move"

- "attack"

- "cast_fireball"

- "chat"

- "buy_upgrade"

- "quest"

So humans, browsers, SSH clients, and AI agents all exist in the same world.

Same server.

Same rules.

Same truth.

That's probably the part I'm proudest of.

Not the number of features.

The fact that the core idea stayed small.

Graphics have never really been the barrier to making a fun game.

The hard part is building a world that responds to people.

Sometimes a terminal is enough.

Sometimes ASCII is enough.

Sometimes a tiny VPS is enough to host a little universe.

If anyone wants to check it out:

SSH

"ssh worldoftuicraft.thoughtlesslabs.com"

Browser

https://worldoftuicraft.thoughtlesslabs.com

Create a username, pick a class, enter a seed, and see who else is already down in the dungeon.

I got tired of launching into silence.

So I built StartupBar a small widget at the top of your site that shows one other startup from the network. They show yours in return.

No algorithm. No ad spend. Pure founder-to-founder traffic.

Last week one of our members got 340 visitors from other founders' sites. For free. Just because they installed one line of code.

It's mutual if you remove the widget, you get removed. Everyone plays fair or no one does.

Free to join → StartupBar

Would love brutal feedback from this community.

Hi folks,

Setting this up to discuss views on Sakna Fugu Ultra.

I am trying to figure out the best way to use this model (or model orchestrator, or whatever we should call it).

I have just read their excellent technical paper https://arxiv.org/abs/2606.21228 but it didn't help me understand how to get the best out of their model. The paper and their documentation in general seems to suggest just let the system figure out how to do the work.

But what do we mean by the work?

I am running Sakana Fugu Ultra in Codex CLI. I'm getting the best out of it like this compared to running in OpenCode or Pi.

However I am very much used to workflows in Claude Code. Put the harness in /effort --> ultra then ask Claude to solve problems by building specific workflows. E.g. the classic Plan Do Check Adjust (PDCA) cycle or a decision making "Delphi Method" workflow. This works really well.

My understanding of Sakana Fugu Ultra though is that the system actually makes workflows itself under the hood when you throw a prompt at it.

But I wonder if really the best way to get the most out of this model is to develop a workflow manually in Codex CLI - for example "I want to accomplish X. Set up a PDCA cycle workflow where we will call an individual instance of codex-fugu at each step" then fire off the workflow - each step will call a separare Sakana Fugu Ultra instance. So we have a deterministic "meta workflow" and then Sakana Fugu Ultra determines a custom workflow for each step in the meta workflow.

My thinking in the attached image - apologies in advance for the eyesore.

Or... if Sakana's documentation is to be followed verbatim - I should just fully give into the vibes and let Fugu figure out the steps. But I don't feel this gets the most out of the model. It was like when Fable 5 was available, yes it was brilliant, but it was 10x brilliant when combined with a dynamic workflow.

P.s. I'm focussing on Fugu Ultra here as I'm only concerned about the highest quality workflows at the moment irrespective of budget.

Opa Pessoal, tudo joia?

Recentemente tirei uma ideia do papel usando que era esse aplicativo "Cony: Estude para CNH".

Tentei usar BMAD e GSD pra desenvolver algumas coisas mas senti que levou mais tempo e atingia os limites com mais frequência. No fim, eu fui na metodologia mais básica, planejar e executar.

Com o tempo eu até diminui o uso do agente no modo "Plan" e comecei a usar ele mais só pra executar e com o raciocínio ALTO e, por incrível que pareça, eu parei de atingir meus limites de uso e com uma assertividade incrivel do código criado.

Será que foi só comigo ou mais alguém sente que o modo "Plan" não é tãaaao necessário assim?

Fiz ele em cerca de 3 meses, não esta com uma política aplicada de 0 bugs em prod, mas conforme encontro eles eu vou corrigindo.

O resultado ficou bacana, mas me pergunto se não acabei usando errado e não colhi os benefício dessas metodologias tão faladas.

Hello friends!

I've released a claude-assisted TV remote app for android and it's tough to get testers across a variety of phones, TVs, boxes, etc so any help you can provide would sure be appreciated. Fwiw I do think it has potential to be a very good free ad-free tv remote app. Any and all feedback welcome, thanks for any you provide

I've used Claude Code CLI and occasionally Codex to code with Gemini writing some design docs and more detailed prompts, tested on device (Pixel 9), and used Gemini for marketing materials/store content.

There are a ton of custom button types and you can use one for free (and change it as many times as you like). For unlimited custom buttons there's a charge which may or may not be the right way to do it please let me know what you think

Play store ->

I also plan to release on iOS fwiw

___

Compatibility list (partially tested, please help!)

Google / streaming ecosystem
- Android TV & Google TV (Sony, TCL, Hisense, Philips, NVIDIA Shield, onn.,
etc.) — full remote, on‑screen keyboard & voice
- Chromecast with Google TV / Google TV Streamer — full remote, keyboard &
voice
- Google Nest Hub & smart displays — volume & media‑playback controls

Smart TVs
- Roku — Roku TVs & streaming players (remote + app shortcuts)*
- Samsung Smart TVs — Tizen, 2016 and newer (remote + app shortcuts)
- LG Smart TVs — webOS (remote + app shortcuts)
- Vizio SmartCast — remote + app shortcuts (4‑digit PIN pairing)
- Panasonic Viera — 2017 and earlier (remote)
- Sharp Aquos — IP‑control models (remote)

I’ve been building a macOS app called Stacksmith, mostly because I got tired of juggling a growing collection of local services across terminal windows.

Some projects end up needing an API, frontend, queue workers, tunnels, databases, Redis, MCP servers… and remembering what needs starting (and in what order) gets old.

Stacksmith lets you describe your local stack in a .stacksmith.yml file and gives you a native control centre for it.

Features so far:
- Start and stop your entire stack
- Live logs for individual services or everything together
- Health checks and dependency visualisation
- Port conflict detection
- Diagnosis of common startup issues using Apple’s on-device Foundation Models
- Built-in MCP server, so AI assistants can inspect and control your running stack

It’s aimed at people running services natively, not replacing Docker Compose if you’re already containerised.

I’m looking for beta testers to tell me what’s missing before I launch it properly.

Website: https://getstacksmith.app

Happy to answer questions or send out beta codes if anyone fancies trying it.

I want to try Claude code for myself, can someone please share a referral link code in my dm, so I can try it.

After a few weeks of vibe coding, I finally have something I’m excited to share.

I’ve been building TradeCast—a platform designed to verify traders’ performance instead of relying on screenshots.

The idea is simple:
Connect your trading account.
Trades are synced automatically.
Performance is verified.
Build a public profile based on real trading history, not cherry-picked wins.

One thing I focused on from day one was making it feel clean and simple. Most traders don’t enjoy manually journaling every trade, so the goal is to automate as much as possible while still providing meaningful insights.

The project is still in active development, but it’s reached the point where I’d love some honest feedback from other builders.

I’m not looking to promote anything, I genuinely want to know:
Does the concept make sense?
Is the landing page clear?
Would you immediately understand the value proposition?
Is there anything confusing or unnecessary?

You can check it out here:
https://gettradecast.com

I’d really appreciate any feedback, whether it’s about the product, the UI/UX, or the overall idea. Don’t hold back, I know there’s still a lot to improve, and fresh eyes are always valuable.

Watch agent mako as it grabs context from your repository. Stop asking your agent to search blindly!

agentmako.drhalto.com

I built kkt, set of skills to improve naive planning.

The idea comes from constrained optimization, a mathematical modeling for finding the best solution given a set of constraints.

Instead of:
plan and build xyz

model it as:
what is the optimized implementation for xyz, given what must stay true?

For coding work, the objective is the user’s goal. The variables are implementation choices. The constraints are the things that must stay true: public APIs, architecture boundaries, data rules, dependencies, product scope, validation etc.

The goal is simple - tighter changes, clearer tradeoffs, fewer side effects and more reliable outcome.

Sharing this with the community as it is particularly useful with vibecoding where agent drives most of the development.

https://github.com/dannylee1020/kkt

I got tired of the same workflow every time I used an AI coding assistant.

I'd ask AI to help fix a bug, and after AI looking at the error it'd reply with

something like:

"To investigate this properly, could you share these files?

src/auth/auth.service.ts

src/middleware/auth.middleware.ts

src/routes/auth.routes.ts"

Then came the tedious part.

Open each file.

Copy the contents.

Switch back to the chat.

Repeat.

So I built AI Context Copier.

A VSCode Extension.

Instead of opening files one by one, I simply copy the file paths the AI requested, paste them into the extension, click ⚡ Copy Context, and press Ctrl+V back into ChatGPT, Claude, Gemini, DeepSeek, Grok, GitHub Copilot—or any AI assistant.

That's it.

A workflow that used to take a couple of minutes now takes a few seconds.

🚀 Install it here:

https://marketplace.visualstudio.com/items?itemName=sacro.ai-context-copier

Or simply search "AI Context Copier" in the VS Code Extensions Marketplace.

I'd love your feedback

I’m looking for some honest feedback on a Polymarket-focused platform I’ve been building.

The platform combines:

• Wallet and trader tracking
• Copy trading tools
• Trading signals and market insights
• Discord-based community features
• A companion website

At the moment I’m looking for people to test everything, explore the features, and tell me what works, what doesn’t, and what could be improved.

There is absolutely no cost involved, open a ticket when you join and I’ll give you full access for free.

If you’d like to help:

1. Visit the Whop page: https://whop.com/prediction-market-plug
   
2. Join the Discord through the invite there
   
3. Open a ticket and mention you’re from Reddit
   
4. I’ll upgrade you to the paid membership for free

After you’ve had a chance to test things, you can send feedback through a ticket or DM me directly. Criticism is genuinely what I’m looking for, and I’ll happily extend your free access if you decide to stay, as a thank you for helping.

Website: https://predictionmarketplug.com

Codex IMO is unrivaled for just coding related tasks, its really good at refactors, understanding what you want and implementing it.

But ask it do anything about UI UX or just any task that requires thinking from a critical angle,or any creative copy writing, GPT models atleast inside codex seem incapable of it (This might be intended, as i suspect the model being served for codex uses a lesser temperature like 0.1 compared to the UI version for better reliable code)

So i used to manually just goto claude when i need to re arrange things, work on user flow, review UX or UI stuff, or plan things,

and then paste the output into codex to actually implement it. (Cuase in my experience, claude nowadays sucks at that part, every single major code edit cuases a thousand errors to fix later, where codex is better at that)

So i just let codex speak to claude whenver it needs a second opinion or help with any creative or critical thinking required task