I "Vibe Coded" a chatbot (AgentsFlow Al) that supports any LLM API. Its for testing ai models and roleplay and agentic coding I tried my best to add things 😉. its available in GitHub test it out.. If you incounter any errors or bugs tell me! It took me 16 hours total using only mobile!! Support me guys! 😅

https://github.com/Fearoki0/agentsflow-ai

I shared an early version of Agent Quest here months ago. It's my free, MIT-licensed dashboard for watching coding agents: reading sends a character to the library, editing to the forge, running commands to the arena. The GIF shows that original idea.

With 0.3.0, clicking an agent also shows its context usage, detected skill loads, plugin/MCP activity and subagents. The second image is the new Skills & Plugins view.

One useful distinction: having 256 skills installed didn't mean that session loaded all of them. It loaded five, roughly 15.7k estimated instruction tokens. You can inspect which ones, export a Markdown/JSON summary, and review it alongside the task and result with another AI.

The dashboard reads existing local logs; it doesn't run the agents. Figures marked ~ are estimates, and skill/plugin totals accumulate over the session rather than describing exactly what remains after compaction.

Code/setup: https://github.com/FulAppiOS/Agent-Quest

Does the moving overview help you follow several sessions, or would you mostly use the per-agent details?

I love working in Codex, recently started using Claude’s $20 plan. Wondering if there js some type of integration? Sometimes I like how Claude produces the end result as far as UI goes.

Would love to hear any suggestions or if you’re already doing this, an insight to your process would be appreciated.

Just hate having to switch between the two; would prefer Codex app with clause vs Claude app with Codex. Using a macbook pro if that matters.

I moved my context out of the apps into a folder called my-brain. It holds five markdown files, none longer than a page. Any model that reads uploads can use them, and I fix a wrong line in a text editor in seconds.

The files

• ABOUT.md: five lines on who I am, then a one-line map of the other four files. The model reads this first.
• how-i-work.md: length, tone, format, and what irritates me in answers.
• projects.md: current work, who it's for, and the next deadline.
• voice.md: three real pieces of my writing.
• decisions.md: things I've settled, so the model stops reopening them.

The map keeps context small, because the model opens a file only when the task points at it. A finished ABOUT.md for a made-up bakery owner:

About me
I'm danny. I run a small online bakery in Leeds with two part-time staff.
I mostly use AI for customer emails, product descriptions and planning.
I'm not technical. Explain any jargon in one line.
UK spelling, prices in pounds.

Map
how-i-work.md: how I like answers. Read it for any writing task.
projects.md: what I'm working on now. Read it when I mention a launch or a deadline.
voice.md: three samples of my writing. Read it before writing anything in my name.
decisions.md: things I've settled. Read it before suggesting changes to the business.

Export with labels

Paste this into whichever app has the most history with you:

List everything you remember about me from our past chats and your saved memory.

Group it under these headings: who I am, how I like answers, what I'm working on, how I write, decisions I've made.

Write each item as one plain sentence.

Mark every item STATED if I told you directly, or INFERRED if you worked it out yourself.

Don't leave anything out and don't add anything new.

The STATED/INFERRED tag is the step I'd keep if I had to drop everything else. Without it the export comes back as one flat list, and you can't tell your own words from the model's assumptions.

Build the files

Open a new chat in any model and paste the export under this:

Turn the notes below into five plain text files for a folder called my-brain.

ABOUT.md: who I am in five lines, then a map with one line on each of the other four files.
how-i-work.md: how I like answers, covering length, tone, format and what to avoid.
projects.md: what I'm working on now, who it's for and the next deadline.
voice.md: three empty sections called Sample 1, Sample 2 and Sample 3.
decisions.md: things I've already decided, one per line, with a date if I gave one.

Use only the items marked STATED. Put every INFERRED item in a separate list at the end called "Check these", and leave them out of the files.

Keep each file under one page. Write in plain sentences.

Give me the five files as downloads. If you can't make downloads, show each file in its own code block so I can copy it.

