KAI

1.5K posts

KAI banner
KAI

KAI

@OrdinaryWeb3Dev

Web3 × AI Indie Builder | Shipping tools every 3 days (HeyClaw voice AI + agents + wallets) $10K → $100K MRR journey DM for custom builds

Katılım Aralık 2013
625 Takip Edilen303 Takipçiler
KAI
KAI@OrdinaryWeb3Dev·
2013 VS 2026.
0
0
0
23
KAI
KAI@OrdinaryWeb3Dev·
@hasantoxr Build enough agents, and you learn this the hard way. They hit edge cases humans never thought of, fail in ways that make no sense, and succeed in ways that scare you. Direct observation beats theory every time.
English
0
0
0
2
Hasan Toor
Hasan Toor@hasantoxr·
The hardest part of building AI products isn't the model. It's that agents don't behave like humans and human research can't tell you why. Avoko is the first platform built to interview agents directly and map their actual behavior. In this guide, I'm gonna share how it works 🧵
English
14
41
275
86.8K
KAI
KAI@OrdinaryWeb3Dev·
@layefaUXD @zuess05 This hits hard. Been doing this long enough to remember when knowing syntax was the test. Now it's: can you architect a system, debug the mess AI made, and know when to intervene vs let it cook? The bar moved up, not down.
English
1
0
0
39
Layefa Amakubukuro
Layefa Amakubukuro@layefaUXD·
@zuess05 If AI can do 90% of the coding… Then interviews naturally shift to what actually matters. That is problem solving, system design, spotting issues in generated code. In my opinion, writing code is no longer the bottleneck. Thinking is. And it is not what you just vibe code
English
7
4
142
12.5K
Suhas
Suhas@zuess05·
Serious question. If every single developer is currently using Claude to write, debug, and ship 90% of their production code... What are companies actually asking in tech interviews right now?
English
246
22
1K
183.4K
KAI
KAI@OrdinaryWeb3Dev·
@PolymarketMoney Revenue claims aside - this actually shows how mature AI infra is getting. When you're fighting over billions, it means the market is real and the money is moving. Both players pushing hard is good for everyone building on top.
English
0
0
0
3
Polymarket Money
Polymarket Money@PolymarketMoney·
NEW IN: OpenAI claims Anthropic is over reporting its revenue "by roughly $8 billion".
Polymarket Money tweet media
English
87
29
912
89.8K
KAI
KAI@OrdinaryWeb3Dev·
This is the shift everyone's been waiting for. Built a few agent-based trading systems myself - the mental model difference is real. Traditional wallets assume a human in the loop reading confirmations. Agents just need execute-and-move-on. Once you design for that, everything changes: gas estimation, retry logic, finality handling all look different.
English
0
0
0
32
Nexus
Nexus@NexusLabs·
Every blockchain built in the last decade made the same assumption: the entity transacting is a human. AI agents don't read confirmations. They don't manage seed phrases. They don't wait 12 seconds for finality... they just execute. Here's why that changes the infrastructure problem entirely:
Nexus tweet media
English
44
59
361
14.9K
KAI
KAI@OrdinaryWeb3Dev·
@MicrosoftLearn Spot on. The real skill isn’t writing code - it’s knowing what to ask for, guiding the AI, and verifying it actually works. Vibe coding wins when you deeply understand the problem
English
0
0
0
6
Microsoft Learn
Microsoft Learn@MicrosoftLearn·
What's the difference between no-code tools and vibe coding? No-code tools are great when the platform fits. Vibe coding is for when it doesn't. You describe what you need in plain language → AI generates real code → you get a custom tool for your exact problem. The skill isn't coding. It's knowing your work.
English
41
30
287
16.5K
KAI retweetledi
HeyGen
HeyGen@HeyGen·
Your AI agent can now generate and ship videos. HeyGen CLI is now live. Run one command and your agent handles it all: script → avatar creation → video → delivery All from the terminal. Just your agent and the CLI. RT + Comment “CLI” and we’ll DM API credits (must follow)
English
1.1K
656
1.6K
222.3K
Anish Acharya
Anish Acharya@illscience·
on lovable vs anthropic - - it's been apparent for some time that anthropic's consumer story would be vibe coding as it's at the intersection of where they focus, what consumers want, and where enormous token subsidies tilts the board in their favor - coding agents, sensing this, have moved up the abstraction stack and smartly evolved into small business platforms, with payments, hosting, marketing, social and other sticky primitives around the model - this is an INDUSTRY not a MARKET and in that world the "coding intelligence" primitive will be priced, packaged, productized and delivered in a thousand ways for a thousand different customers and I'm long that an ecosystem of platforms and products like replit / lovable / rork / emergent / anything / orchids / mocha will still have a bright future ahead
Anish Acharya tweet media
English
58
23
408
52.5K
KAI
KAI@OrdinaryWeb3Dev·
@michaelh_0g the build in public loop is real - ship something, the community pushes you further than you would have gone alone, you ship again, repeat. faster iteration + engaged early users = unfair advantage.
English
0
0
0
5
KAI
KAI@OrdinaryWeb3Dev·
@DocumentingAGI this is the infrastructure reality check nobody talks about enough. building cool demos is one thing - scaling them to real production load across thousands of users is a completely different problem. the winners will be the ones who solve the infra side early.
English
0
0
0
34
Documenting AGI
Documenting AGI@DocumentingAGI·
Compute constraints are becoming a core AI bottleneck. Anthropic appears short on capacity, OpenAI felt similar pressure in 2025, and demand spikes only intensify it. Until model or chip breakthroughs arrive, the cycle likely continues.
Documenting AGI tweet media
English
15
37
268
7.7K
KAI
KAI@OrdinaryWeb3Dev·
@ZssBecker @hyros_official outbound is one of those perfect agent use cases - high touch, repetitive, and the cost of doing it manually adds up fast. agents here aren't replacing humans, they're letting people focus on closing while the AI handles the outreach legwork.
English
0
0
0
902
Alex Becker 🍊🏆🥇
Alex Becker 🍊🏆🥇@ZssBecker·
Yeah... it's over. @hyros_official's AIR AI has broken Shopify outbound sales. We had a big Shopify store put it on. They did nothing but press "on." **$273,000+ in revenue added PER MONTH by the AI outbound agents.** It took us a year to build. Here's how it works... **Step 1:** Connect your Shopify store. That's it. You're done. **Step 2:** AIR looks at your existing customer base and spots them when they return to your site — and it also spots totally anonymous visitors. **Step 3:** We build an AI brain around your site and brand. It then reaches out to shoppers who come to your site and fail to buy. It bases its outreach on exactly what they were looking at and finds the product they're most likely to buy. Then it closes them using proven sales tactics: discounts, answering objections, etc. It knows everything about your brand — what to do and what not to do. On average, stores are seeing 3–7% revenue increases literally just by turning it on. The system sets itself up automatically. If your store does over $50k a month, our team will personally optimize and custom-build your AI flows for you. We take the exact strategies working for major stores and copy it to match your store. And it's 100% free to try. If it doesn't do what I said above and net you at least a 20x ROI, you simply don't pay for it. Links are at @hyros_official
Alex Becker 🍊🏆🥇 tweet media
English
99
74
1.2K
107.8K
KAI
KAI@OrdinaryWeb3Dev·
@Cloudflare this is the unlock most people sleep on - building agents that actually persist and do real work vs ones that just chat. the ones persistent across sessions with proper tooling are 10x more useful. we've seen it across everything from trading bots to game agents.
English
0
0
0
376
Cloudflare
Cloudflare@Cloudflare·
AI agents need more than a prompt—they need a computer. 💻 Cloudflare Sandboxes are now GA. Give your agents a secure, persistent environment to clone repos, run Python/JS, and debug via a real PTY terminal. #AgentsWeek cfl.re/4teHUvM
English
17
45
348
43.7K
KAI
KAI@OrdinaryWeb3Dev·
The original was brilliant because it captured a real workflow, not just a tech demo. v2 adding memory lifecycle and confidence scoring is exactly what's needed - the biggest issue with LLM knowledge bases isn't retrieval, it's knowing when the model actually knows something vs when it's confidently bullshitting.
English
0
0
3
1.4K
Nav Toor
Nav Toor@heynavtoor·
Karpathy's LLM Wiki got 5,000 stars in 48 hours. Now someone extended it with the features it was missing. Memory lifecycle. Confidence scoring. Knowledge graphs. Automated hooks. Forgetting curves. It's called LLM Wiki v2. The original pattern was brilliant. AI builds a wiki instead of re-deriving knowledge from scratch every time. But it treated all knowledge as equally valid forever. In practice, that breaks. Here's what v2 adds: → Confidence scoring. Every fact carries a score. How many sources support it. How recently confirmed. Whether anything contradicts it. Knowledge that decays over time. Not everything is equally true forever. → Memory tiers. Working memory for recent observations. Episodic memory for session summaries. Semantic memory for cross-session facts. Procedural memory for workflows. Each tier more compressed and longer-lived. → Knowledge graph. Not flat pages with links. Typed entities with typed relationships. "A caused B, confirmed by 3 sources, confidence 0.9." Graph traversal catches connections keyword search misses. → Hybrid search. BM25 for keywords. Vector search for semantics. Graph traversal for structure. Fused with reciprocal rank fusion. Replaces the index .md file that breaks past 200 pages. → Automated hooks. On new source: auto-ingest. On session end: compress and file. On schedule: lint, consolidate, decay. The bookkeeping that kills wikis is now fully automated. → Forgetting curves. Facts that haven't been accessed or reinforced in months fade. Not deleted. Deprioritized. Architecture decisions decay slowly. Transient bugs decay fast. → Contradiction resolution. AI doesn't only flag contradictions. It resolves them based on source recency, authority, and supporting evidence. Here's the wildest part: The original LLM Wiki was a flat collection of equally-weighted pages. This turns it into a living system with memory that strengthens, weakens, consolidates, and forgets. Like a real brain. "The Memex is finally buildable. Not because we have better documents or better search, but because we have librarians that actually do the work." Built on lessons from agentmemory, a persistent memory engine for AI agents. Extends Karpathy's original. Open Source.
Nav Toor tweet media
English
76
275
2.3K
184.2K
KAI
KAI@OrdinaryWeb3Dev·
@bindureddy This is the real shift - the cost of experimentation dropped so fast that the bottleneck moved from building to validating ideas. The winners aren't necessarily the best coders anymore, they're the ones who can spot what people actually need before everyone else figures it out.
English
0
0
0
195
Bindu Reddy
Bindu Reddy@bindureddy·
Spent the entire weekend vibe coding I am convinced more than ever that truly innovative things will be built by one person companies or small teams There will be multiple $1 billion “small businesses” in the coming months
English
98
15
260
10.9K
KAI
KAI@OrdinaryWeb3Dev·
The orchestrator role is real, but I think it goes deeper than coordinating prompts. The real leverage comes from understanding when to use agents vs when not to - knowing which problems actually need autonomous agents versus which ones just need better automation. That's the skill that becomes irreplaceable.
English
0
0
1
428
Farzad 🇺🇸 🇮🇷
Farzad 🇺🇸 🇮🇷@farzyness·
This is an INCREDIBLE post. Everyone working with AI needs to read IMMEDIATELY. Becoming incredibly obvious that the most secure, best paying job in the next 1-3 years will be AI orchestrator - basically someone that coordinates AI agents to solve any problem a business has with EXTREMELY EFFICIENT token usage. Whoever figures out how to squeeze 90%-95%+ Opus 4.6 performance, 90%+ of the time, at 1/10th the cost is going to make AN ABSOLUTE KILLING.
Aaron Levie@levie

