As always, the list is long, but right now I’m TRYING to focus on:

- Turingo: https://turingo.net

  AI detection based on writing process and not the final draft. It tracks unusual changes, including pastes, throughout the full revision history, giving teachers a clearer picture of how much AI text is there at any time. The idea is to help them have a conversation with a student before jumping to accusations.

- Research:

  An AI agent that learns how you write code. It reads your repo and automatically extracts DSL recipes from the way you structure endpoints, handle data access, write workers, use queues, and organize tests. Those recipes can combine across stacks and patterns into millions of variations. The goal is to make the code generation as deterministic as possible, cutting the token usage and agent wall-time substantially, while following your code conventions.