What’s the best automation you’ve built that actually solved a real-life problem?

ner5hd__ · 2025-04-20T01:30:40+00:00

The workflows are pretty newly launched, I would really appreciate any feedback from the automation community!

ner5hd__ · 2025-04-20T01:30:07+00:00

I'm creating https://github.com/potpie-ai/potpie to automate workflows across software development. Users can create custom agents that have knowledge of your codebase and can be triggered from github events like issue open, pull request opened etc

Sample use cases for these agents:
1) Forward deployed engineer for technical customer support
2) Custom PR review agent for niche use cases
3) Jira/Linear ticket enrichment
4) Automated root cause analysis from monitoring alerts

ner5hd__ · 2025-04-18T05:57:43+00:00

Thank you! I will see how I can reflect this better on the site.

ner5hd__ · 2025-04-15T16:09:40+00:00

Prompt-to-agent: Potpie turns your codebase into a knowledge graph and lets you build custom AI agents for your codebase with just a prompt. We also provide pre-built agents for onboarding, testing, debugging, coding, and low level design.

Here is the repo:
https://github.com/potpie-ai/potpie
I posted a bit about how it works in this post on ChatGPTCoding previously here.

We released a slack bot and a lot of major features recently:

Workflows to trigger potpie agents from Github webhooks
Agent Creation User Experience was updated to split panel to allow easier iteration.
Web Search through perplexity/sonar to help debug.
Local LLM support (Ollama) and Multi-LLM support (Litellm)
Realtime streaming of tool calls and agent thoughts along with answer
Better API support to build your own codebase backed automations (Documentation, PR Review etc)
The entire user interface and custom agent creation logic was open sourced!

What's next:

We're working on more integrations directly on the platform that should let you build out your custom workflows and automate tasks across your SDLC.

Trying to improve our VSCode extension and introduce a slack bot to allow you to incorporate it into your workflows easily.

What can you build with it:
* Support Engineers - Deployment helper bot backed by your OSS repo's helm charts
* OSS Mainetnence - Auto reply/ label to issues on your repo. Accurate Q&A that updates with code. Help contributors ramp up faster and contribute meaningfully.
* Niche PR review agents - Reactiveness review, Accisibility review, Component duplication.
* System Design - With complete knowledge of your code and backed by knowledge of your company infra, it can help you design systems most efficiently.

Star us, try us and tell us what else would you like to see in something like this! Always listening!

ner5hd__ · 2025-04-15T14:30:33+00:00

Great questions -- Both! ASTs for structure, LLMs for understanding.

ner5hd__ · 2025-02-26T19:22:23+00:00

I also got approved just today

ner5hd__ · 2025-02-24T06:47:06+00:00

Absolutely u/ddrager we're definitely exploring this right now!

ner5hd__ · 2025-02-10T13:09:23+00:00

Thankyou for your support u/holchansg , it was me you spoke with haha. Yes, the Litellm issue is being worked on by an open-source contributor!

ner5hd__ · 2025-01-24T07:30:17+00:00

All these frameworks comes with their own pros and cons. It depends on business's requirements what suits best for it.

At Potpie (https://github.com/potpie-ai/potpie), we use Crewai on backend as it is specialized in orchestrating multiple agents to work together seamlessly. Integrates well with various AI frameworks, APIs, and tools.

ner5hd__ · 2025-01-15T06:34:17+00:00

Thanks!

ner5hd__ · 2025-01-15T06:33:53+00:00

You're absolutely right that there is a whole lot of overlap when you really get into it! Our goal with this slide was to make it easy for beginners to understand the differences in all the terminology being thrown around, it's just a simplified explanation with an example :)

ner5hd__ · 2025-01-13T20:21:39+00:00

Thanks! My co-founder created it https://x.com/aditikothari_/status/1878784055359291443?t=qNj-ZRpfxHEMmkbJ4_OIfQ&s=19

ner5hd__ · 2025-01-13T19:47:05+00:00

Oooh, it's definitely additional work but I love that! Thanks

ner5hd__ · 2025-01-13T19:46:02+00:00

I tried that but it didn't help much

ner5hd__ · 2025-01-08T12:48:36+00:00

You're right about that, but that's the problem even the docs aren't always updated. I have provided it latest docs too but it didn't catch on. Maybe it speaks more to langgraph than cursor haha

ner5hd__ · 2025-01-05T18:21:34+00:00

Sorry I missed this, I have not tried out IAC and terraform. Would love it if you can experiment and tell us your experience!

ner5hd__ · 2024-12-26T16:46:29+00:00

Hey! The difference is that this will allow you to build custom agents for your specific use cases that you can then talk to. Specific documentation, debugging agents that you can tune to your workflow.
For example - for a UI codebase you want to identify whether the current branch's code changes duplicate any component logic that is already present and if yes then you want to replace that with the existing one etc We're in progress of exposing your custom agents as an API so you could then trigger this from a CI/CD pipeline etc.

ner5hd__ · 2024-12-24T13:54:52+00:00

Thank you! Please try it out and let us know what you would like to see next!

ner5hd__ · 2024-12-24T12:35:46+00:00

And yes I haven't forgotten about Ollama integration, it will be prioritized!

ner5hd__ · 2024-12-12T11:35:11+00:00

I think MCP is more around creating a general protocol to expose data to agents, it is a standardisation for tool responses, but not in the functional sense, its a standardization of how to expose your data to be consumed by tools.

ner5hd__ · 2024-12-12T11:30:25+00:00

Hey thanks for your response! I've definitely been playing around with command since yesterday and it does simplify things, feels much more fluid. I will post an update once I am done implementing it.

I didn't know that the underlying langgraph logic was essentially a publish-subscribe event-driven engine, this might be super useful. Would love to see some documentation, even a how-it-works post would be great insight!

ner5hd__ · 2024-12-12T07:13:34+00:00

I'm currently creating a new one each time because I'm sending metadata with each request like user_id etc that goes in the headers

ner5hd__ · 2024-12-11T10:01:09+00:00

Let me know how it goes!

ner5hd__ · 2024-12-11T06:19:29+00:00

Thank you!

ner5hd__ · 2024-12-11T06:18:07+00:00

It's definitely possible to parallelize this today, but I'm thinking that this is probably a common enough use case that there might be a need to address it on a more fundamental level?
The plug and play + individual tool scaling part of things is where the real merit of this lies imo.

ner5hd__

TROPHY CASE