The KhaBot mission, in five notes, part 5 of 5

Things should stay where I left them

How we build: nothing forced.

Khalil Ben Zineb3 min read

I cannot work in a restaurant.

Many people can. They open a laptop at a table, in the noise, and work for hours. I can't. The place is not mine. Nothing is where I expect it to be.

I am autistic, and I have ADHD. Both are official diagnoses. I am telling you this because it explains how KhaBot is built, better than any technical reason I could give.

What my mind asks for

Three things.

Things should be expected. I do not like change much. What really stops me is change I did not expect. A button that moved. A window that opened by itself. A tool that decided something for me while I was not looking.

Things should have borders. I need one thing in front of me, and I need it to be a place. For years, Linux workspaces saved my working life. One project per workspace. Today I often have seven projects open in seven workspaces, on three monitors. Each one is its own room. Working on two projects in the same room does not make sense to me, in the same way the restaurant does not.

Nothing should be pushed at me. If something is there, I want to be the one who reaches for it.

Then there is ADHD. It shares a lot with autism, with some traits turned the other way. Some days I need everything fixed in its place. Other days I need to pull one thing out, right now, and put it on another screen. For me the two do not arrive at the same time. So my tools have to serve both.

How this became KhaBot

I did not plan these as product rules. I built tools for myself, and they came out this way. Then I saw that they were the rules of the whole project.

Nothing forces itself. The Studio watches your files as they change, so you can ignore it completely and work your own way beside it. The API has no plan you must buy. Everything is optional.

Things stay where you left them. A project's settings are plain files, and there is one source of truth. Move a project to another machine and it opens the way you left it: the sessions, the layout, the open tabs, even a prompt you typed and did not send.

Each thing has its own room. One window for one session, placed next to the work it belongs to. And when the other side of my mind takes over, any tab can be pulled out into its own window.

One place for the basics. One account, one key, one balance. I do not want fifteen dashboards. I want one that I know.

Calm by default. Buttons stay hidden until you point at what they belong to.

Predictable before clever. You build something once. You maintain it forever.

I once built a VR workspace for myself. The first rule was that I could stay still.

A project that becomes the machine

There is one experiment I want to tell you about.

I changed the Studio so that a project fills the whole screen, like an operating system. The files you see are the project's files. The windows are the project's tabs. The launcher, the bar, everything on the screen belongs to that one project.

When I switched from one project to another, it felt like switching machines.

I cannot fully explain why that touched me. Technically it is only a design choice. But something in me relaxed. It just made sense.

It is still an experiment. When it is good enough, I will give it to people to try.

Not only for me

I do not speak for every autistic person, or for everyone with ADHD. We are very different from each other. I can only tell you what works for me, and I do not know yet if it works for others.

But I suspect something. A calm screen, and things that stay where you left them, are good for almost anyone.

So I am not hiding where these rules come from. If your mind works like mine, try KhaBot and tell me what I got wrong. If it does not, try it anyway.

Things should stay where I left them.

In KhaBot, they do.

Project OS Mode is planned. If you want to try it early, write to me.