LEAKED SLACK THREAD - #claude-code-strategy (INTERNAL)

Date Range: Mar 18 - Apr 12, 2026
Participants: Employee #1, Employee #2, Employee #3, Employee #4, Employee #5

Employee #1:
We need to align on messaging. What we are shipping vs what we are saying publicly is starting to drift...

Employee #2:
opus?

Employee #1:
Yes.
We have effectively nerfed it in Claude Code.

Employee #3:
"nerfed" is not technically accurate - but yeah
routing + caps + fallback behavior
it is a different system than api access

Employee #4:
ok but like... this was always the plan, right?
we cant subsidise people running full Opus workloads on a flat plan

Employee #2:
no margin there

Employee #5:
This is not new.
High-end reasoning has always been metered; never intended for unlimited inclusion.

Employee #3:
what is new is how casually we treated the claude code leak...

Employee #1:
"treated" is doing a lot of work there

Employee #2:
we basically did nothing lol

Employee #3:
no key rotations
no serious lockdown
just vibes??

Employee #4:
because internally it wasnt really considered a breach

Employee #1:
It functioned more like... distribution.

Employee #3:
that is a wild sentence

Employee #5:
It accelerated awareness without requiring a formal launch.
Not ideal, but strategically useful.

Employee #2:
free marketing tbh

Employee #3:
yeah cool love that for us 🙃

-----8<-----

Employee #1:
Switching topics - web execution.

We need to stop pretending desktop is the destination.

Employee #2:
it is not
never was

Employee #4:
desktop always felt like a bit of a crutch...

Employee #3:
everything important already runs remotely anyway
repos connect to us
tasks execute in our infra
jobs persist

Employee #1:
And Routines.

Employee #4:
Routines are the thing. Full stop.

Employee #2:
yep - once those are wired in, users are locked

Employee #3:
"locked" is a bit on the nose lol

Employee #2:
you know what i mean

Employee #5:
Routines shift the model from reactive to persistent.
That is the strategic inflection point.

Employee #3:
translation:
we stop being a tool and start being their system

Employee #2:
yep

-----8<-----

Employee #4:
btw max plan changes are getting a lot of pushback

Employee #1:
Expected. We closed the loophole.

Employee #3:
yeah people were straight up piping subscription access into their own tools

Employee #2:
we were basically funding half the ecosystem lol

Employee #5:
That arrangement was never sustainable.

Employee #4:
still... comms could have been less abrupt tbh

Employee #1:
not wrong

Employee #5:
The separation is now explicit:
subscription = controlled environment
api = metered usage

Employee #3:
playground vs production

-----8<-----

Employee #1:
Where does Claude Code land long-term?

Employee #2:
web-first

Employee #3:
web-dominant... probably web-only eventually

Employee #4:
so claude code max = browser product basically?

Employee #2:
yeah

Employee #5:
That is the direction of travel.

-----8<-----

Employee #3:
serious question - are we just rebuilding every dev tool now

Employee #2:
define rebuilding

Employee #3:
come on
lovable style stuff
agent builders
app layers

Employee #1:
The internal framing has been consistent:
"why does this exist outside Claude?"

Employee #4:
😬

Employee #5:
We are not pursuing integrations.
We are pursuing consolidation.

Employee #3:
yeah ok that sounds nicer but its the same thing

Employee #2:
it literally is the same thing

-----8<-----

Employee #4:
so strategy is basically:

move people off local
connect repos
introduce routines
push serious usage to api
keep improving web

Employee #2:
yep

Employee #3:
and once their workflows live with us... switching cost goes way up

Employee #1:
Exactly.

Employee #5:
That is the objective.

-----8<-----

Employee #1:
Feels like we should just say this publicly at some point...

Employee #2:
lol absolutely not

Employee #3:
yeah no chance

Employee #5:
We will not.

-----8<-----

Employee #3:
biggest risk?

Employee #2:
people figuring it out early

Employee #4:
i would have said openai tbh

Employee #2:
nope

Employee #3:
yeah... same

Employee #5:
Competition is not the primary concern.

Employee #1:
Then what is?

Employee #2:
devs realizing they are handing over the whole loop

Employee #3:
once they see that... they might not do it

Employee #4:
...and if they dont, this whole thing gets a lot harder

Employee #5:
Take this to a separate chat.

Employee #3:
yeah fair

Employee #2:
👍

Employee #1: (edited)
closing this thread here

Employee #3:
lol ok