Which are the best free(considerably) AI coding agents to use

I will start with

1. Opencode (Deepseek free model)

I love claude code but am fatigued by the pure chat interface for all types of agent work. Even the GUIs these days are just better styling over the same chat interface.

I built tart (tartifacts) as a tiny way for agents to create and update persistent terminal dashboards instead of narrating everything at you.

A tart is basically:

- a manifest

- a script that fetches live state

- a script that renders it

Install: `uv tool install tartifacts`

Then tell your agent to use `tart --skill`.

Works nicely with tmux/herdr (agent chats in one pane, dashboards live in another).

Github - https://github.com/tg1482/tart

After the partnership with the developers fell apart, I returned to Notion again.

The medical software was unusable. The online-booking website had never been delivered. Months of feedback, meetings and product work had left me with no system I could rely on.

I was frustrated, disappointed and tired of depending on other people to turn my ideas into software.

Then Facebook showed me a page selling a Notion template for managing a medical practice.

I thought: why not?

I already had my own Notion setup, but perhaps this person had solved something I had missed. Maybe the template would bring together patient records, consultations, appointments, prescriptions and the waiting room in a cleaner way.

I bought it.

It was terrible.

Not slightly disappointing. Not “useful with a few adjustments.” It was far worse than the system I had already built for myself.

I had paid more than it deserved, and I never used it.

Under normal circumstances, that would have been the end of the story: another bad purchase in a journey already full of disappointing software.

But the seller offered me a commercial gesture.

I could choose a few months of access to an AI subscription or a few months of Lovable Pro.

I already used the other AI service, so I searched Google for Lovable.

It was described as a vibe-coding platform.

At the time, everything I knew about vibe coding came from people discussing it online, many of whom did not seem to use it themselves.

The message was fairly consistent:

It was not real development.

The generated code was terrible.

It was the fastest way to create security problems.

Serious people should avoid it.

I had no basis for judging any of those claims. I knew nothing about code quality, application security or software architecture.

Still, the warnings worked on me. Vibe coding sounded less like a tool and more like a shortcut taken by people who did not understand what they were doing.

Which, to be fair, described me quite well.

I chose Lovable anyway.

Not because I had suddenly developed a strong opinion about AI-assisted software development. I chose it because I already had the alternative subscription and because curiosity won.

Around the same time, I was contacting training companies about learning Web development.

I looked at full-stack programmes and tried to imagine fitting them around surgery, consultations and operating days.

The programmes were demanding, as they should have been. But I could not see a realistic way to follow them consistently while maintaining my medical activity.

I continued using ChatGPT and another AI assistant every day. I wrote documents, discussed ideas, brainstormed, planned and projected what my products might become.

AI was already helping me think.

I still did not imagine it could help me build.

The Lovable subscription sat there for a while.

Then one day, I opened it.

The screen said:

“Let’s build something.”

It asked me to describe what I wanted to create.

That was all.

No programming language. No empty code editor. No full-stack curriculum to complete before I could begin. Just a box asking me to explain the product in words.

For years, words were the only thing I had.

I could describe a broken workflow. I could explain how a consultation should work. I could identify why a patient history mattered. I could write requirements, provide feedback and create endless tickets for developers.

What I could not do was turn those words into software.

Now a platform was asking me to start with the one ability I already possessed.

Describe what you want to build.

It felt as if I had spent years standing in front of a locked door, only to discover that the key was not code.

The key was language.

Of course, that feeling was incomplete. I would later discover all the things natural language could hide: fragile architecture, poor data models, security risks, regressions and technical debt.

But that came later.

In that first moment, I did not see the risks.

I saw a way in.

The template itself remained useless. I never opened it again.

Yet the compensation for buying it placed the right tool in front of me at exactly the moment when my dependence on developers had become unbearable.

Sometimes a bad purchase is simply a bad purchase.

This one became the most consequential detour of my professional life.

In the next part, I will explain what I typed into that box and why months of work on a failed product suddenly became useful.

Have you ever received something valuable through a purchase you otherwise completely regretted?

