Agent for the Agentless: Weftly now has a chat client
Weftly has always been MCP-first: transcribe, find clips, cut vertical shorts, publish platform. Each tool call is paid per job, no subscription, and no sign-up. That works great if you already have Claude or Cursor set up. If you don't, "install an MCP host first" is a rough answer to "can I get a clip out of this interview?"
So we brought the chat client back. Open chat.weftly.ai, drop in a file, say what you want. No setup, no account, no connector config. The tools underneath are the same ones your agent would call. The chat app is just one client, and the interface is yours to pick. Details about our purpose-built Discord client app are in the comments
Free jobs through September with promo code PROD-HUNT-CHAT.
What would you build on it?
Replies
Worth adding some context on why we frame this as a client rather than the interface.
Mike, our editor at The Woven Record, needed branded clips. Branding wasn't in Weftly's pipeline yet, and he shouldn't have to wait on us to ship it or on me to run a Claude skill to do it for him. So, to unblock him, we built `weftly-hermes`: a Discord app backed by a container running hermes and ffmpeg. He posts a clip in a channel, it comes back branded. I use it now too, because it's a dead simple (and fun) way to get branded clips.
It took part of a weekend. It is not a product. It is a client, built for Mike's workflow, and to keep our team's branding consistent.
Those custom branding skills are coming to Weftly proper soon. But hermes made the real point first, which is that nobody had to ask permission to build it. Weftly's tools were already there and already callable. The interface was the only thing missing, and because Weftly's interfaces are well defined, building on top of it as a Discord or Slack app is fairly easy.
Curious what clients people would want. A CLI? A Slack bot? A form your clients could use without knowing what a job costs?