AI - researcher & coder | writing about what I use myself

AI industry
Pinned Tweet
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

78
412
3,323
2,010,416
codila retweeted
Neobanks are great businesses that are easy to run. Today, you can create your own in 15 minutes on Whop: whop.com/blueprints/neobank
81
79
904
511,404
codila retweeted
Chinese students just found the best way to use JEV for any LLM or AI agent - released a PDF research the shift: I pasted it into Claude and GPT - and cut my costs by~63х here’s what they found across 44 benchmarks: 1 → 7,193 responses, 10 types of failure. Jev was tested on hallucinations, prompt injections, data leaks, and other AI failures 2 → One simple question worked: 0.886 median AUROC, beating trained baselines on 25 of 31 benchmarks without task-specific training 3 → Context beat clever prompting - give Jev the source or rule it needs to check the answer against 4 → Keep the probability, not just "yes" or "no" - Fitting a threshold on 10 labeled examples raised median F1 from 0.706 to 0.793 5 → Among the 50% most confident decisions, median accuracy reached 0.933 - send uncertain cases for another review 6 → Jev even helped uncover labeling errors in three benchmarks. Sometimes the test’s "correct answer" was the problem 7 → 11.4 questions per call, with 0.31-second median latency - on 19 benchmarks, checking cost $0.30 vs $18.96 with LLM judges - roughly 63× cheaper the result: It will made your setup CHEAPER and FASTER than what 95% of people are running Copy the Jev setup researchers tested across 44 benchmarks - then read the full Jev architecture ↓
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

21
44
339
40,292
Chinese students just found the best way to use JEV for any LLM or AI agent - released a PDF research the shift: I pasted it into Claude and GPT - and cut my costs by~63х here’s what they found across 44 benchmarks: 1 → 7,193 responses, 10 types of failure. Jev was tested on hallucinations, prompt injections, data leaks, and other AI failures 2 → One simple question worked: 0.886 median AUROC, beating trained baselines on 25 of 31 benchmarks without task-specific training 3 → Context beat clever prompting - give Jev the source or rule it needs to check the answer against 4 → Keep the probability, not just "yes" or "no" - Fitting a threshold on 10 labeled examples raised median F1 from 0.706 to 0.793 5 → Among the 50% most confident decisions, median accuracy reached 0.933 - send uncertain cases for another review 6 → Jev even helped uncover labeling errors in three benchmarks. Sometimes the test’s "correct answer" was the problem 7 → 11.4 questions per call, with 0.31-second median latency - on 19 benchmarks, checking cost $0.30 vs $18.96 with LLM judges - roughly 63× cheaper the result: It will made your setup CHEAPER and FASTER than what 95% of people are running Copy the Jev setup researchers tested across 44 benchmarks - then read the full Jev architecture ↓
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

21
44
339
40,292
codila retweeted
SpaceXAI engineer just shared a prompt that cuts GrokBot’s costs I connected it with Jev - send these to any AI agent to make it CHEAPER and FASTER than 95% of people are running Paste both prompts below. Enjoy:
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

12
18
136
20,348
SpaceXAI engineer just shared a prompt that cuts GrokBot’s costs I connected it with Jev - send these to any AI agent to make it CHEAPER and FASTER than 95% of people are running Paste both prompts below. Enjoy:
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

12
18
136
20,348
SpaceXAI engineer’s prompt (send this first):
6
722
codila retweeted
Send this Jev prompt to any LLM or AI agent It sets up Jev → analyzes you → finds where you waste time and money → upgrades your AI setup beyond 95% of people... Copy this now. Thank me later:
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