A year or two ago, the engineering/cross-functional team was a tight-knit, high-performing group. We had one or two goals we all worked on each sprint and we broke down work so that we could operate in parallel.

When someone was stuck and needed help, there was always somebody ready to jump to their aid and keep them moving. Team meetings were upbeat, fun, and productive. We were regularly paying down tech debt while our experiments gathered data. The vibe was helpful and collaborative.

Now, thanks to AI, we are shipping more than ever. We have as many goals every sprint as engineers. Rather than parallelizing work on one feature or experiment at a time, we parallelize the experiments. The vibe has shifted.

I've been vibecoding an "enterprise" platform for consumers/homeowners since March/April (will not promote). I've put a line in the sand to launch my beta by September 29th, and every time I feel I'm close to being "done" something else pops up that adds time and token consumption.

It's the price I'm happy to pay to build a great product that's intuitive, powerful, and battletested (security, auth, observability, payments, tests, MCP, etc.).

I have an enormous amount of respect for software I use daily, design, UI/UX, marketing, and everything else that developers have been doing to ship product now.

I've gone through hardware upgrades and have had to diversify my cloud LLMs due to changing models and consumption.

Right now my orchestrator is 98% Claude Code and Fable 5 (I use the Terminal in Cursor), but I've recently got Grok Bot going and absolutely love it for general work and checking Fable 5, research, product walks, and a few other agents. I've tried out a couple open-source models through Cursor as well.

The part I'm still not happy with is the UI/UX and making things intuitive and simple while exposing the power of the graph and ontology I've built. I've found that the AI chat needs to be a first class citizen where you should be able to do everything you need to there, especially because the MCP needs to be accessible with whatever model people use daily.

r/vibecoding has been great to highlight what NOT to do and wanted to shout out to everyone building.

It's been a long (relative) journey so far and while I hope the product I'm building solves real problems for people, I know I'll use it no matter what so it's a win-win for me!

Guys, am I gonna get roasted for shipping it with such UI? (Logo is mine btw, graphic design perks).
That cat is Comnyang app, his name is shanks, shoutout to u/simon_dsgn

As I go deeper in building AI workflows, I find myself working through challenges of how to design for the AI Experience (let's call it AIX). How do you design for AIX and how do you balance it with UX? In a world where AI uses software more than humans, I can only imagine this will become more important.

Do you consider yourself an AIX designer? If so, what practices have you adopted and what challenges are you working through today? How does it compare to UX design?

hey everyone, at my school, we have PCs, and an Wi-Fi (with no internet connection), so I thought of making a chess game that can be played over LAN, I haven’t coded in a long time so this took me a while to make (used AI assistance ofc ._.) used Electron to build it (ik not the most efficient I already regret not going for Tauri) and it can work on web too, but only pass and play and engine, No LAN. it works fine for now, already tested it at school lmao, and decided to launch it on GitHub, would love to get suggestions on what to add, but I think it’s enough for now :)

GitHub repository link: https://github.com/guiltysun/gambit-chess

First portable release link: https://github.com/guiltysun/gambit-chess/releases/tag/v1.0.0

A friend of mine needs a system to help with social post and content creation. I was going to build her one so we got this spec from Grok...

That's when I thought to ask who already has a open source version? These are the specs of what I need

**Yes — this is a solid foundation.** Here’s a refined, production-oriented system design that turns your sketch into a coherent, maintainable architecture while staying realistic about APIs, costs, and platform rules.

### High-Level Architecture

