DealForge autonomously sources, scores, and writes investment memos on venture deals. Stop manually hunting.

1,180+ deals tracked  ·  22 AI investment memos  ·  Updated daily

← Back to leaderboard

A CLI that writes its own integration code

Show HN: A CLI that writes its own integration code

72 AI Score
Show_hn other Added Apr 14, 2026

Details

Sector
other
Total Funding
$0
Last Round
$0

About

We run superglue, an OSS agentic integration platform. Last week I talked to a founder of another YC startup. She found a use case for our CLI that we hadn&#x27;t officially launched yet.<p>Her problem: customers wanted to create Opps in Salesforce from inside the chat in her app. We kept seeing this pattern: teams build agents and their users can perfectly describe what they want: &quot;pull these three objects from Salesforce and push to nCino when X condition is true&quot;, but translating that into a generalized hard-coded tool the agent can call is a lot of work and does not scale since the logic is different for every user.<p>What superglue CLI does: you point it at any API, and your agent gets the ability to reason over that API at runtime. No pre-built tools. The agent reads the spec, plans the calls, executes them.<p>The founder using this in production described it like this: she gave the CLI to her agent with an instruction set and told it not to build tools, just run against the API. It handled multi-step Salesforce object creation correctly, including per-user field logic and record type templates.<p>Concretely: instead of writing a createSalesforceOpp tool that handles contact -&gt; account -&gt; Opp creation with all the conditional logic, you write a skill doc and let the agent figure out which endpoints to hit and in what order.<p>The tradeoff is: you&#x27;re giving the agent more autonomy over what API calls it makes. That requires good instructions and some guardrails. But for long-tail, user-specific connectors, it&#x27;s a lot more practical than building a tool for every case.<p>Happy to discuss. Curious if others have run into the &quot;pre-defined tool&quot; ceiling with MCP-based connectors and how you&#x27;ve worked around it.<p>Docs: <a href="https:&#x2F;&#x2F;docs.superglue.cloud&#x2F;getting-started&#x2F;cli-skills" rel="nofollow">https:&#x2F;&#x2F;docs.superglue.cloud&#x2F;getting-started&#x2F;cli-skills</a> Repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;superglue-ai&#x2F;superglue" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;superglue-ai&#x2F;superglue</a>

AI Score Reasoning

Superglue addresses a major bottleneck in the agentic AI space by moving from static, hard-coded tools to dynamic API reasoning. While early-stage, the validation from a YC peer and the focus on the 'long-tail' of custom enterprise integrations suggest strong product-market fit potential in a rapidly growing sector.

Source

Show_hn — View original →