Nitin Mukesh Dhawal retweeted
The older I get, the more I realize that the single greatest challenge for any ambitious person is eliminating the guilt associated with free time and rest.
Now let's do this for every Gartner category of software
Hello computer.
Decompile and distill Grand Theft Auto.
Make the game set in my hometown -- use Google Earth to reconstruct it in pixel-perfect detail.
Make the character me and have my spawn point be in the mansion I always look at on Zillow.
Review my chat memory and make every mission about my hopes and dreams.
Make it playable online so my friends can join.
When you're done, sell all my video games on Ebay and use that money to fund tokens for my next game.
Nitin Mukesh Dhawal retweeted
A lesson from a real customer conversation last week.
Recently, a large Indian company bought Claude for all its teams.
The instruction from management was clear. Use Claude first. Don't buy other AI tools. Go and innovate.
A few weeks later, the IT team was stuck.
I think every CIO should know why.
We had just done a successful PoC with this company's IT team. Then the deal stopped. The PoC went well. The problem was that management had already paid for AI, and teams were told to build with it first.
That makes sense on paper. Now look at it from the IT team's side.
An engineer opens Claude. It can write a script, read a log, draft an RCA. Very useful.
But Claude doesn't know their servers, laptops, network, their IT Infra. It can't fix an issue at 2 AM on its own. It doesn't know which change needs approval or who to call when something goes wrong.
To get real autonomous IT , the team has to build all of that themselves. Connect it to their RMM, ITSM, monitoring tools, and 100s of integrations. Write runbooks. Add approvals, controls and logs. And keep running daily IT operations at the same time.
That's a lot to ask of a team that is already busy.
From what we have seen, innovation needs three things together:
1. A good AI model. Claude already gives you this.
2. Deep knowledge of the domain. In our case, years of fixing IT problems.
3. People who own the result. Engineers who work with your team until it's live.
Buying the model is only step one.
So we told the customer: we are not competing with Claude. Our platform runs on Claude. Connect your Claude account to Scogo AI. Management gets what it wanted, the IT team gets automation that actually works, and you are not paying twice for AI.
Simple way to look at it: management bought every team a great engine. But each team still needs a car built for its own road.
So every CIO who has bought an AI subscription has four options:
1. Let every team build on their own and hope it works.
2. Hire a big SI for a 2–3 year project.
3. Work with a domain partner whose platform runs on the AI you already bought.
4. A mix of these.
There is no single right answer. But one thing is clear to me.
An AI subscription alone will not change how your company works. The right platform, built for your domain, with people who take ownership, will.
At Scogo AI, we do this for IT. Agentic AI Platform for Autonomous IT Ops, running on the Claude you already have.
#EnterpriseAI #ITOps #AgenticAI #Claude #CIO
And it begins, every couple of weeks over the last 1year I get to experience the magic of Karan Singh. Goes into his shell and comes out with a banger
Today we are delighted to Open-Source Synthlite, a Rust CLI we developed to generate SFT ready dataset that we use to domain fine-tune our IT-Ops family of SLMs.
At @scogoai we're building Sia, an agent for autonomous IT operations. Training it takes a lot of domain-specific fine-tuning data, and we needed it fast.
A common approach is a pipeline: generate several answers, have a second model judge them, then loop on the rejects. It works, but it multiplies spend and adds a model whose judgments you also have to audit.
We made a narrower bet. One SOTA teacher call per prompt, then plain, deterministic filters for duplicates, length, refusals, repeated lines and held-out eval prompts. After that we run our own evaluation before anything gets trained.
What it does:
• Turns a file of prompts into chat-format train and validation files that TRL, @axolotl_ai , @UnslothAI and @huggingface datasets load as-is
• Works with any @OpenAI compatible endpoint, hosted or self-hosted
• Can be stopped at any point. Rerunning the same command resumes without duplicate rows or paying twice for finished work
• Pushes only to private Hugging Face datasets
• Ships as one ~7MB static binary for Linux and macOS: no Python environment, no services
Because there is no judge, the teacher sets the quality ceiling. For real datasets we recommend a frontier teacher such as Claude Opus 5.5 or GPT-6-Sol
It won't tell you whether an answer is right. The rows are unverified teacher output, so evaluate before you train.
If your team fine-tunes models for a specific domain, try it and tell me where it falls short: github.com/scogo-ai/synthlit…
डरता हूं किसी को पास आने देने से,
कहीं मेरी शख्शियत के सुराख़ न दिख जाए
हस्कर दूर रखता सबको महफ़िल में,
कहीं मेरे कुछ राज़ ना बिक जाए
है तो घर तेरे भी शीशे के,
कहीं पत्थर मारू और मुझे भी कांच लग जाए
We spent a lot of time, not on building this video but in building every layer that it covers. I and Karan have always followed that our work should speak for itself. Hopefully the echoes of this will reverberate through enterprise deployments
The next five years will change IT more than the last twenty did. I've watched two of those shifts already, and neither of them comes close.
First we fixed the process. Ticketing, workflows, ITIL. It helped us track the work. The work itself was still done by hand.
Then we automated. Scripts, RMM, orchestration. That helped too. But a script only does what you told it to do. The day something looked a little different, it stopped and waited for a person.
So the basic setup never really changed. Someone still had to be there for every decision.
Now look at how much of IT is built around that one thing. We have L1, L2 and L3 because people are busy. We have change windows because we don't want too many things going wrong at once. We check compliance once a year because checking is painful.
None of that is because it's the right way to work. It's just all we could do.
That's changing. Software can now look at a problem it has never seen before and deal with it properly. Once that's true, a lot of our old rules stop making sense.
This is why we started @scogoai , Our team has spent close to 200 years in IT between us, and we've been on the wrong end of enough outages to know how careful you have to be when software is allowed to act on its own. So we spent as much time on safety as we did on the AI.
Our platform is live with multiple Enterprise customers. Sharing this two minutes vid below if you want to understand what's keeping us busy.
IT shouldn't wait for something to break before it does its job.
We built SIA to change that.
Not another dashboard. The layer beneath your stack that makes the rest of it work.
Autonomous IT ops are where the industry is headed. We're saying that plainly, on day one.
Nitin Mukesh Dhawal retweeted
asking experts @MiaAI_lab @Tech2Wild for connecting multiple (read 3) dgx systems together , which is the right SFP cable (brand / model / specs / purchase link) you guys recommend ?
there are so many cables floating around and chances of picking the wrong cable is very high.
Nitin Mukesh Dhawal retweeted
A 15-year-old dream has come true today. I started a PhD with the dream of creating a system that chants any Sanskrit shloka perfectly.
And here I am opening sourcing 𝐕𝐚𝐠𝐝𝐡𝐞𝐧𝐮 - 𝐀 𝐯ṛ𝐭𝐭𝐚 (𝐦𝐞𝐭𝐞𝐫) 𝐚𝐰𝐚𝐫𝐞 ś𝐥𝐨𝐤𝐚-𝐭𝐨-𝐜𝐡𝐚𝐧𝐭 𝐭𝐞𝐱𝐭-𝐭𝐨-𝐬𝐩𝐞𝐞𝐜𝐡 (TTS) 𝐬𝐲𝐬𝐭𝐞𝐦 𝐟𝐨𝐫 𝐒𝐚𝐧𝐬𝐤𝐫𝐢𝐭. This is the world's first vrutta-aware, open-source TTS for Sanskrit Chanting.
Nitin Mukesh Dhawal retweeted
We shipped @TPLINKUS integration for @scogoai today.
Sia our AI Agent for ITOps now brings up and verifies TP-Link enterprise routers end to end. One instruction in, a live, verified site out. No engineer clicking through a web UI needed anymore.
Why it matters:
Branch rollouts have always been one engineer per site, hand-configuring the same router over and over. You miss one value, a branch goes dark.
Now you set up one golden unit and Sia replays that exact config across every site. It checks the tunnel is actually up before calling the site done, and stops cold if anything looks off.
The part i'm proudest of is the part most demos quietly skip. When Sia reconfigures the lan, the router's ip changes and the laptop's connection drops. So Sia renews the dhcp lease, moves itself into the new subnet, re-points to the router's new address, and keeps going.
Sia has pre-configured verification gates with explicit stop codes (WAN_NO_IP, VPN_DOWN, LAN_RECONNECT_FAILED). A gate fails, Sia stops, tells you exactly what it saw, and changes nothing further, it never factory-resets, never reuses another site's values, never prints a PSK value.
Below is a quick demo of a full site coming up, factory-fresh to verified tunnel.
@TPLINKUS is the first OEM we're putting our name behind, and we are just getting started.
@nmdhawal @scogoai
Nitin Mukesh Dhawal retweeted
There is such misunderstanding of seat vs token based billing in AI. Software was static - you literally sat on a seat, clicked on GUIs, and extracted value through actions. Companies paid fixed salaries to people who extracted value out of & through software. The more action you take (i.e. the more seats you have), the more value you could extract. AI, if you are truly using it as you're supposed to, feels like an endless tube of toothpaste. One day you'll want to squeeze a lot of it, the next not so much. A third day you may spin up heavy token usage very long horizon task with extended thinking on. You can spin up tasks while you sleep, on a flight, or at the gym, or with family. Or rather, when you're not in the seat! There is no other way to price AI _except_ usage and anyone who's not moved to this model is indicating to the world they just don't get it yet...
Nitin Mukesh Dhawal retweeted
Thinking of selling your car to @cars24india? think again! Car sold in apr'25, insurance lapsed in oct'25. Cars24 is driving the car without insurance and they keep sending replies like "working on it". Please RT
@rick_gerson
@yurimilner
@vikramchopra @nitin_gadkari
Nitin Mukesh Dhawal retweeted
1/ Upgraded Claude Code to v2.1.50 while watching India vs SA. Just wanted to try the git worktree feature.
Five agents. Five branches. Each working independently. Everything merged back to main. Cleanly.
Then India lost. And I had an afterthought.
Tshirt to choo ke hi maza aa gaya, kal testing karunga. Proud of your work @supreetkashyap
Nitin Mukesh Dhawal retweeted
Ramesh kept his documents in a blue plastic folder inside the cupboard.
Electricity bills, insurance papers, tax returns all neatly arranged. Every March, he would sit at the dining table with a calculator and his reading glasses, making sure nothing was missed. His wife would tease him for being so particular.
“Even the government doesn’t care this much,” she once laughed.
But Ramesh cared.He believed that if you lived correctly, life would behave correctly in return.
You pay your taxes.
You buy health insurance.
You don’t bribe.
You stop at red lights.
You build things slowly, properly.
He had spent twenty-five years building small securities a modest flat in Mulund, a fixed deposit for his son’s education, a medical policy renewed every year without fail. He wasn’t rich, but he was careful. Careful felt close to safe.
That afternoon, the sun was harsh. The kind that makes the road shimmer.
He stopped at the signal on LBS Road and wiped sweat from his neck. Above him, the metro line stood unfinished concrete segments resting on pillars like heavy thoughts paused mid-sentence. It had been under construction for so long that no one really noticed it anymore.
He had contributed to it too, in ways he never saw directly.
Through deductions on his payslip.
Through rising fuel prices.
Through the idea that the city would become better for his son.
The signal turned green.
He moved forward with everyone else.
The sound came suddenly a crack that didn’t belong to traffic. Some people later said they thought it was construction noise. Others said they felt the vibration before they heard it.
There was no time for understanding. Just weight.
Dust rose and covered everything in a pale cloud. For a few seconds, the afternoon disappeared.
When the air cleared, people were running. Someone was shouting instructions. A helmet lay on the road, cracked neatly down the middle.
By evening, traffic began moving again, squeezed around the debris. The metro pillars still stood. Work would pause, then resume. It always does.
At home, the blue plastic folder remained exactly where he had kept it.
The insurance policy was active.
The tax returns were up to date.
The investments were in order.
All the careful planning remained intact.
Only he did not.
In the days that followed, there were announcements, suspensions, fines. Numbers were discussed. Compensation was calculated. The language was official and steady.
But there is something unsettling about how quickly life can be translated into an amount.
Ramesh had done everything he was told a responsible citizen should do. He had believed that responsibility created a thin shield between you and chaos.
Yet that afternoon, beneath a structure meant to represent progress, the shield proved invisible.
The city will move faster one day when trains run overhead. People will look up at the smooth concrete and think of efficiency, convenience, growth.
Very few will think of the afternoon when something unfinished decided to fall.
And in a small flat in Mulund, a blue plastic folder will remain
perfectly arranged, carefully preserved presenting a quiet reminder that doing everything right does not always make a life heavier than concrete.


