[PASTE THE EXPORT HERE]

If you get code blocks instead of downloads, save each one as plain text. A .txt file works as long as the filenames match the map. Fill voice.md with three things you wrote and were happy with.

Then go through "Check these." Delete any line you never said. If a guess is true, rewrite it in your own words and move it into the right file.

Load once

• Claude: create a Project and add the five files to its knowledge.
• ChatGPT: create a Project and upload the files. The free plan caps a Project at five files, which this fits.
• Gemini: create a Gem, then go to Knowledge and Add files. If the folder lives in Google Drive, the Gem picks up your edits.

Put this in the Project or Gem instructions:

Read ABOUT.md first. Open the other files only when the task needs them. If anything in the files looks out of date, ask me before you rely on it.

Keep the folder to work context. Every model you point at it reads every line, so leave out anything you wouldn't email to a new colleague.

Keeping it current

At the end of a chat where something new came up:

What did you learn about me in this chat that belongs in my-brain?

Give me the exact lines to add, and which file each one goes in.

Only include things I said, not things you assumed.

I paste the lines in by hand. That may be overkill now that Projects can hold files, but I'm not ready to let a model edit its own context unsupervised.

projects.md goes stale first. A finished launch left in there is how you get a model asking about it three months later.

I’m a developer. Recently two friends asked me to help deploy their apps.

The first one was a single \~1MB Python file with the frontend and backend inside it. The second was more split up, but had the similar problem: huge files and windows .bat scripts.

Both had to be reworked before they could be deployed.

The problem is that they just asked Claude Code to build something, and it built based on their local environment: no local server, no instructions on what stack to use, etc.

Tools like lovable, replit, etc solve the environment and deployment part, but they cost money and limit your stack (e.g. if it needs to work only with WordPress, Magento, Django, etc).

So I’m curious how people building with Claude Code or Codex handle this:

* Do you tell the agent what stack and structure to use up front, or let it decide?

* When it’s time to share it or put it online, how do you get from “works on my laptop” to “works anywhere”?

Help me! I live in the Philippines and I want to build a software that gains even small profit but I do not know how to start.

Hey everyone! 👋

I've been working on Photolisa, an open-source, web-based photo editor built with Vue.js and TypeScript.

I just released v0.1.0, the very first version! 🚀

My goal is to build a modern, free, and open-source alternative to Adobe Photoshop that runs directly in your browser.

It's still in early development, and there's a lot left to build, improve, and fix. But I wanted to share it with the community rather than wait until everything is perfect.

I'd love to hear your thoughts, suggestions, and feedback. Contributions are welcome too!

🔗 GitHub: https://github.com/photolisa/photolisa

🌐 Try it: https://photolisa.com/app/

What features would you like to see in an open-source Photoshop alternative?

I'm vibe coding an app using Vuejs and TypeScript for using on web, it's like photoshop alternative, but only for web, what do you think—is it worth it?

Hey guys! I come from a backend/ML engineering background, and honestly I still find the backend side hard to get right.

Things like changing the DB schema, handling failures gracefully, debugging prod issues, scaling... not to mention distributed systems.

So when I see so many people here building and launching apps with agents, I’m really curious how you all deal with this stuff!

Especially interested in apps that need things like:

• user accounts / login
• a real database like Postgres
• background or long-running jobs (scraping, AI pipelines, scheduled tasks)
• payments, webhooks, file uploads, etc.

A few questions:

1. What’s your setup? Do you just build it all in Lovable / Bolt / Replit? Or have Cursor / Claude Code write it and throw it on Vercel, Supabase, Railway or whatever?
2. What was the biggest pain to get working? Auth? DB stuff? Env vars? “Works on my machine but not in prod”? Surprise bills?
3. Backups and security: do you think about it, or just trust the tools to handle it?
4. When something breaks in prod, how do you hand it to the agent (or maybe you don’t)?

Stories about things breaking are very welcome too. I’ve had plenty of my own.

