Yes (thank god, finally). Your team talks in Kithe. It is the only chat tool you need.

You keep them (for now, we may have big plans lined up though). Kithe connects to your tools and reads them when a question needs it. The answer about last night read a Linear issue. The answer about Halden read your Attio.

A channel gives every kind of work the same shape, while Kithe reads what an interaction is for and opens a space built for that purpose. For example, a dev project tracks what shipped and what broke. Each space is tailored to the work it contains.

You can change the rule or delete it, all rules show who set them and when.

A wrongly routed message can be rerouted to the right person from where it sits (and Kithe routes it correctly the next time, we learn from everything that happens in Kithe).

You set the scope of what Kithe reads so what it learns stays in the space where it belongs. A direct message does not reach a dev project unless you send it there.

Smaller teams and startups, for now. Kithe works best as the first tool you set up. At that point your team has no habits to unlearn and no workarounds to defend. We're planning to support migrations from Slack and other chat / knowledge systems too. If you are using Slack and want to give Kithe a go, *really* send us your email.

Kithe rhymes with scythe. It comes from Old English cȳþan, and it means to make known. It is a cousin of kith, the people you know. We expect to correct people on this for about a year or two. (PS. I still get it wrong sometimes ngl)