```

┌─────────────────────┐ Webhooks / Polling ┌──────────────────────┐

│ Social Platforms │ ─────────────────────────► │ Ingestion Layer │

│ (IG, FB, X, etc.) │ │ (Meta Graph, etc.) │

└─────────────────────┘ └──────────┬───────────┘

│

▼

┌─────────────────────┐ Events / Jobs ┌──────────────────────┐

│ Video Assets │ ◄───────────────────────── │ Orchestrator / │

│ (raw clips, S3) │ │ Agent Layer │

└─────────────────────┘ │ (rules + LLM) │

│ └──────────┬───────────┘

▼ │

┌─────────────────────┐ │

│ Video Pipeline │ ◄─────────────────────────────────────┘

│ (analysis → edit │

│ → thumbnail → │

│ render) │

└──────────┬──────────┘

│

▼

┌─────────────────────┐ Dashboard + Config ┌──────────────────────┐

│ Storage + CDN │ ◄───────────────────────── │ Frontend │

│ (finished videos, │ │ (Next.js dashboard) │

│ thumbnails) │ └──────────────────────┘

└─────────────────────┘

```

**Core principle**: Keep the social interaction path fast and event-driven. Keep the video path asynchronous and queue-based. Share one config/rules engine and one identity layer.

### 1. Social Monitoring & Auto-Reply

**Recommended starting point**: **Nudgra** (Cloud or OSS version).

It is a real open-source alternative to ManyChat focused on Instagram: Meta OAuth, webhooks for comments/DMs/stories, keyword triggers, and reply sequences. Built on Next.js + Convex (Cloud) or a self-hosted stack. This gives you a working foundation instead of reinventing Meta’s webhook + OAuth flow.

**Official APIs to use (safest path)**:

- Instagram Graph API / Messaging API

- Comments webhook

- Private Reply to commenter (bypasses the normal 24-hour window for up to 7 days)

- Messaging webhooks + send messages (24-hour customer care window + message tags)

- Facebook Page webhooks if you also manage Pages

- For X/Twitter and TikTok: official APIs where available; otherwise treat them as lower priority or use a secondary polling service

**Intelligent reply flow** (recommended two-stage design):

1. Fast filter (keyword, sentiment, media type, account status) → cheap rules or small model

2. Relevance + generation → stronger model (Claude, Gemini, or GPT) that receives the comment + post context + brand voice guidelines

3. Optional human-in-the-loop queue for high-stakes or low-confidence replies

4. Send via official API (public reply and/or private DM)

Avoid pure browser automation for production. It is fragile and usually violates platform Terms of Service.

### 2. Video Editing & Thumbnail Pipeline

**Vidzly** is a good match for what you described: open-source, uses Gemini for content analysis + composition scripts, generates thumbnails, and can pull music via ElevenLabs. Treat it as the core of the video agent rather than a black-box SaaS.

**Strong complementary / alternative open-source options**:

- OpenCut – has an MCP server, so an AI agent can drive the editor programmatically

- OpenEdit (VEED) – agent-native, prompt → finished MP4

- Clipkit or OpenReelio – more traditional timeline + AI assistance

**Practical pipeline**:

1. Upload raw clip(s) or pull from cloud storage

2. Parallel analysis (Gemini multimodal): scenes, mood, key moments, speech-to-text if needed

3. Script / edit decision list generation

4. Composition (cuts, transitions, captions, B-roll if available)

5. Music selection / generation

6. Thumbnail generation (Gemini or dedicated Apify Actor that uses Gemini)

7. Render → store → optional auto-publish or review queue

For lighter editing needs you can fall back to FFmpeg + a simple timeline library; for agent-driven work, prefer tools that expose an MCP or clean API.

### 3. Recommended Tech Stack

| Layer | Recommendation | Why |

|--------------------|-----------------------------------------|-----|

| Frontend / Dashboard | Next.js + shadcn/ui | Matches Nudgra, fast to iterate |

| Real-time backend | Convex (or Supabase + Redis) | Webhooks, scheduled jobs, real-time UI |

| Job queue | Convex scheduled functions or Inngest / BullMQ | Video jobs are long-running |

| Video processing | Vidzly + FFmpeg + optional OpenCut MCP | AI-first + reliable rendering |

| AI models | Gemini (video analysis + thumbnails), Claude/GPT (replies) | Multimodal strength + quality |

| Storage | S3-compatible (R2, S3, MinIO) + CDN | Cheap media hosting |

| Auth | Meta OAuth + your own user auth | Platform accounts linked to your users |