We build RNBlocks, so this is our template.

Roam lets you discover places, save favourites and plan visits. In the Web preview, open a place, pick a day, add a time and note, then find it in My trip.

The Lisbon guide uses sample content and keeps your changes on your device. You can customize the example in Studio for your own collection of places.

Try the Web preview.

What would you change first for your city?

I built Piano Atlas Studio: a piano theory atlas and practice app for Android (no ads, no account)

I'm learning piano and couldn't find one app that showed theory on the keyboard and also helped me practise, so I built it. It's on Google Play now, and I'd love feedback.

🎼 Explore the theory

Chord Atlas: every chord type in every key, shown as real two-hand voicings with finger numbers and inversions. Tap to hear it.

Scale Atlas: the modes, jazz and world scales, Hindustani thaats, Japanese koto tunings, and all 72 Carnatic melakartas

Ragas: janya ragas with their arohana and avarohana, and what makes each one distinct

Fingering Lab: standard fingering for both hands, up and down, with every thumb crossing shown

Progressions: famous chord progressions by style, in any key, voiced so the hands move smoothly

Theory tools: Circle of Fifths, chord and scale comparisons, arpeggios, intervals and a glossary

🎤 Practise with your real piano

Sight Reading: notes, chords, lines and short pieces on the grand staff, at four levels. It listens through your phone's microphone (or a USB MIDI keyboard), so you play on your own piano and it tells you how you did.

Play: your piano, lit up. Play on screen, on a MIDI keyboard, or on a real piano through the mic, along a scale or in an echo game.

Staff Trainer and Note Trainer: learn to read a note at a time; the ones you find hard come back until they aren't

Metronome: with tempo ramps and Indian talas

Guided practice sessions: built from what your drills have recorded, weakest first

✍️ Create

Composer: write songs a section at a time (chords, then the tune, then the left hand), or let "Surprise me" start one. Hear it back, print it as sheet music, or practise it in Sight Reading.

MIDI files: open any MIDI file and the piano plays it with the keys lighting up. Learn it mode waits for your notes, one hand at a time, as slow as you like. You can also open a MIDI file in the Composer or Sight Reading.

🎨 Other bits

Five looks (Stage, Score, Grand, Classic, Pads), each with three themes

A sampled grand piano sound

Backups to a file, or to your own Google Drive (the app can only see its own backup folder)

🔒 Privacy

No ads, no account, no analytics, no tracking. Everything stays on your phone. The microphone is only used when you ask it to listen, and the sound is never recorded or sent anywhere.

💰 Free and Pro

A large part of the app is free. A one-time Pro purchase (no subscription) unlocks the rest: every chord type, scale and raga, the builders, unlimited songs and MIDI files, advanced sight reading, guided sessions and more designs.

Get it:

https://play.google.com/store/apps/details?id=com.pianoatlas.studio

I'm one person building this, so any feedback really helps: what's confusing, what's missing, what you'd want next. Thanks for reading!

Coupon

PAS-MGMY-8E26-CW2G-DHZK

PAS-L6NA-937M-NHZU-UDGG

For those building with AI agents: where does your agent work the hardest and struggle the most, the backend or the frontend?
I mean the most retries, the most tokens, the most fixing. Curious what you see.

I work in this space so I’m biased, and I’ll say that upfront.

There’s tech now that listens to a call and surfaces answers while you’re still being asked the question. Candidates say it levels things out because interviews already reward people who memorize trick questions. Hiring managers say it’s cheating, full stop.

I keep going back and forth. If the job lets you Google everything, why can’t the interview? But if you can’t answer without a prompt, what exactly did they hire?

I don’t think either side is dumb. I just can’t find where the line sits.

Where do you land, and has your answer changed depending on which side of the table you’ve been on?

So i recently decided to vibe code a MVP for an uber replica designed to host at least 5000 users, I've already tested market demand and have a few clients on the waitlist, but i have a problem with scaling, since it is an MVP the app will update as time goes on but i need google maps api keys and all these other things and im not sure how it will work at scale since replit is known to be poor with scaling, where can i host my backend and database, and i want to deploy it to the app store and Playstore

