Show HN: Clink – Bring your own CLI Agents, Ship instantly

Show HN: Clink – Bring your own CLI Agents, Ship instantly clink.new...

Clink lets you use the coding agents you already pay for (Claude Code, Codex CLI, Gemini CLI, Z.ai GLM) to build → live-preview → ship apps in an isolated container.

No token purchases, no extra cost for coding. Just link your existing Claude/OpenAI/Gemini account and start building and deploying instantly.

Why we built this:

Claude Code is our go-to for coding, but it lacked preview + deploy capabilities. We didn't want to pay Lovable again just for that.

Different agents excel at different tasks - Claude Code for versatility, Codex for complex work, GLM for speed. We needed one platform to leverage them all.

CLI agents offer more freedom than traditional web builders. We wanted to unlock their full potential with proper dev tooling.

What it does:

- Prompt → Build → Live → Deploy - The fastest path from idea to live website. Deploy for free.

- BYO Subscription - Use your existing plans efficiently (Claude Code $20 = 10x Lovable $25 usage, GLM $3 = 3x Claude Code $20)

DEV Mode (Beta):

- Multi-stack support - Build with Node, Python, Go, Rust and deploy containers to public URLs instantly

- Repo imports - Upgrade and deploy your existing projects across any stack

Links:

- Clink: https://clink.new

- OSS origin (Claudable, ~2.8k): https://github.com/opactorai/Claudable

We'd love any feedback, bug reports, or stack requests - we iterate fast and read every comment.

Pretty cool! I see you support deploying to Vercel. Any plans to support other hosts?

aaronSong · 2 months ago

Ah, Vercel is what we use in the open source Claudable version! For Clink, we currently deploy static/frontend to Cloudflare Pages and full stack apps to Railway, both work great for different use cases. We're definitely interested in adding more deployment targets. What hosting platforms would you prefer to see? we can prioritize based on what the community needs most

WildGreenLeave · 2 months ago

I'm part of a new hosting platform focusing on the European market, would you be open to discuss what you are looking for and see if we can become partners? Obviously no strings attached :) If so, please drop me an email zander@ploi.cloud

Edit: Forgot to add my thought; I think you should be more clear about what Clink does compared to other software like Claude Code. The building demo's to me (a developer/devops person) are cool but my first thought was 'Why would I use this over Claude Code'? And only in this thread I saw the USP for Clink which makes perfect sense for non-techies!

harry7922 · 2 months ago

This is super cool. Love the idea of using the agents I already pay for instead of signing up for yet another subscription. Curious how you're handling sandboxing and dependency isolation between builds? That's usually the hardest part when trying to make build -> preview -> deploy feel seamless for multiple runtimes.

sandboxing is indeed the trickiest part.

We're using Daytona for development environments, which gives us proper isolation out of the box. Each build runs in its own sandbox workspace with full container isolation, so there's no cross-contamination between projects or users.

mentalgear · 2 months ago

Interesting, but Daytona appears to be a cloud-only sandboxing system. Yet your copy states: "coding agents run locally"; so unless I'm missing something, this is at least misleading, since the code/sandboxes need a Daytona cloud account.

cba18jy · 2 months ago

Interesting use case.

I used many vibe coding apps and also cli agents. This could serve as a useful testbed for evaluating different CLI agents. Does the system support switching between multiple agents, or is that not currently implemented?

For now, we support switching between models within the same provider, but we're currently adding the ability to switch providers mid-session. We're working on agent switching similar to Cursor's LLM switch so you can seamlessly move between Claude Code, Codex, GLM, etc. during development. We're also exploring auto-switching based on task type, our model would automatically select the best agent for each task. For example, using Opus for frontend work and Codex for backend refactoring. The goal is to leverage each agent's strengths without you having to think about it.

willchen · 2 months ago

Really interesting project! I tried it last week and ran into same errors and today I tried it again and it worked.

I'm curious how the Clink desktop app connects to the web app. Is it sending some kind of oauth token so you can use call Claude Code, etc, on behalf of the user?

FWIW, I created an open-source project in this space https://github.com/dyad-sh/dyad/ and it's great to see people trying different approaches :)

Oh I really like your product! you're right about how it works. the desktop app sends oauth tokens to connect to the cloud infrastructure. dyad looks really cool, love the local-first approach. it's exciting to see so many different takes on this space right now. what are you focusing on with dyad these days?

thanks! we recently added MCP support so we're figuring out how to make it easier to find & add the right MCP tools for your use case :)

cetinsert · 2 months ago

We do the same over at https://rtcode.io with "Agent Share"!

Instead of containers and "stacks", we use the web platform with vanilla HTML, CSS and JS (front-/back-end in 1 place)!

Deployments go to Cloudflare!

See examples at https://new.rt.ht – service workers you can edit live in the playground with URL imports of ESMs, get deployed as Cloudflare Workers!

ant1894 · 2 months ago

How does this differ from existiong app builders? I've seen quite a few similar projects.....

Most app builders use lightweight coding agents and infrastructure. we're leveraging the full power of CLI agents (Claude Code, Codex, etc) as the engine, which means you can build with any frontend stack like react/next/svelte and any backend like fastapi/nestjs/flask/ruby, then deploy everything as a container. this is live in beta now. also, if you have an existing project, say a python ML model, you can import it and add a frontend to create a complete deployable service. the CLI agents are just way more capable than typical app builder agents, and we're giving them the infrastructure to match that capability.

Other than having a GUI, how is this different from something more established like openCode ?

Good question! while we use CLI agents as the coding backbone, our focus is really on the application building experience: live preview and seamless deployment. The key difference is that we give you an isolated sandbox container where you can see your app running instantly, then deploy it with one click. so instead of just getting code output, you get a runnable application that you can interact with and ship immediately. openCode is great for pure coding tasks, but we're optimized for the full build-preview-deploy cycle.

Thanks for the clarification, and kudos to you for making it open-source!

dohyun1m · 2 months ago

I’ve actually used claudable before, and happy that you guys just made an cloud hosted version of it. But how are you handling all those server costs? Since it’s not just a local open source project right now, the fees might be kinda expensive.

thanks for using claudable before! for server costs, the sandbox previews have auto-stop functionality so the actual runtime is pretty short. keeps costs manageable. for deployments, cloudflare static hosting is basically free, and we only charge a small fee for custom domains since that's where we have actual costs. the beauty of leveraging existing platforms is that we don't have to run expensive infrastructure ourselves. most of the heavy lifting (the actual coding) happens on your CLI agent subscription, not our servers!

jhack · 2 months ago