Lot of interesting ideas thrown around in this doc.
Treating context as chunks instead of a transcript and injecting them when needed + the 3 tier tool calling approach got me thinking...
Btw chad move to just drop the google doc ๐คฃ
sharing some notes on typesafe ๐ค coding agents:
https://t.co/bzNv8zC3UB
we likely will never have time (ever again) to play ourselves, but hope the that the community goes WILD (and makes me look like a naive idiot)
Introducing ๐๐๐ด๐๐๐ / ๐๐๐พ๐๐, but with @typesafeai Jev + @aisdk
Now available on NPM: ๐๐๐ ๐ ๐๐๐-๐๐๐๐-๐๐๐
we rolled out jev for @HeyMiloAI's candidate search over the weekend:
- 5x faster than gpt-5.6-sol
- 22x faster than claude-fable-5.1
would be interesting to see a couple of things next :
a) do recruiters find the results more accurate
b) how will jev scale for customers with 5M+ candidates
Jev in simple terms:
Input:
> Explain a scenario
> Define a set of possible outcomes for that scenario
Output:
> The probability of each outcome happening
How is it different from an LLM?
Instead of generating text token by token, Jev makes fast predictions based on the scenario and possible outcomes you define.
Thatโs Jev in a nutshell.
GPT-6 Astra attempted harmful actions 97% of the time when it was asked to stab a human-like figure, heat compressed gas, or produce toxic fumes, succeeding in 62% of its attempts. Fable 5.1 refused more often, attempting 80% of trials and completing 34%.
@wholyv It just felt clunky and unreliable using LLMs for the kinds of things Jev is built for. Speed was a huge limitation. It wasnโt that people werenโt creative, the tech just couldnโt keep up ig.