50
289
2,234
250,571
codila retweeted
Jev + Muse is the first AI agent system that actually automate 100% of my life 99% of people pay 200x more for slower AI agents - while 1% run this 2030 setup just 5 min and setup is ready: prompt → Muse → Jev decision → Muse execution → result step 1 → create your Jev API key (typesafe website) step 2 → clone and install the complete router from Github below python3 -m venv .venv && .venv/bin/pip install -r requirements.txt && cp config.example.yaml config.yaml step 3 → export the key before running anything: export TYPESAFE_API_KEY='YOUR_KEY' add the same export to ~/.zshrc or ~/.bashrc if you want it to survive a new terminal session step 4 → give your agent skill/jev-decision-layer.SKILL.md and connect it to src/router.py + recipes/ , raw Jev returns probabilities - the router converts them into executable actions step 5 → test the entire chain, not the raw Jev API: .venv/bin/python -m src.cli '{"goal":"what is 2+2?","kind":"chat"}' the final JSON should contain action, reason, mode, jev_used and confidence details step 6 → keep mode: shadow for 20–50 real decisions: the agent works normally while Jev’s routes are logged and checked; promote only reliable question packs step 7 → switch to mode: active with hard confidence gates: ≥0.80 act automatically, 0.50–0.79 advisory only, <0.50 escalate to the human the result: Jev + Muse is a system that decides what to do, what to skip and when to bring in - I’ve tested it across my daily workflows, and it’s the best setup I’ve found for automating routine Take the exact stack I built, run it yourself from the repo - then read the full Jev architecture behind it ↓
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

34
126
961
90,155
Jev + Muse is the first AI agent system that actually automate 100% of my life 99% of people pay 200x more for slower AI agents - while 1% run this 2030 setup just 5 min and setup is ready: prompt → Muse → Jev decision → Muse execution → result step 1 → create your Jev API key (typesafe website) step 2 → clone and install the complete router from Github below python3 -m venv .venv && .venv/bin/pip install -r requirements.txt && cp config.example.yaml config.yaml step 3 → export the key before running anything: export TYPESAFE_API_KEY='YOUR_KEY' add the same export to ~/.zshrc or ~/.bashrc if you want it to survive a new terminal session step 4 → give your agent skill/jev-decision-layer.SKILL.md and connect it to src/router.py + recipes/ , raw Jev returns probabilities - the router converts them into executable actions step 5 → test the entire chain, not the raw Jev API: .venv/bin/python -m src.cli '{"goal":"what is 2+2?","kind":"chat"}' the final JSON should contain action, reason, mode, jev_used and confidence details step 6 → keep mode: shadow for 20–50 real decisions: the agent works normally while Jev’s routes are logged and checked; promote only reliable question packs step 7 → switch to mode: active with hard confidence gates: ≥0.80 act automatically, 0.50–0.79 advisory only, <0.50 escalate to the human the result: Jev + Muse is a system that decides what to do, what to skip and when to bring in - I’ve tested it across my daily workflows, and it’s the best setup I’ve found for automating routine Take the exact stack I built, run it yourself from the repo - then read the full Jev architecture behind it ↓
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

