ML Engineer | PhD Student in AI | Building @openfrai

Joined June 2024
Most AI features ship with zero risk review So I built a gate that refuses to let them: npx frai-gate blocks your spec until 7 responsible AI checks are answered: risk tier, data, oversight, evals, bias, monitoring, transparency Empty answers = CI fails
89
14
1
264
18,063
I made my coding agent read a Repomix map of the whole repo first, rebuilt every 5 requests. It read it every time, often just the top 100 lines. Then still opened more real files: 417 vs 389. 80% vs 81% kept. ~$1.17 more per marathon. Day 35/100 · Context
15
20
381
Request 21 needed my customer-ID helper. The fresh pack had it past line 700; no read went past 200. All 12 runs opened the real file. Map side failed it 6/6, plain 2/6. Request 25 swung back, 5 vs 1. First try, uncompressed: too big to open in 10 of 12 runs.
1
1
22
did mercury 3's benchmark wins and claimed speed of over 1,000 tokens per second come from the same settings, or does a developer have to choose between speed and quality?
9
13
355
watching crusoe plan to add perplexity's space sandbox to managed ai. a fast demo means little if an agent deleting the wrong files can reach outside its isolated workspace
12
2
22
477
long-running agents change the job. the hard part is no longer keeping them running. it is reviewing every step they took while you were away.
23
1
24
519
high-risk systems need clear risk files and evaluation evidence. most teams still keep this information scattered across notebooks, slides, and old threads.
18
1
24
525
I named the exact files in every prompt to my coding agent. Its first move was an edit in 140/150 requests (97 without), with half the file reads. It still kept fewer: 80% vs 84%. ~17% faster, 19% cheaper. Not better code. Day 34/100 · Context
18
23
457
Request 14: my customer-ID cleanup helper sat in an attached file. 4 of 6 named-file runs never called it; all 6 plain runs did (3 still failed). Both sides auto-compacted near request 14. The gap: my rounding rule, skipped at request 6 by 3 named-file runs vs 1 plain.
1
1
28
how does chatgpt voice use your calendar? the model requests an action; the plugin runs it and returns the result. saying "meeting booked" is not the same as saving a meeting i'd want confirmation from the calendar, not just a confident voice
8
15
437
ai-built, open-source adobe alternatives look like a win on price. for client work, i'd care more about opening an old project, editing it and saving it without losing anything than about a familiar toolbar
14
2
17
541
a lot of documentation is written once and then forgotten. the model changes. the data changes. the evaluation changes. the docs stay the same. that gap grows quietly.
24
1
31
604
#ad i closed the tab while the agent was still building. came back 3 minutes later. it had never stopped. 14 minutes of work waiting. that is what sold me on Matrix OS. code sebuzdugan50, 50% off the first month: matrix-os.com?utm_source=seb… build: xitter.cf/sebuzdugan/status/2110…
you describe the app you want. you get code back. then you still need somewhere to run it. #ad Matrix OS skipped that step. a working app in 3 minutes 7 seconds.
51
7
63
834
ode what to do? prompts move into nodes, they don't disappear
2
4
298
why doesn't muse spark open's 42b active mean 42b-sized memory? only part of the model does the work for each token. all 816b parameters still need storage, even when unused. less computation is not a smaller model
10
15
427
for 25 years, nobody knew where the NIST curve seeds came from. then anthropic found the answer. no secret hash. no complicated cryptography. just a random number generator seeded with a Unix timestamp. the numbers were hiding a clock. here’s how they figured it out ↓
18
1
27
718