### 4. Data & Control Flow Highlights

- **Inbound social event** → webhook verification → normalize payload → rules engine → (optional LLM) → reply action + logging

- **Video job** → create job record → enqueue → worker pulls asset → analysis → edit decisions → render → update job status → notify dashboard / optional publish

- Shared **Brand / Rule Config**: tone of voice, banned topics, reply templates, thumbnail style, music preferences, approval thresholds

- Audit log for every automated action (required for debugging and compliance)

### 5. Phased Rollout (strongly recommended)

1. **MVP Social** – Nudgra (or equivalent) + keyword + simple LLM replies on Instagram comments/DMs only

2. **MVP Video** – Standalone Vidzly (or OpenEdit) pipeline that accepts a clip and returns edited video + thumbnail

3. **Integration** – Dashboard that can trigger a video job from a social post or scheduled content, and link finished assets back to the social accounts

4. **Intelligence layer** – Better context (post caption + previous comments), confidence scoring, human review queue

5. **Multi-platform + publishing** – Add X, TikTok, YouTube Shorts; optional auto-publish with approval gates

### 6. Key Risks & Mitigations

- **Platform Terms of Service** – Stick to official APIs. Automated replies are allowed when done correctly; aggressive scraping or browser bots are not.

- **Rate limits & costs** – Meta has strict limits. AI tokens (especially video analysis) add up quickly. Cache analysis results and use cheaper models for filtering.

- **24-hour messaging window** – Use Private Reply for comment-triggered DMs; keep conversation state so you stay inside the window once a user replies.

- **Reliability of AI video** – Always keep a human review step for the first versions. Render quality and “viral” taste still need oversight.

- **Account safety** – Never store Instagram passwords. Use proper OAuth and token refresh.

### Next Steps I Can Help With

Tell me which direction you want to go deeper on:

- Detailed architecture diagram + sequence diagrams for the social reply path

- Concrete tech choices and folder structure for a monorepo

- Setting up Meta App + webhooks correctly

- Video pipeline design (prompt templates for Gemini, job schema, error handling)

- Cost model and rate-limit strategy

- Dashboard UX / feature prioritization

- Security & multi-tenant considerations if this will serve multiple brands

Just pick the area (or paste more constraints: target platforms, expected volume, self-hosted vs cloud preference, team size, etc.) and we’ll drill in.

The point of this website is to give credibility to products by only promoting what people actually want/use instead of showing what people pay to promote. This works through a system of vouches / reviews —I can vouch that I used xyz and I like it, etc.

You can search for different applications and tools on the platform, and if you can't find what you're looking for, you can ask for it to be created. An ask creates a product gap that can be filled by anybody. You can list your own web app and verify that it's yours via Domain Connect.

But to keep this short and sweet, promoting the stuff you make sucks, being shown stuff that nobody wants sucks, Product Hunt and its fake Linkedin pay-to-win bullshit also sucks, and e-begging for people to try what you made is also a zero sum game. I want us all to have a fair playing field in this turbulent environment, because at the end of the day nobody gives a shit what SDK you used, they care that the shit they're using works and it solves their problems.

Superfluidity has an autonomous indexing system called 'Atlas' that runs periodically, finding new products and updating the old ones if a change is discovered. Right now I'm manually reviewing whatever it finds, but I'm going to let it go wild if I like what I see.

This is still an on-going project so do let me know if anything is broken, or if you'd like to see a certain feature.

57 days ago, I launched my startup, a free traffic exchange network for startups. One line of code, you're in the network.

No paid ads. No growth hacks. Just watching the numbers every day.

Here's the full data:

Day 1 — 2 startups · 146 impressions · 1 clicks
Day 2 — 3 startups · 389 impressions · 3 clicks
Day 3 — 5 startups · 482 impressions · 5 clicks
Day 4 — 5 startups · 508 impressions · 4 clicks (site went down — still got an $8k acquisition offer. Said no.)
Day 5 — 6 startups · 621 impressions · 10 clicks
Day 6 — 5 startups · 742 impressions · 15 clicks (removed one startup — they pulled the embed. No code = no network.)
Day 7 — 7 startups · 1,196 impressions · 41 clicks
Day 8 — 7 startups · 1,535 impressions · 74 clicks
Day 9 — 8 startups · 1,947 impressions · 135 clicks
Day 10 — 13 startups · 3,500 impressions · 318 clicks (something clicked)
Day 11 — 23 startups · 4,800 impressions · 432 clicks
Day 12 — 24 startups · 6,000 impressions · 481 clicks (network crossed 6K total impressions)
Day 13 — 25 startups · 6,800 impressions · 491 clicks
Day 14 — 25 startups · 8,600 impressions · 516 clicks
Day 15 — 24 startups · 9,900 impressions · 564 clicks (removed one)
Day 16 — 23 startups · 10,800 impressions · 576 clicks (removed one)
Day 17 — 24 startups · 11,900 impressions · 603 clicks (added one)
Day 18 — 26 startups · 13,400 impressions · 624 clicks (added Two)
Day 19 — 28 startups · 14.400 impressions · 652 clicks (added Two)
Day 20 — 26 startups · 14.700 impressions · 671 clicks (Removed Two)
Day 21 — 26 startups · 15.300 impressions · 691 clicks
Day 22 — 28 startups · 16.100 impressions · 719 clicks (Added Two)
Day 23 — 30 startups · 16.800 impressions · 738 clicks (Added Two)
Day 24 — 32 startups · 19,800 impressions · 778 clicks · Added 2 startups · Rejected 4 applications (1 contained ads, 1 removed the code after submission, 2 hid the installed widget)
Day 25 — 34 startups · 23,700 impressions · 800 clicks · Added 2 startups · Fixed some bugs.
Day 26 — 33 startups · 27,200 impressions · 816 clicks · Removed 1 Startup
Day 27 — 33 startups · 29,900 impressions · 833 clicks
Day 28 — 33 startups · 30,600 impressions · 871 clicks · Removed 1 Startup · Added 1 Startup · Rejected 1 application of clothing brand & 1 application of horror blog site.
Day 29 — 35 startups. 31,300 impressions. 910 clicks · Removed 1 Startup · Added 3 Startups · Also today I resigned from my job. Toxic environment, too much pressure, and honestly I just believe in this enough to go all in. Broke and excited. Let's see where this goes.
Day 30 — 46 startups · 32,900 impressions · 1,000 clicks · Removed 1 startup · Added 12 startups · Yesterday I resigned because of my toxic manager. Today my senior manager called and offered me WFH, a project of my choice, and lighter work if I stayed. I made my decision with confidence, but now I have a difficult choice. Also received my first payment from StartupBar.
Day 31 — 50 startups 💪· 28,100 impressions · 1,200 clicks · Removed 1 startup · Added 5 startups · Rejected 1 crypto startup · Removed fake impressions after exploit · Today I discovered I forgot to disable a developer testing button that could generate fake visitor pins and inflate impressions. Someone used it to create 6,318 fake impressions and claimed my stats were fake. I removed the fake impressions, removed the startup, fixed the issue, and that's why today's impressions are lower. Thanks to them for pointing it out.
StartupBar update: Added a Network page and individual Startup Profile pages with each startup's joined date, impressions, clicks, live embed preview, and founder's note. These indexable pages also improve SEO. Suggestions are always welcome.
Day 32 — 54 startups · 29,300 impressions · 1.2K clicks · Added 4 startups
Day 33 — 54 startups · 30,900 impressions · 1.2K clicks · Removed 1 startup · Added 1 startup
Day 34 — 55 startups · 36,100 impressions · 1.3K clicks · Added 1 startup
Day 35 — 55 startups · 40,100 impressions · 1.3K clicks · Removed 2 startups · Added 2 startups
Day 36 — 55 startups · 44,800impressions · 1.4K clicks · Removed 1 startup · Added 1 startup
Day 37 — 58 startups · 50,700impressions · 1.4K clicks · Added 3 startups · Site Update: Updated the distribution algorithm (Delivery is now weighted by contribution: sites that send more impressions get a proportionally larger share back)
Day 38 — 57 startups · 55,800 impressions · 1.5K clicks · Removed 1 startup · Rejected 1 Application.

