Building Apache Maka(Incubating), focusing on AI agent. 中文/EN

Joined March 2011
现在 Maka Rust 分支已经做到,3000 个 Agent 并行的情况下,内存占用控制到 1.2GB 了。 对比之下 Codex 大概需要十几个 GB。 Maka Rust 还在持续快速迭代中,目标下个月中完成 Rust 全面切换!
现在几乎主要的 Agent 都是用 Electron 方案,Codex、Claude...一旦同时跑的 Session 和工作多了,性能消耗和资源占用都很大,尤其是 Web 渲染的各种动画。 我们在把整个 Maka 重写为 Rust + GPUI。为未来几十/上百/上千个 agent 并行做好准备。 已经几乎可用了: github.com/apache/maka/tree/…
7
3
1
84
13,578
现在 Maka 已经把 GUI 完全做到终端里了,在 TUI 里实现了 GUI 的效果!
刚刚基本已经完成将gui带到terminal中来,基于github.com/longbridge/nsh 并添加tui支持。 实现在分支(包括vendor的nsh的tui支持) github.com/apache/maka/tree/… 我的操作比较墨迹,时长比较长,所以建议视频开2倍速
2
1
1
15
3,218
相比之前之前的纯文字终端效果简直就是原始人。。。
1
208
奥特曼表示 OpenAI 的内部模型远远领先市面上的所有模型,只要看数学结果就知道。 那你倒是放出来啊,现在被 Claude 按着头打...封号封的也太难受了
Sam Altman: OpenAI's advantage is their internal models are way ahead of public models. I asked how far ahead they are:
5
1
897
Maka 的魔法师又整了个大活,这个 TUI 和 GUI 也没有区别了吧。。。 从来没想过 TUI 还能做成这样
如果maka tui是这样的,是不是很酷 demo使用 nsh.dev 编写,在我的fork添加了tui backend。在支持kitty sixel iterm2 图形协议的终端上可以显示成这样,不支持的终端回退到 unicode 字符。原理也比较简单,就是利用nsh的gpui后端生成可提取的像素,然后注入到nsh tui后端即可
3
7
1,320
昨天一个海外客户下单+订单管理页面,团队找用友询价,居然报2.6万美金... 整个页面和商城都停留在 10 年前的水平,技术栈感觉也很久没更新了。 自己快速搓了个 demo,评估下一周就能开发完上线,再去 AWS 买个 VPS,预计总成本 200 美金/年。 很难想象以后这些 SaaS 还有谁采购...
7
14
3,991
补充下,2.6万美金是一年...后续每年都这个价格
2
420
针对 GPT 模型的过度敏感问题,一个有效的全局 AGENTS.md 提示词可以改善,核心就是对所有的工作都要按照 P0-P3 进行分级,P0-P1 才真正要紧,大部分 P2 P3 都可以不处理或者不重要。
5
14
1
97
13,093
所有工作先在内部按可验证证据、实际影响范围和可恢复性分级,再决定顺序与投入:P0为严重、广泛或不可恢复的核心目标、安全、资金或权限损害,立即处理;P1为核心目标、关键功能或实际交付实质受阻,优先解决,不一概视为紧急;
1
3
1,457
P2为不阻塞核心目标的局部或次要差异,低优先级核实、合并处理或延后;P3为装饰、排版等微小影响,通常不处理。分级用于取舍,不为小事单独输出分级说明。
3
1,334
只要多开了一些 subagent 做 chrome 采集任务,电脑就起飞了。。。
1
4
747
LlamaFactory 团队开始做 Agent 自进化了! 让 Agent 根据评测反馈改自己的指令和 skills,再用测试验证有没有用。 这个和 DSH 对 Agent Harness,还有之前的一些 Agent 自进化方向的工作不谋而合。 还开源了 awesome-rsi 和 GDPevo 评测集,做 Agent 和 RSI 的朋友可以一起关注下~
👋 Hi everyone! Long time no see We're the LlamaFactory team. After passing 70k stars on GitHub, we're now building the "LlamaFactory" of recursive self-improvement (RSI), towards a unified, efficient, stable, and flexible framework for agent self-evolution. Excited to share our team's latest work with you all. TL;DR: 🐧 We've open-sourced PenguinHarness, a multi-agent self-evolution framework that brings every RSI algorithm under one roof, over 2,600 GitHub stars. 📖 To get a fuller picture of existing RSI work, we went through 140 papers, organized and categorized them into the awesome-rsi repo, and published a survey paper. 📊 To compare self-evolution efficiency across algorithms fairly, we built GDPevo, a self-evolution benchmark covering 6 enterprise scenarios and 240 tasks, and used it to evaluate 6 mainstream agents. The details: Following the same philosophy as LlamaFactory, we want to bring all RSI-related data, models, algorithms, and benchmarks into a unified open-source harness, so everyone can try and debug RSI more easily. We've already integrated 5 RSI algorithms and 7 benchmarks, and we're aiming for 100+ down the road. Borrowing from DSH's "everything is a plugin" approach, we've packaged every algorithm and benchmark as a plugin. They're fully decoupled, so users can freely mix and match any RSI algorithm to evolve different agents. We also built a modern desktop client that installs in one click on any OS and runs locally, so you can grab the latest version from our website. Website: penguin.ooo/ OSS Repo: github.com/Prism-Shadow/peng… To better understand where the academic work stands today, we open-sourced the awesome-rsi repo and published a survey paper covering 140 recent works. We also mapped the trajectory of RSI against that of deep learning — many concepts line up one-to-one, only now the subject is an agent. OSS Repo: github.com/Prism-Shadow/awes… Paper: arxiv.org/abs/2610.14625 To better evaluate how different harnesses and methods perform at self-evolution, we built the GDPevo benchmark, spanning 6 real-world enterprise scenarios and 240 tasks. With a train/val split, it fairly measures an agent's self-evolution ability while guarding against overfitting. OSS Repo: github.com/Prism-Shadow/GDPe… Paper: arxiv.org/abs/2608.03764 This post isn't just about our work. We're also hoping to invite friends from academia and industry to join our open-source project. If you'd like to see your name on an open-source project and co-author papers with us, DM us and let's talk!
16
12
838
ChatGPT Web 现在可以直接调用和访问本机 Chrome 标签页了! 分析了下原理,就是 ChatGPT Chrome 插件在云端注册一个浏览器会话,作为 MCP 工具连给云端的 ChatGPT,统一由云端下发指令,插件再通过 Chrome 的 CDP 接口控制本机浏览器。 但看起来真的很黑科技了,未来会有更多 Agent 跑在云上
A few big upgrades for Chrome users today! We’re bringing the power of computer use to anyone who uses Chrome. First up: ChatGPT can now use your tabs in Chrome to make answers more useful and get things done for you. If you’re in Chat, it can look across your open tabs and gather info. If you’re in Work, ChatGPT can control your Chrome tabs to get things, like sending messages, filling out forms, or downloading files. It can even help you organize and group that pile of tabs you have open.
21
7
2
20
2,967
现在几乎主要的 Agent 都是用 Electron 方案,Codex、Claude...一旦同时跑的 Session 和工作多了,性能消耗和资源占用都很大,尤其是 Web 渲染的各种动画。 我们在把整个 Maka 重写为 Rust + GPUI。为未来几十/上百/上千个 agent 并行做好准备。 已经几乎可用了: github.com/apache/maka/tree/…
57
36
9
413
125,910
RC 的新观点依然是遥遥领先,Agent Harness 已经不再适用了,现在的模型不再需要驾驭和引导,不再需要额外的 plan mode、各种复杂的 skills、一些特殊的规则。 未来需要的是针对 Agent 薄薄的 runtime以及各种给 Agent 的各种程序,提供原生接口,或者是通过 Browser use Computer Use 访问。
I've actually stopped using the word "harness." I now think in terms of two things: agent runtimes and agent applications. Agent runtimes should be very small. Their core job is to connect an LLM API to an execution environment. That environment could be a full OS or a language VM, like a JavaScript runtime. Almost all that matters here is robustness. An agent runtime must be able to keep an agent running forever. Literally forever. Agent applications are everything else. Yes, literally every piece of software in the world. If software isn't built for agents, they use it through computer use or browser use. These capabilities can be built into the agent runtime or provided by another agent application. If software is agent-native, agents should be able to use it directly. The experience of an agent using that software—what we call "agent experience"—needs to be carefully designed, at least for now, to make efficient use of both time and tokens. Another key piece is agent identity. Agent applications should recognize each agent individually, rather than just the browser or computer it's using. This allows each agent's actions to be recorded in detail and audited in real time or after the fact. Everything we're building at @botiverse follows from this view.
5
2
38
4,002
补充一点,GPT 6.1 Sol 在 Agent Arena(模型匿名打分)的 Code 领域,是表现第一名的模型。 甚至高于 Astra。 也高于 Fable 5.1 和 Opus 5.5。 但 Opus 5.5 依然更全面,整体而言是第一名,在 Chat、Work 等工作也表现的更好,更灵活。
发现个很有意思的事情,在中文 X 中,Claude Opus 5.5 几乎是碾压 GPT 6.1 Sol,所有人都说吊打。 但在英文的 X 上,现在 Claude Opus 5.5 对比 GPT 6.1 Sol 大概是 6/4 开或者 7/3 开,其实 GPT 6.1 Sol 的口碑也是不错的。 整体上大家还是认可 Opus 5.5 是目前最好的模型,但没有这么一边倒。
10
4
73
38,522
发现个很有意思的事情,在中文 X 中,Claude Opus 5.5 几乎是碾压 GPT 6.1 Sol,所有人都说吊打。 但在英文的 X 上,现在 Claude Opus 5.5 对比 GPT 6.1 Sol 大概是 6/4 开或者 7/3 开,其实 GPT 6.1 Sol 的口碑也是不错的。 整体上大家还是认可 Opus 5.5 是目前最好的模型,但没有这么一边倒。
208
11
18
574
256,381
好耶!现在 Codex GPT-6.1-Sol 的默认上下文限制扩大到 500k 了。 我个人认为对于目前几个 1M 上下文模型,500k 左右的上下文基本都是默认最佳选择。 从缓存的角度,超过这个线压缩会变得更加划算。从性能角度,一般 500k 以下,现在的主流模型表现都是稳定的。
Day 7/ We have increased default context length for GPT-6.1 Sol to 500k when used through Codex & Work, up from 272k or an ~ 80% increase. We will go higher in the future, but it helps reduce occurrence of compactions and with tasks that require keeping a lot of context and nuance over periods of time. It was carefully tested and is the new sweet spot for most of our users. You can still override it if you want to be higher our lower, with maximum context length of GPT-6.1 Sol of 1M.
1
4
1,333
当然 200k 以下肯定模型表现会更好,但是以现在的 Codex Harness 和 Claude Code 的上下文使用量,基本起手就是 50-100k 的上下文使用,几乎就不可用了。。。 500k 会是一个不错的平衡点。
1
285
Grok Bot 产品完善速度有点快的,本身产品就做得很好了,最近又能免费接入 X,又能使用信用卡购物。 持久智能体真的要成为 Coding Agent 之后的下一个产品方向了吗?
To buy stuff, you can just take a picture of your credit card, drop it in the chat and Grok @Bot will scour the Internet for the best deal on the item you want and order it
Readers added context they thought people might want to know
xAI explicitly warns users not to include personal information in prompts, yet credit card photos may contain such information. Grok Bot's terms state that user data and credentials may be stored in its cloud environment and require human review for financial transactions. x.ai/legal/privacy-… x.ai/legal/grok-bot…
4
6
869