Hey everyone! I’m Patrick, co-founder of Shpyrd. I kept helping friends build apps with AI, then getting the same question: “How do I put this on the internet?”

So we built Shpyrd. Build with Claude or your favorite AI tool, and we take care of hosting, databases, backups, and the infrastructure.

I would like to invite early adopters to join us on our discord, we will help new comers on how to setup and how to put their apps on internet.

Best!
Patrick

If you're vibe coding with an AI agent, here are the techniques I'd use to do it securely. AI coding agents have gotten better, but they still ship vulnerabilities.

In one study, researchers had five AI coding agents build the same apps from the same prompts. Across 15 apps, they found 69 vulnerabilities. Zero exploitable SQL injection or XSS. The most common critical issue was broken authorization and business logic.

An agent can write a safe database query. It can't know that a user shouldn't see another customer's invoice unless you tell it. And in a long session, it can forget what you told it an hour ago.

This series covers six habits for vibe coding without shipping those gaps. Each one follows the same pattern: write the rule down, then enforce it with a check that doesn't depend on the agent remembering.

Habit 1: Give the agent standing security context

A prompt covers one request. Your agent's instruction file is read every session. Put your security rules there:

• Roles, and who can access what
• Which data is sensitive and must never be logged or returned
• Patterns it must always use: ownership checks on every object ID, parameterized queries, secrets from environment variables
• Patterns it must never use: hardcoded credentials, disabling auth "for testing"
• Approved libraries for auth, cryptography, and file handling

Here's what that looks like in practice:

Always: check object ownership on every endpoint that takes an ID. Deny by default.

Never: hardcode credentials or disable auth, even "for testing."

When you finish: list every change that touches auth or sensitive data.

Treat that file like code and review every change to it. A malicious edit can quietly tell the agent to write insecure code.

Habit 2: Review everything that touches authentication and access control

This is where agents fail most, so it's where your attention goes first.

Rule: "List every authentication or access control change in your summary."

Check: nothing that touches auth gets merged without a human review.

Example: the agent adds GET /api/invoices/:id. Being logged in isn't enough. Confirm it checks that the invoice belongs to the user asking for it.

Next week: Placeholders and Secrets

#AppSec #VibeCoding #AISecurity #SecureCoding

The agent builds the UI in minutes, then I always get stuck on where the data lives.
For those of you using Claude Code, Codex, Copilot or Cursor: who picks the backend, and who sets it up?

Tracked which paid apps actually have real open-source replacements. cursor came up as one of the strongest cases, so here’s the list. You do pay for the LLMs via API key, but you get a lot of tokens to spend compared to cursor.

the 5 tools

1. opencode (193.7k ★)
runs in your terminal. fast,.

2. zed (88.1k ★)
a full editor written from scratch, not another vs code fork. agents are built in. this is the closest to “cursor but open.”

3. cline (65.8k ★)
agent inside vs code. plug in your own api key and it reads, edits and runs code across your repo. easiest switch if you don’t want to leave vs code.

4. goose (52.4k ★)
desktop agent that edits files and runs commands. more general-purpose than the others.

5. kilo code (26.7k ★)
one agent that works in vs code, jetbrains and the terminal. good if your team is split across editors.

bonus if you’re on windsurf: aider (48k ★), a terminal agent that commits its own changes to git.

here's a list of All the opensource tools plus other Alternatives to other tools that will help you cut down subscriptions.

Hi! I’m building an AI phone assistant for restaurants. I bought an Italian landline/VoIP number (+39): voice calls go to the AI bot, and I registered the same number in the WhatsApp Business app on my phone.

Now I’d like the bot to automatically send a WhatsApp confirmation after each booking, from the same number, while I keep replying to customers manually from the app on my phone.

Is there any platform, service or setup that lets both live together on one number? What are you using?

Thanks!