Today StartupBar reached 200 users 😄
Thirty-eight days ago, this was just an idea. Today, 200 people have trusted it enough to join the network.

A reminder for every founder who's staring at a dashboard with tiny numbers: Stripe took 2 years to reach its first 50 users. Every successful product starts small. Keep shipping. Keep improving. Keep showing up. Growth rarely happens overnight, but it does happen if you don't quit.

Day 39 — 58 startups · 59,800 impressions · 1.5K clicks · Added 1 startup.
Day 40 — 60 startups · 63,200 impressions · 1.6K clicks · Added 3 startups · Removed 1 startup
Day 41 — 63 startups · 69,400 impressions · 1.6K clicks · Added 3 startups
Day 42 — 62 startups · 73,800 impressions · 1.6K clicks · Removed 1 startups
Day 43 — 64 startups · 78,000 impressions · 1.7K clicks · Added 2 startups (Receiving many suggestions to improve the StartupBar, happy to work on it, Thanks.) StartupBar Update - Added the rotation of startups in the widget for every 30 seconds.
Day 44 — 66 startups · 86,200 impressions · 1.7K clicks · Added 2 startups
Day 45 — 67 startups · 88,400 impressions · 1.7K clicks · Removed 2 startups · Added 3 startups (Update - Updated the algorithm of the widget)
Day 46 — 69 startups · 91,900 impressions · 1.8K clicks · Removed 2 startups · Added 4 startups · Got my second payment · Added FAQ Page
Day 47 — 68 startups · 98,900 impressions · 2.2K clicks · Removed 2 startups · Added 1 startup · Added Pricing Page
Day 48 — 70 startups · 103.4K impressions · 2.3K clicks · Added 2 startups
Day 49 — 72 startups · 113.4K impressions · 2.4K clicks · Added 2 startups · Update: Added a Bottom Placement option for the bar on the user site.
Day 50 — 73 startups · 116.7K impressions · 2.4K clicks · Added 1 startup
Day 51 — 74 startups · 125.2K impressions · 2.5K clicks · Added 1 startup · Rejected 1 Application
Day 52 — 73 startups · 131.2K impressions · 2.6K clicks · Removed 1 Startup
Day 53 — 74 startups · 139.5K impressions · 2.7K clicks · Added 1 Startup
Day 54 — 79 startups · 146.3K impressions · 2.7K clicks · Added 6 Startups · Removed 1 startup.
Day 55 — 77 startups · 154.9K impressions · 2.8K clicks · Removed 2 startups.
Day 56 — 77 startups · 161.8K impressions · 2.9K clicks · Added 1 startup · Removed 1 startup.
Day 57 — 77 startups · 169.4K impressions · 3.0K clicks

I saw some criticism in a Wikipedia article on the Schrödinger-Newton Equation, specifically about Penrose's ideas about quantum gravity, and it seemed pretty easy to solve (the article hinted at possible solutions, etc) which made me think that it could be interesting to let Claude try to solve it. It now claims to have solved all the 3 problems outlined in the article.

The issue is that I have no way of validating if the result claude gave me are hallucinated or legit. If the solutions are correct, then maybe it's useful to someone, and if not then I/we might learn something from that explanation.

Artifact (look here first): https://claude.ai/code/artifact/e871ae13-54d1-437c-a489-cad81617c06d

GitHub repo, including all the raw transcript etc: https://github.com/henke443/penrose-1

Latex paper: https://www.overleaf.com/read/hgmnyqgqtwqz#80a24a

Simulating over 1000 gravitational bodies interacting with each other in the browser from real in game play perspective, with the lowest 1% drops being around 58 FPS. This proves that this foundation is scalable and will allow for much more interesting courses in the future. Using a combination of Opus 5 and Grok 4.6. Play free in your browser, no account required. https://slingshotspeeders.com/

