June 20, 2026

### Minor Changes - a94715f: Forward `userId` when creating trigger instances so trigger 2FA flows can verify connected account ownership. - 44e5458: Remove the legacy `composio.tools.createCustomTool(...)` in-memory registry API. Use Tool Router custom tools via `experimental_createTool`, `experimental_createToolkit`, and `composio.create(..., { experimental: { customTools, customToolkits } })` instead. ### Patch Changes - 22a9171: Defer telemetry batch and error sends so instrumentation does not wait for telemetry network requests before returning SDK results or rethrowing SDK errors. - 93b67e8: Fix automatic file upload/download substitution for file schemas that accept either a single file or a list of files. The file modifier now selects composed-schema branches by runtime value shape, so `anyOf(file, array )` uploads or downloads each file when the tool receives a list while preserving existing single-file behavior. - b69cef1: Tolerate dangling `$ref` pointers in tool schemas the Composio API ships without a matching `$defs` entry. Some toolkits (e.g. `GMAIL_FETCH_EMAILS`) emit `outputParameters` with `"$ref": "#/$defs/FetchEmailsResponse"` while never declaring a top-level `

Solo dev from Japan here. Not Tokyo, not really in any startup scene, just building from a more rural area. I launched a translation app in Oct 2025 and it recently passed $10k MRR. took around 8 months. proof: https://profile.stripe.com/nani/Ae1hNCkN No ads, no paid referral thing, no big launch. mostly just posting progress on X and people sharing it. Just writing down stuff I noticed I spent way too much time before launch wondering, “does anyone actually want this?” Most of my supposedly realistic predictions were wrong anyway. Sometimes you just put it out there and it does better than you thought. I made a small tool to solve my own problem. It started as something just for me, then I turned it into a product. Turns out other people had the same problem. You don’t always need a big vision. Don’t ship something that’s obviously bad just for the sake of shipping. People have limited attention. Once they decide your app is useless, it’s pretty hard to win them back. Your landing page should make it obvious what the product does. That matters more than some vague, clever-sounding headline. People are tired of reading landing pages. Even better if they can try part of the product

Hey guys, I thought I share my story because I want to show that for most people the journey is hard and that it takes time to really get going. I structured the post a little to give some good overview. The start (early 2024) I met two guys looking for a developer to build their SaaS idea for marketing agencies. They already ran a successful agency so I figured they knew the problem very well. Over the next 6 months I built it alongside my full-time job. Launch early traction We ran a beta, collected feedback, launched officially in January 2025 and hit $1k MRR in the first month. Then reality hit. We had priced too low and attracted the wrong users. We had added too many features, but users only cared about one we d almost added as an afterthought. Churn went up fast. Pivot the grind I quit my job and went all in. Had a lot of conversations with customers and we pivoted to a completely different direction and moved to high-ticket pricing. We tested everything on onboarding: 14-day trials with credit card to demo calls option to 10-day no-card trials to demo calls only. At peak we were spending $2k/month on Google + Meta ads and pulling in $6,500 in revenue. But the product had be

Jun 19 , 08:45 UTC Resolved - This incident has been resolved. Jun 19 , 08:37 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 19 , 08:17 UTC Investigating - We are currently investigating this issue.

Mark Nottingham lays out when well-known endpoints are appropriate, and warns against using them as a prestige signal or a shortcut when a real URL would work better.

Comments