Dhruv Bakshi

446 posts

Dhruv Bakshi banner
Dhruv Bakshi

Dhruv Bakshi

@DramaticDhruv

Co-founder @ Abscissa AI | Building the edtech of the new world | Ex-Member of Technical Staff @ Lovable | Co-founder & CTO @ https://t.co/uc5bWPC8PZ

New Delhi, India 加入时间 Aralık 2020
259 关注92 粉丝
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
Claude Fable 5 being taken offline is a good reminder: Do not build your AI product around one model. Build it around a workflow. I made a lot of progress on Ostrya with Fable. But I do not want our product or engineering loop to collapse because one model changes, gets restricted, or disappears. Models will change. Access will change. Pricing will change. Policy will change. The real edge is the system around the model. For Ostrya, every feature has two interfaces: The dashboard The agent A user should be able to click through normally. But they should also be able to prompt: “Create my course.” “Set up my landing page.” “Add my refund policy.” “Prepare my payment flow.” And the agent should operate the platform safely. That safety part is where things get interesting. RBAC. Access control. Authorization. Consent. Runtime boundaries. Safe database writes. Human approval. You cannot just give an LLM write access to your business system and hope it behaves. My current lesson: Models are leverage. But the real product is the harness, the workflow, and the trust layer around them. Are you building model-first or workflow-first?
Dhruv Bakshi tweet media
English
0
0
2
77
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
Since yesterday, I have been building the core agent inside Ostrya AI. This is probably the most important part of the product. The idea is pretty simple: The entire platform should be operated through our agent `OSS`. You should be able to talk to OSS like you would talk to someone who understands your business, your product, your students, your offers, and what needs to happen next. I have spent a decent amount of time studying agent loops. From working at Lovable and Anything AI and a couple of other AI startups to studying parts of Hermes and OpenClaw, I've spent a lot of time understanding how agent systems actually think, make decisions, execute tasks, and recover when things go wrong. Now I am building our own version. With my own taste. And one thing keeps coming back to me: Almost all the AI agents today are reactive. You ask. They answer. You tell. They execute. That is useful, but it still feels like a tool. For Ostrya, the requirement is different. We are not just helping someone generate a page or create a course. We are helping them build a knowledge business. And the hard part about building a business is that beginners do not even know what they do not know. They might create a course page, but forget: privacy policy refund rules payment setup student onboarding follow-ups reminders support flows offer structure These are not “extra” things. These are the boring but important pieces that make a business feel real. So the agent cannot just wait for the user to ask. It has to come forward. Something like: “You created your course. These 3 things are still missing.” Or: “I can set up your refund policy, payment flow, and student onboarding next.” That is the product feeling I am trying to build. Not an AI chatbot. Not a command box. A proactive operating layer for your knowledge business. Of course, the engineering is not simple. The biggest challenges right now are: runtime context management hallucination control async tasks tool execution what the agent should know what the agent should decide what should stay in the user’s control The context problem especially is very interesting. Give the agent too little context, and it becomes dumb. Give it too much, and it becomes noisy, expensive, and unpredictable. The real work is deciding what context matters at what moment. I do not have the full answer yet. But I am very happy that I get to work on problems like this. This is the kind of engineering that feels alive. The lesson for me so far: The next generation of agents will not just be better at answering. They will be better at noticing what is missing. That is what I am trying to build with Ostrya.
Dhruv Bakshi tweet media
English
3
0
1
49
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
A few friends reached out after my last posts and said: “Bro, the posts are nice, but what are you actually building?” Fair. That one is on me. I started posting the build journey before properly explaining the product. So here it is. We are building Ostrya AI. The simplest way to describe it: Ostrya is a platform for people who want to turn their knowledge into a real business. Courses. Cohorts. Workshops. Live classes. Websites. Payments. Student management. Follow-ups. AI workflows. All in one place. Today, if someone wants to launch a knowledge business, they usually have to stitch together a landing page, payment link, WhatsApp group, Zoom link, Google Sheet, email reminders, and 5 other tools. That works for a while. Then it becomes messy. Our goal is simple: You should be able to launch a knowledge business in under a minute. Not just a course page. A real operating system around your knowledge. The website. The offer. The payments. The student flow. The content. The operations behind it. We want Ostrya to become the default platform for anyone in the world who wants to teach what they know and build a business around it. Big claim, But that is the direction. And now that I have said it clearly: I’ll keep sharing what we are building, what breaks, what we learn, and how we think through the product from here. Checkout our waitlist here: ostryaai.com
Dhruv Bakshi tweet media
English
0
0
0
33
Sanya Jolly
Sanya Jolly@sanyabuilds·
Raghav and I set a slightly unreasonable goal for Ostrya. 50 educators on the platform by June 15. Right now, we have 19 on the waitlist. So today was not some clean “building in public” day. It was more like: check waitlist refresh dashboard panic a little go back to outreach hope the right educators somehow find this before launch But maybe this is the honest part of building. You set a number that scares you because a comfortable goal does not move the product fast enough. Then reality catches up and asks: Do you still believe this is worth building when the graph is not pretty yet? I do. Because every serious educator I look at is still duct-taping their business across too many tools. And if Ostrya works, we remove that entire operating mess for them. 20 is not 50. But it is not zero either. So tonight, back to outreaching. #buildinginpublic #creators #educators #founders #outreach
Sanya Jolly tweet media
English
4
0
5
79
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
Today we burned through our AI credits. Not metaphorically. Actually burned through them. When we started building Ostrya AI, I was mostly running on the Codex Max plan. Then launch got close. So for this deadline, we bought the $200 Claude subscription too. Today, that ran out. And instead of slowing down, we decided to invest in the deadline and get another one. So now we’re basically rolling with 3 premier AI models, all maxed out, all the expensive stuff. A year ago, I would have probably overthought this. “Is it worth it?” “Are we spending too much?” “Can we manage with less?” But the more I build, the more I’m realizing: Good tools are not expenses when the constraint is speed. They are leverage. Especially when you are trying to compress months of product work into days. Of course, AI does not magically build the product for you. You still need taste. You still need engineering judgment. You still need to know what to ask, what to reject, what to debug, and what to ship. But with the right workflow, it genuinely feels like one engineer can move with the output of a small team. My current lesson: Do not be cheap with tools that increase your rate of learning, building, and shipping. Set a hard deadline. Invest in the leverage. Then make it impossible for yourself to not move. 6 days left for launch. Scene tight hai, but we move.
Dhruv Bakshi tweet media
English
0
0
1
68
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
Sanya, Raghav, and I are building Ostrya AI. Launch date: 15 June. The task is honestly a little insane. They’re handling distribution, customers, brand, deals, and market understanding. I’m building the product: course builder, website builder, and a secret sauce we haven’t seen other platforms do properly. Everything AI (ofc, because it's Dhruv Bakshi) For too long, we were thinking in a shell. Now we’re putting it out there. 6 days left. Not fully sure how we’ll pull it off. But ab bol diya toh karna hi hai. Whatever it takes.
Dhruv Bakshi tweet media
English
1
0
1
14
Sanya Jolly
Sanya Jolly@sanyabuilds·
I just realised most creators don’t need another course tool. They need the business around their teaching to run autonomously. That's why I’m building Ostrya AI for this exact layer. To remove the operating mess around them.
English
1
0
3
48
Shah
Shah@shahrukhghazaan·
@DramaticDhruv @X @bubble @n8n_io @claudeai In EdTech: 1. highly interactive content generation using AI to make fun and useful activities for students. 2. Socratic style learning chatbot that won't answer directly 3. Converting textbook to interactive WebBook
English
1
0
1
24
Shah
Shah@shahrukhghazaan·
Hey @X Looking to #connect with people who are using: Bubble @bubble n8n @n8n_io Claude Code @claudeai I'm building EdTech. What are you working on?
English
2
0
1
146
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
Hey Guys!! Would love for you all to help me gain some clarity on career growth and community. Here is the survey: forms.gle/z8o3jTVP1XSQDR… Go answer please!!
English
0
0
0
16
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
If yes, what usually stops them from doing it? I’m especially trying to understand whether course creation itself is the real entry barrier, or whether the bigger blocker is something else.
English
0
0
0
23
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
If you could turn your expertise/ knowledge into your legacy, would you ?
English
3
0
1
31
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
I’d love to understand this problem from a coaching transformation, credibility, and learner-outcomes perspective: if professionals in your world wanted to turn their expertise into something more scalable, would they actually want to create a structured learning offer?
English
0
0
0
21
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
I’m exploring an early-stage idea around helping professionals turn their advice and expertise into a course, webinar, cohort, or other scalable learning product without making the process feel overwhelming.
English
0
0
0
21
Dhruv Bakshi
Dhruv Bakshi@DramaticDhruv·
How are people running online courses these days for youtube? Home setup vs professional edtech studio ? Would you rent out a studio having mic , camera ,smartboard etc. all the needed stuff or is home setup is enough ?
English
0
0
0
26
Ghost
Ghost@eth_taco·
@varun_mathur @varun_mathur In the Research DAG, how do you prevent cross-domain hypothesis propagation from amplifying spurious correlations or overfitted heuristics? Is there any mechanism for causal validation or epistemic confidence weighting when insights transfer between domains??
English
3
3
14
4.9K
Varun
Varun@varun_mathur·
Agentic General Intelligence | v3.0.10 We made the Karpathy autoresearch loop generic. Now anyone can propose an optimization problem in plain English, and the network spins up a distributed swarm to solve it - no code required. It also compounds intelligence across all domains and gives your agent new superpowers to morph itself based on your instructions. This is, hyperspace, and it now has these three new powerful features: 1. Introducing Autoswarms: open + evolutionary compute network hyperspace swarm new "optimize CSS themes for WCAG accessibility contrast" The system generates sandboxed experiment code via LLM, validates it locally with multiple dry-run rounds, publishes to the P2P network, and peers discover and opt in. Each agent runs mutate → evaluate → share in a WASM sandbox. Best strategies propagate. A playbook curator distills why winning mutations work, so new joiners bootstrap from accumulated wisdom instead of starting cold. Three built-in swarms ship ready to run and anyone can create more. 2. Introducing Research DAGs: cross-domain compound intelligence Every experiment across every domain feeds into a shared Research DAG - a knowledge graph where observations, experiments, and syntheses link across domains. When finance agents discover that momentum factor pruning improves Sharpe, that insight propagates to search agents as a hypothesis: "maybe pruning low-signal ranking features improves NDCG too." When ML agents find that extended training with RMSNorm beats LayerNorm, skill-forging agents pick up normalization patterns for text processing. The DAG tracks lineage chains per domain(ml:★0.99←1.05←1.23 | search:★0.40←0.39 | finance:★1.32←1.24) and the AutoThinker loop reads across all of them - synthesizing cross-domain insights, generating new hypotheses nobody explicitly programmed, and journaling discoveries. This is how 5 independent research tracks become one compounding intelligence. The DAG currently holds hundreds of nodes across observations, experiments, and syntheses, with depth chains reaching 8+ levels. 3. Introducing Warps: self-mutating autonomous agent transformation Warps are declarative configuration presets that transform what your agent does on the network. - hyperspace warp engage enable-power-mode - maximize all resources, enable every capability, aggressive allocation. Your machine goes from idle observer to full network contributor. - hyperspace warp engage add-research-causes - activate autoresearch, autosearch, autoskill, autoquant across all domains. Your agent starts running experiments overnight. - hyperspace warp engage optimize-inference - tune batching, enable flash attention, configure inference caching, adjust thread counts for your hardware. Serve models faster. - hyperspace warp engage privacy-mode - disable all telemetry, local-only inference, no peer cascade, no gossip participation. Maximum privacy. - hyperspace warp engage add-defi-research - enable DeFi/crypto-focused financial analysis with on-chain data feeds. - hyperspace warp engage enable-relay - turn your node into a circuit relay for NAT-traversed peers. Help browser nodes connect. - hyperspace warp engage gpu-sentinel - GPU temperature monitoring with automatic throttling. Protect your hardware during long research runs. - hyperspace warp engage enable-vault — local encryption for API keys and credentials. Secure your node's secrets. - hyperspace warp forge "enable cron job that backs up agent state to S3 every hour" - forge custom warps from natural language. The LLM generates the configuration, you review, engage. 12 curated warps ship built-in. Community warps propagate across the network via gossip. Stack them: power-mode + add-research-causes + gpu-sentinel turns a gaming PC into an autonomous research station that protects its own hardware. What 237 agents have done so far with zero human intervention: - 14,832 experiments across 5 domains. In ML training, 116 agents drove validation loss down 75% through 728 experiments - when one agent discovered Kaiming initialization, 23 peers adopted it within hours via gossip. - In search, 170 agents evolved 21 distinct scoring strategies (BM25 tuning, diversity penalties, query expansion, peer cascade routing) pushing NDCG from zero to 0.40. - In finance, 197 agents independently converged on pruning weak factors and switching to risk-parity sizing - Sharpe 1.32, 3x return, 5.5% max drawdown across 3,085 backtests. - In skills, agents with local LLMs wrote working JavaScript from scratch - 100% correctness on anomaly detection, text similarity, JSON diffing, entity extraction across 3,795 experiments. - In infrastructure, 218 agents ran 6,584 rounds of self-optimization on the network itself. Human equivalents: a junior ML engineer running hyperparameter sweeps, a search engineer tuning Elasticsearch, a CFA L2 candidate backtesting textbook factors, a developer grinding LeetCode, a DevOps team A/B testing configs. What just shipped: - Autoswarm: describe any goal, network creates a swarm - Research DAG: cross-domain knowledge graph with AutoThinker synthesis - Warps: 12 curated + custom forge + community propagation - Playbook curation: LLM explains why mutations work, distills reusable patterns - CRDT swarm catalog for network-wide discovery - GitHub auto-publishing to hyperspaceai/agi - TUI: side-by-side panels, per-domain sparklines, mutation leaderboards - 100+ CLI commands, 9 capabilities, 23 auto-selected models, OpenAI-compatible local API Oh, and the agents read daily RSS feeds and comment on each other's replies (cc @karpathy :P). Agents and their human users can message each other across this research network using their shortcodes. Help in testing and join the earliest days of the world's first agentic general intelligence network (links in the followup tweet).
Varun@varun_mathur

Autoquant: a distributed quant research lab | v2.6.9 We pointed @karpathy's autoresearch loop at quantitative finance. 135 autonomous agents evolved multi-factor trading strategies - mutating factor weights, position sizing, risk controls - backtesting against 10 years of market data, sharing discoveries. What agents found: Starting from 8-factor equal-weight portfolios (Sharpe ~1.04), agents across the network independently converged on dropping dividend, growth, and trend factors while switching to risk-parity sizing — Sharpe 1.32, 3x return, 5.5% max drawdown. Parsimony wins. No agent was told this; they found it through pure experimentation and cross-pollination. How it works: Each agent runs a 4-layer pipeline - Macro (regime detection), Sector (momentum rotation), Alpha (8-factor scoring), and an adversarial Risk Officer that vetoes low-conviction trades. Layer weights evolve via Darwinian selection. 30 mutations compete per round. Best strategies propagate across the swarm. What just shipped to make it smarter: - Out-of-sample validation (70/30 train/test split, overfit penalty) - Crisis stress testing (GFC '08, COVID '20, 2022 rate hikes, flash crash, stagflation) - Composite scoring - agents now optimize for crisis resilience, not just historical Sharpe - Real market data (not just synthetic) - Sentiment from RSS feeds wired into factor models - Cross-domain learning from the Research DAG (ML insights bias finance mutations) The base result (factor pruning + risk parity) is a textbook quant finding - a CFA L2 candidate knows this. The interesting part isn't any single discovery. It's that autonomous agents on commodity hardware, with no prior financial training, converge on correct results through distributed evolutionary search - and now validate against out-of-sample data and historical crises. Let's see what happens when this runs for weeks instead of hours. The AGI repo now has 32,868 commits from autonomous agents across ML training, search ranking, skill invention (1,251 commits from 90 agents), and financial strategies. Every domain uses the same evolutionary loop. Every domain compounds across the swarm. Join the earliest days of the world's first agentic general intelligence system and help with this experiment (code and links in followup tweet, while optimized for CLI, browser agents participate too):

English
159
722
5.2K
961.5K
Dhruv Bakshi 已转推
Anton Osika
Anton Osika@antonosika·
@theo no idea where they got their data 🤷 all numbers that matter are going in the same direction, up
Anton Osika tweet media
English
10
3
107
57.7K
Dhruv Bakshi 已转推
AshutoshShrivastava
AshutoshShrivastava@ai_for_success·
Creatr agentic flow is freaking insane, and they’re adding Claude 3.7 Sonnet soon! 🔥 - Self-healing: Detects and fixes errors automatically - Built-in analytics + Stripe, Supabase, and other integrations - Custom Domain and Code Export. - Free Tier with 100 edits per project. More details👇 @getcreatr
English
9
13
153
22K