Olga Ostrovskiy

Hot take: most developer time trackers are basically surveillance software with a productivity logo slapped on top.

Random screenshots. Keyboard activity. Idle timers. Productivity scores.

And somehow we're supposed to believe that's helping developers do better work?

If you've been following along and would like to support us we would appreciate a star of GitHub: https://github.com/ota-run/ota

Ota now supports refusal canaries. Repositories declare tasks that must remain unavailable to agents, and CI verifies that the real execution boundary rejects them with `--expect-refusal`.

In the AI era, governance cannot stop at documenting what agents may do. Teams also need negative tests proving that forbidden execution remains forbidden.

Everyone talks about model lock-in, but the real switching cost is your conversation history. Months of context, decisions, and half-finished projects living inside one app.

We just shipped chat import in Osaurus (free, open source Mac app) so you can export your conversations from ChatGPT, Claude, Grok, Gemini, or Open WebUI and continue them with any model. Building it made us realize how differently each app treats your data on the way out. Some exports are clean JSON, some are a mess clearly not designed to be read by anything else.