朱哲清
Frontier Insights
Thesis: Pokee AI decouples agent architecture: small LLMs handle front-end I/O, while specialized Reinforcement Learning (RL) models manage back-end reasoning, trajectory planning, and API execution.
Strategy: Target developers and prosumers by replacing expensive frontier models with compact architectures (15M-param RL + sub-10B LLM). Leveraging verifiers and synthetic trajectories slashes inference costs by orders of magnitude while enabling direct, controlled tool execution.
Risks: Verifier generalization remains the primary frontier bottleneck. Scaling hinges on acute talent scarcity, multimodal data limits, and proving reliability—failing to outpace negative unit economics will trigger rapid consolidation.
Key Views & Dialogues
E201｜The Next AI Frontier: Reinforcement-Learning Pretraining and AGI’s Inflection Point (Part II)
Agent training depends on closing the loop between tasks, objectives, and Verifiers, with the central AGI gap running from Level 3 Agent to Level 4 Innovator and RL potentially producing correct but unintelligible strategies. Expensive environment interaction, scarce RL talent, and negative Agent margins will drive selection; scalable verification, disciplined reward design, and reliable tool orchestration will determine the next wave of differentiation and acquisitions.
View summary (7)
- The key divide in Agent training is not just data scale, but whether a task can be closed-looped through an objective and a Verifier. Tasks with existing text, image, and video collaboration data can first learn via SFT, then use RLHF to align preferences; but if a task requires 50 tool calls, no such complete trajectory exists online. Goal-driven tasks in code, math, physics, and supply chains need counterfactual generation of new solutions, followed by ground-truth verification—“If you can find a Verifier, you can consider the problem solved.”
- Within OpenAI’s five levels of AGI, the real technical chasm is not chat to reasoning, but Level 3 Agent to Level 4 Innovator. 朱哲清 sees the framework as a product-capability taxonomy: Level 1 depends on the definition, Levels 2 to 3 may not represent a huge leap, and the gap between Levels 4 and 5 may not be that large either. The hard part is whether a Verifier can generalize from known knowledge to judge new knowledge discovered by AI itself. “The gap between 3 and 4 is far greater than the gap separating 1, 2, 3 from 4 and 5.”
- RL pretraining could push AI toward knowledge unknown to humans, but it could also produce strategies that run while remaining unintelligible to people. Current attempts may still carry prior knowledge unavailable through pretraining; if developed further, code could have completely correct inputs and outputs while its internal variables, operations, and compilation logic look like gibberish. “Human readability” itself is difficult to encode as a rule-based check. 朱哲清 therefore sees reward design as a potential regulatory target, because the incentives assigned to an Agent during training determine its eventual behavior.
- RL’s cost disadvantage is real, but complex tasks may eventually leave companies no choice. 泓君 cited the industry view that RL delivers roughly 2x better results at roughly 10x the token consumption. 朱哲清 did not confirm the ratio, but explained that RL must rely solely on a reward function to reach its objective, while SFT already has standard answers; “RL fine-tuning will cost more.” Once tasks become complex enough to have no standard answer, the cost-effectiveness comparison breaks down: “Problems will become more complex in the future… and then there will be no choice.”
- Meta’s rationale for acquiring Scale AI may not be a return to a pure-text data race, but filling the medium-term annotation gap in multimodal and robotics. 朱哲清 summarized the resource cycle as compute in the short term, data in the medium term, and RL optimization over the long term. Image aesthetics are hard to standardize, video details are difficult to parse, and annotators may not even understand a robot’s intermediate actions. Multimodality may first require better parsing and reward-model capabilities before a Judge or Verifier can be built and RL fine-tuning can begin.
- Pokee AI is betting on a proprietary “reasoning + tool sequence” model that delivers the result through a single API and one line of prompt. A browser or virtual machine can compress thousands of tools into one generic interface, but at high cost, low speed, and with weak generalization in professional scenarios. Pokee instead accesses tools directly and hopes eventually to combine semantic understanding, planning, tool selection, and result generation into a single model. But 朱哲清 stressed: “Model capability determines your product’s floor, while product details determine its ceiling.”
- Scarce RL talent and negative-gross-margin Agents will jointly drive the next round of capital bifurcation. 朱哲清 estimates that “the entire industry has only a few dozen people” who can truly optimize RL well. Meanwhile, Agent companies may grow faster and lose money faster, with gross margins potentially reaching negative 50%. The technical route determines whether a company survives; the founder and team determine product differentiation. Over the next 1 to 2 years, the market may see a “big fish eating small fish” wave in which small teams are acquired.
E201｜From Manus to ChatGPT Agent: How Do Their Underlying Technical Architectures Differ? (Part 1)
ChatGPT Agent combines Deep Research, Operator, and a virtual machine, but minute-scale runtimes, weak preference memory, and payment trust still constrain consumer adoption. Competition is shifting toward repeatable professional workflows, with browsers, virtual machines, and APIs trading off universality, speed, reliability, and permissions as the Agent entry-point battle reshapes portal traffic and content monetization.
View summary (7)
ChatGPT Agent links Deep Research, Operator, and a virtual machine into an end-to-end workflow, but its first-round experience feels more like an engineering effort to seize the general-purpose Agent entry point than a mature technological leap. 朱哲清 tested “research first, then make a slide deck,” which took 35 minutes to 1 hour; travel tasks also took 20–30 minutes. He believes the main cause is the original speed of Deep Research and Operator, which becomes even slower when the two are combined. Its advantage is using strong vision capabilities to operate on webpages, but the overall results fell short of expectations and were far slower than imagined.
For consumer Agents, the hardest problems are not clicking through webpages but personalization, payment trust, and whether the task is worth delegating in the first place. ChatGPT Agent’s selected Singapore flights and hotels were ultimately rejected because it failed to remember the user preferred Hyatt, direct flights, and lower prices; when it reached payment, a human still had to take over. 泓君 noted that human assistants also require communication. 朱哲清 acknowledged the point, but said complex preference memory remains incomplete and cold start has not been solved.
The four architectural paths for general-purpose Agents are fundamentally trade-offs among universality, speed, reliability, and permission coverage. The browser route “is indeed universal,” but comes with high token usage and network latency; an open virtual machine suits coding and data analysis but struggles with login and authorization; restricted environments trade templates for speed; Pokee-style third-party API/SDK integrations are faster and more reliable, but can execute only actions formally exposed by platforms.
Product differentiation has shifted from “who is more general-purpose” to “who can be reused reliably within a target workflow.” Manus wins on coverage through its browser-plus-virtual-machine architecture, but may be dragged down by long contexts, hallucinations, and hour-scale runtimes; JSBox breaks the super-agent into templates for slides, spreadsheets, AI calls, and other tasks, improving speed while moving toward a vertical platform; 朱哲清 says Pokee can be 4 to 10 times faster than comparable products and cut per-run tool-call costs by 50% to 60%, at the cost of giving up some personal-account scenarios.
The clearer commercial market is recurring workflows for professional users, not one-off “universal assistants” for ordinary consumers. 朱哲清 observes that many consumer Agents have poor retention because a task “ends after you use it once”; Pokee users, by contrast, repeat the same workflow every week. Standardized business travel suits API-based Agents, while leisure travel with many variables is better suited to browser-based Agents—a divide that directly determines retention and unit economics.
If Agents become the entry point over the next 1 to 2 years, portal traffic, protocol control, and content monetization could all be rewritten. 朱哲清 expects portal traffic for e-commerce, search, and video to fall rapidly. He cites Google’s launch of A to A and argues that ChatGPT, Cloud, and Pokee launching protocols likewise reflects a contest for the Agent entry point. He also estimates that of nearly 20,000 MCPs, fewer than 200 are actually usable, making maintenance and reliability hard constraints on the protocol ecosystem.
The creator economy may not disappear, but advertising and recommendation could migrate from “page ranking” to “conversational sequencing.” Responding to 泓君’s concern that AI summaries could erode podcast advertising, 朱哲清 imagines Agents paying content providers per invocation, then inserting commercial recommendations at points where there is no single correct answer. The traditional ranking mechanism that displays 5 to 10 pieces of content at once could be replaced by 5 to 10 rounds of recommendations, with each round competing for the next interaction. He explicitly preserves the uncertainty: “I’m not 100% sure this is definitely where the future is headed.”