The IntoChat blog
Why work software is slow, and what we're doing about it.
Your operating system makes you the glue between apps
Windows, macOS, iOS and Android all ask you to pick an app and then carry your work between apps by hand. That made sense when a program took months to build. Now it takes an afternoon, and the operating system hasn't caught up.
Read the post →
To share software, a link should be enough
Software that someone built for themselves is easy to make now and hard to hand to a colleague. GitHub is where it ends up, and most people can't use it. A link works better, and it is how we're starting.
Read the post →
What if your AI learned from every employee?
Every employee teaches the company something each day, and most of it is forgotten by Friday. A chat that everyone uses could hear all of it, and a nightly process could turn it into what the whole company knows.
Read the post →
Banning AI at work doesn’t stop it
Tell people they can't use AI at work and they use it on their phone, with your customer list in the prompt. What a ban actually produces, and what control looks like instead.
Read the post →
Build it, use it, throw it away
Small programs written for one job, used while the job lasts, then deleted. They used to cost too much to build. Now they cost days, sometimes an afternoon.
Read the post →
AI that remembers how you work
The models are good, but they forget everything you talked about with them. What AI memory is today, what it misses, and how we're building ours.
Read the post →
The person who does the job should automate it
Whoever does a job knows best how to automate it. Now they can describe it in plain words, and AI writes code that a person checks before it runs.
Read the post →
Three problems we built IntoChat to fix
Shared memory for your team, powerful tools without a command line, and software you can just ask instead of click through.
Read the post →