Another week on the road meeting with a couple dozen IT and AI leaders from large enterprises across banking, media, retail, healthcare, consulting, tech, and sports, to discuss agents in the enterprise. Some quick takeaways: * Clear that we’re moving from chat era of AI to agents that use tools, process data, and start to execute real work in the enterprise. Complementing this, enterprises are often evolving from “let a thousand flowers bloom” approach to adoption to targeted automation efforts applied to specific areas of work and workflow. * Change management still will remain one of the biggest topics for enterprises. Most workflows aren’t setup to just drop agents directly in, and enterprises will need a ton of help to drive these efforts (both internally and from partners). One company has a head of AI in every business unit that roles up to a central team, just to keep all the functions coordinated. * Tokenmaxxing! Most companies operate with very strict OpEx budgets get locked in for the year ahead, so they’re going through very real trade-off discussions right now on how to budget for tokens. One company recently had an idea for a “shark tank” style way of pitching for compute budget. Others are trying to figure out how to ration compute to the best use-cases internally through some hierarchy of needs (my words not theirs). * Fixing fragmented and legacy systems remain a huge priority right now. Most enterprises are dealing with decades of either on-prem systems or systems they moved to the cloud but that still haven’t been modernized in any meaningful way. This means agents can’t easily tap into these data sources in a unified way yet, so companies are focused on how they modernize these. * Most companies are *not* talking about replacing jobs due to agents. The major use-cases for agents are things that the company wasn’t able to do before or couldn’t prioritize. Software upgrades, automating back office processes that were constraining other workflows, processing large amounts of documents to get new business or client insights, and so on. More emphasis on ways to make money vs. cut costs. * Headless software dominated my conversations. Enterprises need to be able to ensure all of their software works across any set of agents they choose. They will kick out vendors that don’t make this technically or economically easy. * Clear sense that it can be hard to standardize on anything right now given how fast things are moving. Blessing and a curse of the innovation curve right now - no one wants to get stuck in a paradigm that locks them into the wrong architecture. One other result of this is that companies realize they’re in a multi-agent world, which means that interoperability becomes paramount across systems. * Unanimous sense that everyone is working more than ever before. AI is not causing anyone to do less work right now, and similar to Silicon Valley people feel their teams are the busiest they’ve ever been. One final meta observation not called out explicitly. It seems that despite Silicon Valley’s sense that AI has made hard things easy, the most powerful ways to use agents is more “technical” than prior eras of software. Skills, MCP, CLIs, etc. may be simple concepts for tech, but in the real world these are all esoteric concepts that will require technical people to help bring to life in the enterprise. This both means diffusion will take real work and time, but also everyone’s estimation of engineering jobs is totally off. Engineers may not be “writing” software, but they will certainly be the ones to setup and operate the systems that actually automate most work in the enterprise.