34
126
961
90,155
codila retweeted
Jev Creator Diogo Almeida just released a 7-page document on how to use Jev better than ~95% of people I built and tested the FULL list, wrote a 14-page PDF setup guide and ranked every use case from 0–10: use case 1 → build a Permission Gate: Jev decides whether an agent action can run automatically, needs review or must be blocked before execution 9.5/10 - high safety value with relatively simple decision logic use case 2 → route tools instead of loading everything: Jev selects the category, tool and MCP schema required for the current task 9/10 - reduces unnecessary tool exposure; its value grows with the number of tools use case 3 → make context dynamic: Jev decides which files, messages and tool outputs should be included, summarized or excluded before every execution 10/10 - relevant to nearly every multi-file or long-running agent task use case 4 → compact history around the next task: the same agent memory becomes a different summary for UI work, security review or testing 8/10 - most useful when histories become long or task intent changes use case 5 → route models by total economics: Jev weighs difficulty, context, cache, latency and cost before deciding whether switching models is actually worth it 9/10 - high optimization potential, but dependent on reliable model metadata use case 6 → spawn subagents only when needed: Jev chooses the specialists, isolates their context and decides how their results should be merged 8/10 - valuable for decomposable tasks, with meaningful coordination overhead use case 7 → load AGENTS.md conditionally: give the coding agent only the rules required by the current task, file and directory 8.5/10 - low integration cost, impact grows with repository complexity use case 8 → turn skills into structured modules: each skill can modify tools, permissions, hooks, context policy and agent behavior without rewriting the whole system 8/10 - high reuse potential, but requires maintenance and governance use case 9 → route sensitive work safely: Jev classifies the data, selects an allowed provider or local executor and escalates high-risk actions to a human 9.5/10 - high risk-reduction value, effectiveness depends on policy quality use case 10 → run review in the background: testing, security checks and code review execute in parallel while Jev decides which findings should block the result 9/10 - broad verification value, with additional compute and triage cost overall score: 8.9/10 the result: Jev CEO showed you what to build - I tested the ideas, ranked what matters and turned everything into a Jev system better than what 95% of users are running Copy my complete 14-page Jev engineering playbook - then read Jev CEO’s original 7-page vision below ↓
sharing some notes on typesafe 🤝 coding agents: docs.google.com/document/d/1… 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)
33
47
530
95,007
Jev Creator Diogo Almeida just released a 7-page document on how to use Jev better than ~95% of people I built and tested the FULL list, wrote a 14-page PDF setup guide and ranked every use case from 0–10: use case 1 → build a Permission Gate: Jev decides whether an agent action can run automatically, needs review or must be blocked before execution 9.5/10 - high safety value with relatively simple decision logic use case 2 → route tools instead of loading everything: Jev selects the category, tool and MCP schema required for the current task 9/10 - reduces unnecessary tool exposure; its value grows with the number of tools use case 3 → make context dynamic: Jev decides which files, messages and tool outputs should be included, summarized or excluded before every execution 10/10 - relevant to nearly every multi-file or long-running agent task use case 4 → compact history around the next task: the same agent memory becomes a different summary for UI work, security review or testing 8/10 - most useful when histories become long or task intent changes use case 5 → route models by total economics: Jev weighs difficulty, context, cache, latency and cost before deciding whether switching models is actually worth it 9/10 - high optimization potential, but dependent on reliable model metadata use case 6 → spawn subagents only when needed: Jev chooses the specialists, isolates their context and decides how their results should be merged 8/10 - valuable for decomposable tasks, with meaningful coordination overhead use case 7 → load AGENTS.md conditionally: give the coding agent only the rules required by the current task, file and directory 8.5/10 - low integration cost, impact grows with repository complexity use case 8 → turn skills into structured modules: each skill can modify tools, permissions, hooks, context policy and agent behavior without rewriting the whole system 8/10 - high reuse potential, but requires maintenance and governance use case 9 → route sensitive work safely: Jev classifies the data, selects an allowed provider or local executor and escalates high-risk actions to a human 9.5/10 - high risk-reduction value, effectiveness depends on policy quality use case 10 → run review in the background: testing, security checks and code review execute in parallel while Jev decides which findings should block the result 9/10 - broad verification value, with additional compute and triage cost overall score: 8.9/10 the result: Jev CEO showed you what to build - I tested the ideas, ranked what matters and turned everything into a Jev system better than what 95% of users are running Copy my complete 14-page Jev engineering playbook - then read Jev CEO’s original 7-page vision below ↓
sharing some notes on typesafe 🤝 coding agents: docs.google.com/document/d/1… 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)
33
47
530
95,007
codila retweeted
I found the "Internet" moment in using Jev Jev analyzed every LLM and chose the BEST-VALUE one for each prompt It cut my costs and time by ~80% - and it’s probably the best way to use Jev... here's how to setup it in 10 min: step 1 → open @typesafeai , create API key (keep it off chat paste) step 2 → store TYPESAFE_API_KEY in a local .env step 3 → clone the Github below, then npm install && npm test && npm run demo step 4 → test Jev before connecting an agent: npx tsx sdk-runner/cli.ts --route-only "Rename a button label" step 5 → dry-run first: npx tsx sdk-runner/cli.ts --dry-run "your task" - read tier + model before you spend step 6 → add CURSOR_API_KEY + npm i cursor/sdk → live: npx tsx sdk-runner/cli.ts --run "your task" step 7 → Jev picks cost / balanced / intelligence → that model runs → you get the result step 8 → financial / production / publish / send-email stop unless --approve step 9 → kill switch: enabled: false or bypass step 10 → use it! the result: your agent stops wasting maximum intelligence on easy work - Jev picks the cheapest model that can win, then unlocks maximum power only when failure gets expensive unfortunately, AutoMode works extremely poorly across all AI tools and wastes even more tokens - this setup finally solves that problem Steal the agent setup everyone will use by 2028, copy repo - then read the complete Jev playbook below ↓
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

