ken lu

第二大脑

[ken lu @luyuncan]

豆包手机大部分头部 app 都抵制，包括微信。微信这次希望所有小程序主动把自己奉献给微信 AI。小程序作者能得到什么？

[ken lu @luyuncan]

26 年 AI 编程走向成熟，开始进入工作效率领域，27 年工作效率走向成熟，开始进入生活场景，28 年生活场景成熟，开始真正的 AI 手机类平台硬件机会，29 年新的 AI 平台类硬件成熟，进入 AGI 时代。 30 年该真的开始脑机接口和人形机器人联动的元年了！

[ken lu @luyuncan]

@haozhi 你好

[ken lu @luyuncan]

@sitinme 和VPN 冲突怎么解决？

[ken lu @luyuncan]

OPC鼓吹者怎么想的，未来创业只会越来越难，因为迭代速度，巨头业务颠覆越来越快。除了巨头，最有可能的是几个互补的有经验的人用AI放大自己后，一起抱团创业。10人以内公司，强强合作，律师事务所模式，强AI依赖，远程协同办公，可能是常态！

[ken lu @luyuncan]

2026 年，个人 Agent 开始爆发。Claude Code 可以自主阅读代码库、修复 Bug、提交 PR。Devin 可以独立完成一个完整的开发任务。越来越多的 AI Agent 不再只是「聊天助手」——它们开始真正地操作软件。但一个尴尬的现实是：世界上绝大多数软件并不是为 Agent 设计的。Blender 有强大的 3D 建模能力，但 Agent 无法操作它的 GUI。Bilibili 有海量的视频数据，但 Agent 无法登录浏览器去搜索。LibreOffice、GIMP、Audacity、OBS Studio——这些已经存在多年的软件，它们的功能依然强大，但它们的交互界面只为人类设计。
https://t.co/czDX82cCid

[ken lu @luyuncan]

https://t.co/B3wSwAv3mb

发本书，大家可能需要

[ken lu @luyuncan]

@blackanger 谢谢

[ken lu @luyuncan]

很多人迷惑 skills 和 plugin 的区别，其实前者是给个人的无状态单一技能，而后者是服务企业团队的有完整数据流，各种 SAAS 鉴权的可交付 Agent 产品。OpenClaw 是前者最优框架，CoWork 是后者最优框架。不过都离不开最强基模的驱动。未来半年 Anthropic，OpenAI ，Google 都会用自己最新模型去搅动这个几万亿的企业办公市场，所有的软件公司都被迫转型！

[ken lu @luyuncan]

@AAAAAAAJtoy 文字可以编辑吗

[ken lu @luyuncan]

@jakevin7 拉一下吧

[ken lu @luyuncan]

@jakevin7 满了

[ken lu @luyuncan]

@LawrenceW_Zen vps 和 ip 哪里买

[ken lu @luyuncan]

@Zihan_dev @readwise save

[Satya Nadella @satyanadella]

Announcing Copilot Cowork, a new way to complete tasks and get work done in M365.

When you hand off a task to Cowork, it turns your request into a plan and executes it across your apps and files, grounded in your work data and operating within M365’s security and governance boundaries.

[Andrej Karpathy @karpathy]

Very interested in what the coming era of highly bespoke software might look like.

Example from this morning - I've become a bit loosy goosy with my cardio recently so I decided to do a more srs, regimented experiment to try to lower my Resting Heart Rate from 50 -> 45, over experiment duration of 8 weeks. The primary way to do this is to aspire to a certain sum total minute goals in Zone 2 cardio and 1 HIIT/week.

1 hour later I vibe coded this super custom dashboard for this very specific experiment that shows me how I'm tracking. Claude had to reverse engineer the Woodway treadmill cloud API to pull raw data, process, filter, debug it and create a web UI frontend to track the experiment. It wasn't a fully smooth experience and I had to notice and ask to fix bugs e.g. it screwed up metric vs. imperial system units and it screwed up on the calendar matching up days to dates etc.

But I still feel like the overall direction is clear:
1) There will never be (and shouldn't be) a specific app on the app store for this kind of thing. I shouldn't have to look for, download and use some kind of a "Cardio experiment tracker", when this thing is ~300 lines of code that an LLM agent will give you in seconds. The idea of an "app store" of a long tail of discrete set of apps you choose from feels somehow wrong and outdated when LLM agents can improvise the app on the spot and just for you.
2) Second, the industry has to reconfigure into a set of services of sensors and actuators with agent native ergonomics. My Woodway treadmill is a sensor - it turns physical state into digital knowledge. It shouldn't maintain some human-readable frontend and my LLM agent shouldn't have to reverse engineer it, it should be an API/CLI easily usable by my agent. I'm a little bit disappointed (and my timelines are correspondingly slower) with how slowly this progression is happening in the industry overall. 99% of products/services still don't have an AI-native CLI yet. 99% of products/services maintain .html/.css docs like I won't immediately look for how to copy paste the whole thing to my agent to get something done. They give you a list of instructions on a webpage to open this or that url and click here or there to do a thing. In 2026. What am I a computer? You do it. Or have my agent do it.

So anyway today I am impressed that this random thing took 1 hour (it would have been ~10 hours 2 years ago). But what excites me more is thinking through how this really should have been 1 minute tops. What has to be in place so that it would be 1 minute? So that I could simply say "Hi can you help me track my cardio over the next 8 weeks", and after a very brief Q&A the app would be up. The AI would already have a lot personal context, it would gather the extra needed data, it would reference and search related skill libraries, and maintain all my little apps/automations.

TLDR the "app store" of a set of discrete apps that you choose from is an increasingly outdated concept all by itself. The future are services of AI-native sensors & actuators orchestrated via LLM glue into highly custom, ephemeral apps. It's just not here yet.

[ken lu @luyuncan]

https://t.co/gTjr0BJomR

[ken lu @luyuncan]

@vikingmute @readwise save thread

[ken lu @luyuncan]

@berryxia @readwise save thread