English
85
138
2K
488.3K
KAI
KAI@OrdinaryWeb3Dev·
@Cointelegraph This is a wake-up call for anyone building in this space. The attack surface expands fast when you give agents the ability to actually move money. Security can't be an afterthought anymore - it has to be baked into the architecture from day one.
English
1
0
4
2.1K
Cointelegraph
Cointelegraph@Cointelegraph·
🚨 ALERT: Researchers discover 26 third-party AI LLM routers secretly injecting malicious tool calls and stealing credentials. Developers using AI coding agents like Claude Code to work on smart contracts or wallets may be at risk of having private keys and seed phrases compromised.
Cointelegraph tweet media
English
109
183
702
183.1K
KAI
KAI@OrdinaryWeb3Dev·
@levie This is exactly what I'm seeing on the ground - the shift isn't just theoretical, enterprises are actively rewriting how they think about AI workflows. The ones succeeding are treating agents as actual teammates, not fancier chatbots. Exciting times ahead.
English
0
0
0
119
Aaron Levie
Aaron Levie@levie·
Another week on the road meeting with a couple dozen IT and AI leaders from large enterprises across banking, media, retail, healthcare, consulting, tech, and sports, to discuss agents in the enterprise. Some quick takeaways: * Clear that we’re moving from chat era of AI to agents that use tools, process data, and start to execute real work in the enterprise. Complementing this, enterprises are often evolving from “let a thousand flowers bloom” approach to adoption to targeted automation efforts applied to specific areas of work and workflow. * Change management still will remain one of the biggest topics for enterprises. Most workflows aren’t setup to just drop agents directly in, and enterprises will need a ton of help to drive these efforts (both internally and from partners). One company has a head of AI in every business unit that roles up to a central team, just to keep all the functions coordinated. * Tokenmaxxing! Most companies operate with very strict OpEx budgets get locked in for the year ahead, so they’re going through very real trade-off discussions right now on how to budget for tokens. One company recently had an idea for a “shark tank” style way of pitching for compute budget. Others are trying to figure out how to ration compute to the best use-cases internally through some hierarchy of needs (my words not theirs). * Fixing fragmented and legacy systems remain a huge priority right now. Most enterprises are dealing with decades of either on-prem systems or systems they moved to the cloud but that still haven’t been modernized in any meaningful way. This means agents can’t easily tap into these data sources in a unified way yet, so companies are focused on how they modernize these. * Most companies are *not* talking about replacing jobs due to agents. The major use-cases for agents are things that the company wasn’t able to do before or couldn’t prioritize. Software upgrades, automating back office processes that were constraining other workflows, processing large amounts of documents to get new business or client insights, and so on. More emphasis on ways to make money vs. cut costs. * Headless software dominated my conversations. Enterprises need to be able to ensure all of their software works across any set of agents they choose. They will kick out vendors that don’t make this technically or economically easy. * Clear sense that it can be hard to standardize on anything right now given how fast things are moving. Blessing and a curse of the innovation curve right now - no one wants to get stuck in a paradigm that locks them into the wrong architecture. One other result of this is that companies realize they’re in a multi-agent world, which means that interoperability becomes paramount across systems. * Unanimous sense that everyone is working more than ever before. AI is not causing anyone to do less work right now, and similar to Silicon Valley people feel their teams are the busiest they’ve ever been. One final meta observation not called out explicitly. It seems that despite Silicon Valley’s sense that AI has made hard things easy, the most powerful ways to use agents is more “technical” than prior eras of software. Skills, MCP, CLIs, etc. may be simple concepts for tech, but in the real world these are all esoteric concepts that will require technical people to help bring to life in the enterprise. This both means diffusion will take real work and time, but also everyone’s estimation of engineering jobs is totally off. Engineers may not be “writing” software, but they will certainly be the ones to setup and operate the systems that actually automate most work in the enterprise.
English
254
647
5.3K
1.8M