24
11
100
15,148
I found the "Internet" moment in using Jev Jev analyzed every LLM and chose the BEST-VALUE one for each prompt It cut my costs and time by ~80% - and it’s probably the best way to use Jev... here's how to setup it in 10 min: step 1 → open @typesafeai , create API key (keep it off chat paste) step 2 → store TYPESAFE_API_KEY in a local .env step 3 → clone the Github below, then npm install && npm test && npm run demo step 4 → test Jev before connecting an agent: npx tsx sdk-runner/cli.ts --route-only "Rename a button label" step 5 → dry-run first: npx tsx sdk-runner/cli.ts --dry-run "your task" - read tier + model before you spend step 6 → add CURSOR_API_KEY + npm i cursor/sdk → live: npx tsx sdk-runner/cli.ts --run "your task" step 7 → Jev picks cost / balanced / intelligence → that model runs → you get the result step 8 → financial / production / publish / send-email stop unless --approve step 9 → kill switch: enabled: false or bypass step 10 → use it! the result: your agent stops wasting maximum intelligence on easy work - Jev picks the cheapest model that can win, then unlocks maximum power only when failure gets expensive unfortunately, AutoMode works extremely poorly across all AI tools and wastes even more tokens - this setup finally solves that problem Steal the agent setup everyone will use by 2028, copy repo - then read the complete Jev playbook below ↓
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

24
11
100
15,148
codila retweeted
Jev + GrokBot is the best AI agent system I’ve built in my life It just made my setup CHEAPER and FASTER than what 95% of people are running... setup takes literally 7 minutes: prompt → GrokBot → Jev decision → GrokBot execution → result step 1 → open @typesafeai , create API key (keep it off chat paste) step 2 → tell Grok Bot: store TYPESAFE_API_KEY in the secure field step 3 → prompt Grok Bot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → tell Grok Bot: build the usage lab (router, dry-run, config, logs) - or clone Github below step 5 → add skill jev-usage-router: before browser / research / retry / extra bot → call the router, honor action step 6 → stay shadow first, read logs, then active when you trust it - kill switch: bypass jev or enabled: false step 7 → flip active: GrokBot obeys route - Jev decides - GrokBot executes - humans control irreversible actions the result: Jev + GrokBot the best and fastest agent running directly on your computer rn, I’ve already tested it on routine tasks - and the results are genuinely incredible You can come up with endless ways to use Jev + GrokBot - but the most important thing is to install it as soon as possible Copy this 2028 setup, explore my repo below - then read the full Jev deep dive ↓
Jev is the "Internet" moment for the AI industry It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost If you set it up correctly, you will have the AI engineer’s stack for 2028 In this article, I show you how
Article

Jev Engineering: Full 10-Step Roadmap to Set Up and Use a New Brain for AI (from scratch)

The Jevons Paradox (he's on picture) is a rule stating that an increase in the efficiency of a resource's use does not reduce, but rather increases, its overall consumption - That's the global

123
254
2,396
377,583