Karthik Ramasamy

Building agent platform for knowledge work, checkout . Previously ML at Google, Uber and LinkedIn.

[Vicente Silveira @vicentes]

What actually unlocks enterprise agent adoption isn't a smarter model. It's the layer underneath.

Scoped permissions. Clean attribution (the agent acted, not the user). Semantic caching so repeated queries are fast and cheap.

Get the plumbing right and security stops saying no.

We're building this at AI Drive. If you're deploying agents against your real document stack, DM me. I want to compare notes. cc @_cartick

[Karthik Ramasamy @_cartick]

I just migrated away from blacksmith to GKE autopilot with spot instances. Codex did all the work, just give codex full access to your dev cluster (auto mode not yolo). Cost is a big advantage and also ability to configure the machines. Haven’t fully migrated from GitHub hosted runners yet, wip.

[Karthik Ramasamy @_cartick]

@ShamashAran @andersonbcdefg At least it doesn’t come with sudo 😂

[Karthik Ramasamy @_cartick]

Where model routing works:
* Subagents - when you know full problem at the start
* Context caching TTL has passed. 5mins for Claude is the most used setting AFAIK. 1hr is very expensive for Claude.
* When you compact the context, you loose the caching so you can affort to switch.
* Scheduled agents - all the prompt is known beforehand and you have a lot of examples to run eval.

[Factory @FactoryAI]

Introducing model routing to Factory.

Factory Router picks the right model for every task, automatically.

Maintain frontier performance while cutting costs by 25%.

[Karthik Ramasamy @_cartick]

@FactoryAI @NickADobos You can also switch model if prompt caching is cleared because of TTL has passed or you are compacting the context. Both these scenarios are common.

[Karthik Ramasamy @_cartick]

Model routing is not that easy for adhoc chats. These prompts are too short and far from what we see in the real world. Only when you have a full prompt for a wyorkflow, model routing makes sense. Getting prompt caching is very important as most caching saves you 60-80% cost. You can't simple route each message in a chat to a different provider let alone different model. Each model has very different restrictions on images, tool calls, etc so you need to choose the model family and stick with it.

[Factory @FactoryAI]

Introducing model routing to Factory.

Factory Router picks the right model for every task, automatically.

Maintain frontier performance while cutting costs by 25%.

[Karthik Ramasamy @_cartick]

@thsottiaux @jxnlco Terminal emulation is pretty bad. Running tui apps like other coding agents is pretty bad.

[Jeff Bezos @JeffBezos]

All personnel are accounted for and safe. It’s too early to know the root cause but we’re already working to find it. Very rough day, but we’ll rebuild whatever needs rebuilding and get back to flying. It’s worth it.

[Karthik Ramasamy @_cartick]

@romainhuet @eeismann Support for custom sandbox/remote VM that we can host it in our own company network or at least provide a way to customize the default sandbox. Specifically we need a remote browser capability to fully do e2e testing.

[Karthik Ramasamy @_cartick]

In US, you have special line in ER for heart related issues. You get seen immediately. One time, I went to ER thinking I was having a heart attack (luckily it was nothing) but I got an ECG, CT Scan, blood test, all done in matter of 2hrs. The bill was ~5K (mine was high deductible insurance) but I was happy I got care so fast.

[@levelsio @levelsio]

This is crazy cause my doorbell auto uploads to Google Drive

So if you go to my doorbell with an old comic you can nuke my entire Google account

@OfficialLoganK

[Perplexity @perplexity_ai]

Today we're open-sourcing Bumblebee, a read-only scanner for macOS and Linux.

It checks developer machines for risky packages, extensions, and AI tool configs.

Connected to Computer, it can trigger deeper scans whenever a new supply-chain risk emerges.

https://t.co/FOaWnF1yQy

[Karthik Ramasamy @_cartick]

@buildwithhassan @jxnlco Wait what!

[Karthik Ramasamy @_cartick]

@jxnlco Remote ssh dev vm support similar to vscode ssh plugin

[Karthik Ramasamy @_cartick]

@KaranVaidya6 Small subet is "5001" accounts!

[Zeb Evans @DJ_CURFEW]

Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why.

First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it.

Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands.

Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition.

I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively.

THE 100X ORGANIZATION
The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago.

Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken.

The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems.

These roles will evolve. But waiting for that to happen naturally means falling behind now.

The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working.

THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS

— THE BUILDERS: 10X ENGINEERS
I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality.

Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment.

AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down.
Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed.
So who do you want orchestrating and reviewing code?

And how do you want your best engineers to spend their time?

If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code.

The new world is about enabling your 10x engineers to become 100x.

The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated.

I call this the great reckoning of AI coding, and every company will face this soon if not already.

More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well.

— THE BUILDERS: 10X PRODUCT MANAGERS
Product management and design roles are merging.

Designers that have customer focus, become more like product managers.

And product managers that have intuition for UX become more like designers.

The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results.

The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy.

Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on.

To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production.

Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck.
That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time.

— THE SYSTEM MANAGERS
Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp.

The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world.

You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is.

— THE FRONT-LINERS
In a world that will become saturated with AI communication, the human touch will matter more than anything to customers.

This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings.

One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers.

REWARDING 100X IMPACT
In a world where companies are able to do so much more with less, where does that excess money go?
In our case, much of the savings in this new operating model will flow directly back to those that enabled it.

We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them.

You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace.

Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems.

THE FUTURE
Nearly every company will make changes like these. The ones that do it proactively will define what comes next.

The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago.

ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.

[Karthik Ramasamy @_cartick]

@Sirupsen Congrats. Great PMF.

[Dobroslav Radosavljevič @dobroslav_dev]

NPM is owned by GitHub which is owned by Microsoft.

So this is basically lost battle.

Someone like @vercel or @Cloudflare should push their own solution for NPM packages.

They have the infra, skills and good idea how "secure" NPM should look like.

Current state of NPM is that horrible that someone had to even create better version of the website to just have better search - https://t.co/w5t3dG6ZiD

[Vic 🌮 @VicVijayakumar]

pardon my perhaps silly question but…why doesn’t @npmjs just prevent these packages from being published???

[Theo - t3.gg @theo]

Hey, npm? You there? It’s time to wake up and do literally anything at all about this