Show HN: Coyote – Wildly Real-Time AI

It's like you're talking to a real person. No stop buttons, no waiting. Interrupt, add details, or change direction anytime. Just like a natural conversation.

Context here means any additional information.

For me this cancel and restart thing e.g. in ChatGPT is so annoying. Plus most chat tools don't even get your second message if you send it before they finish, so you're locked into waiting. And in this coyote approach I can just add more context if I forgot something and it picks it up without cancelling what's already running. It' s more like talking to human.

Fully understand the WhatsApp part. Do you use any other communicators? Discord, Signal or something else? We are looking for more "interfaces".

When it comes to async that's exactly what we are trying to "solve". Right now models are built in a way that they expect tool results right after tool calls.

We are building datasets and a model with asynchronous interface as it's core. https://huggingface.co/qforge/Qwen3-14B-AT you can read more about it here.

For tooling attached to it right now we are using Pipedream integrations and are planning to move to an open source public solution configurable by users so u can set whatever you want.

So imagine you have a single chat interface that steers a fleet of other agents in the background for code. But not by handing off the memory but navigating the tasks in an async way.

Right now it can: - handle real tasks in the background — emails, calendar stuff, research, finding info, organizing data - chat naturally without feeling like you're talking to a bot - remember context and keep conversations flowing - work with integrations (gmail, calendar, docs, maps, etc.) so it can actually do stuff, not just talk about it - multi-task — you can ask it multiple things and it can handle them in parallel also if u mispronounce anything it can update the existing stuff that is happening.

It can also set reminders and do stuff when you're not looking and talks to you by itself rather than always being triggered by the user message.