Composio for building AI agent platforms with integrations

We found Composio to be super useful for building AI agent platforms that needed integrations here at Plank . Also it has been fun to help contribute towards building the Composio platform.

On a post by Soham GanatraFounder @ Composio | Agent action infrastructure
DoorDash had to build an entire platform just to let AI agents use tools in production. That tells us so much about where the agent stack actually is. MCP made it much easier for agents to discover and invoke tools.
Read Soham Ganatra’s full post on LinkedIn 
  • Customers and partners
  • AI agents

Keep reading

Software architecture

DBOSify replaces Temporal Python with plain Postgres

Really cool work from Peter Kraft and Qian Li, PhD - DBOSify is a drop-in replacement for Temporal Python that uses Postgres instead of a Temporal server. This lets you run durable workflows, activities, signals, updates, retries, and recovery without needing any infrastructure except Postgres. The other project that took a similar approach was Absurd (github.com/earendil-works/absurd). Excited to try DBosify, hoping there's a Typescript version soon as well. DBOSify GitHub: github.com/dbos-inc/dbosify-py

Plank

Founders must pick between being a virus or a dinosaur

As a startup founder, you only have two paths. Be a virus or be a dinosaur - both are apex predators in nature. Path 1: Be a dinosaur. Your goal is to keep getting bigger and bigger. The idea is simple - you can keep upselling more things to your existing customers. Companies like Salesforce have executed this strategy well. Path 2: Be a virus. You stay laser-focused on a single product or line of business, and you keep your org and core team extremely small and lean. Cursor and Instagram are examples - both built massive businesses with tiny teams. There's no wrong answer. But you have to pick one.

Coding agentsSoftware architecture

Coding models should be trained for concept minimalism

I hope OpenAI and Anthropic include elegance and concept minimalism as a metric to train against in post training for coding models. These models require a lot of guardrails to be put in the harness else you end up with a cambrian explosion in concepts in your code very quickly. And once that happens, it is hard to backtrack. In the meantime, I recommend people to add a couple of these steps in your harness pipeline: - as one of the adversarial review steps, ask to count the number of new concepts added and critically evaluate if they are absolutely needed. - in systems that involve AI prompts code and software code, don't let the deterministic code be over-engineered. When in doubt, rely on the AI prompts vs hard-coded code. - be clear in your agents.md and claude.md that you like simplicity and elegance. In the coming days, I will share more about my harness where I have this working. In the meantime if you're interested, DM me and happy to show you.