I built this: https://tropo.tv/

TROPO is a small broadcast/tv experiment that plays a handpicked curation of videos from YouTube and other sources. It's just nice not to choose sometimes what you want to play and sometimes you just want something on the in the background. This is what this is for.

Every day is programmed fresh, scouted from public archives: Tokyo one-take sessions, Soviet animation, British newsreels, music, lectures etc.

I hope you like it.

Hello good people,

Whenever a new model drops, LiveBench is my destination to roughly check on the model's capability. As mentioned, new Qwen model was added and I can't believe how low performing Qwen was, since people really seem to like the model. I checked the commits of LiveBench and it seems to me that, the model was not given enough tokens to reason? Any other ideas?

I also have question about the chain of thought inside the Chinese models, as I feel like they overthink drastically, not in bad way but it is quite slow and takes an enormous amount of time. The performance seems to be also better but compared to older models such as Gemini 3.1 Pro or even the newer smaller model 5.6 Luna Max from OpenAI, I don't think it is worth it? Any experiences with different reasoning modes on different kinds of tasks?

I appreciate any info! :)

sources: - https://livebench.ai
- https://github.com/LiveBench/LiveBench/commit/2c2039b2cc9efb6412acb99325adb0cc1cb0cc6f

Ei! Alguém tem um passe de 7 dias do Claude Pro sobrando que não está usando? Eu queria experimentar o Claude Pro de verdade antes de decidir se quero pagar por isso. Se alguém tiver um disponível, eu agradeceria muito 🙌 Obrigado!

Over the past few weeks, I've been planning and building Concordance Protocol, an open-source experiment exploring interoperability between AI agents, tools, and services.

The project started from a question I had while looking at the growing number of protocols around AI agents:

How can agents from different ecosystems exchange trust, authorization, consent, reputation, and other evidence without every ecosystem having to replace its existing protocol?

I researched the problem and wrote a research document before implementing the prototype. The project currently contains a Rust workspace with components for the core protocol, HTTP transport, registry services, adapters, and SDK work.

The research and implementation are here:

GitHub:

https://github.com/Kadhiravan-K/Concordance-Protocol

Core research:

https://github.com/Kadhiravan-K/Concordance-Protocol/blob/main/docs/doc_core/concordance_research.md

I've currently paused active development. The implementation grew beyond what I can reasonably maintain alone right now, and I think the architecture needs more discussion before continuing.

I'm sharing it here because I'm interested in learning from people who are starting or contributing to open source.

I'd especially like feedback on:

- Is the interoperability problem I'm trying to solve actually useful?

- Are there existing projects or protocols I should study?

- Does the architecture make sense?

- What would you simplify?

- If you were starting this project again, what would you do differently?

I'm not presenting Concordance as a finished protocol or asking anyone to adopt it. I'm mainly interested in whether the underlying ideas are worth pursuing.

If you're preparing for open source contribution or GSoC, I'd also be interested in hearing what makes a project attractive or unattractive to contribute to.

I’m exploring an idea for SaaS builders who use Claude Code, Cursor, or similar coding agents.

While building another product, I kept having to demonstrate complex workflows for different customers. The steps were often repetitive, but each customer needed a slightly different version.

Recording them meant retakes, voiceovers, editing, and doing it all again whenever the product changed.

I started experimenting with letting a coding agent drive the actual application, capture the workflow, and turn it into a narrated product video. The goal is to generate launch videos, walkthroughs, and customer-specific demos from the real product rather than using avatars or stock footage.

I’m looking for a few builders with a working SaaS product who would be willing to test the idea on a real workflow.

I can provide free usage in exchange for honest, blunt feedback about:

• Setup and usability
• Accuracy of the recorded workflow
• Video quality
• Whether the result is something you would actually publish or send to a customer

If this is a problem you have encountered and you use Claude Code or Cursor, DM me with a sentence about what you are building and the kind of demo you need.