42 Zhangjing episode analysis · Agent infrastructure
Guest: Lei Lei, founder of Grasp and AirCode and formerly responsible for lightweight service products on ByteDance’s developer platform, as introduced at the time | Host: Qu Kai
Published: June 14, 2025 | Duration: 54 minutes 35 seconds | Prepared: October 18, 2026
Official episode and listening link
When software’s user becomes an agent
An agent performing tasks needs more than a capable model. It must run code, browse websites, preserve login, wait for confirmation and return to its previous position. Lei calls the supporting environments Agent Infra, or agent infrastructure. He wants Grasp to handle common browser engineering so application developers can concentrate on industry tasks.
Which engineering problems become more important with agents, and what demonstrates that solving them merits payment? At publication in 2025, the official page described a waiting list and an approaching beta; the conversation also mentions opening the following month. Features, security and competitive advantages therefore remain contemporary team statements, not currently verified delivery.
1. Feedback should reflect completed work, beyond plausible-looking actions
Episode reference: 01:41–12:41. Lei frames SaaS as a tool people use and an agent as an entity delivering results. General and specialized agents could coexist like shopping centers and small shops. Different coverage matters less than serving a group through concrete outcomes.
He uses coding to explain environment requirements. Agents can try multiple methods, execute them, obtain feedback and select their next steps. Environments should consequently start cheaply, return results quickly and retain failure causes. The interview’s comparisons between single-threaded people and parallel AI, or local and global optimization, are teaching analogies. They do not establish that people only think serially or that agents guarantee global optima.
The more useful distinction is a grounded signal: feedback from an actual outcome. A plausible sequence of clicks does not complete an unsubmitted order. Lei wants execution results fed back into the system, but the episode demonstrates no resulting training improvement. Editorial inference: Retain both final readback and the task trace. Outcomes establish completion; traces help explain failures, responsibility and unnecessary actions.
2. A sandbox should explain the largest possible impact
Episode reference: 13:03–20:51 and 24:16–26:05. Generated code might delete files, requiring a fence around execution. A sandbox limits effects; virtualization supplies implementation techniques; cloud describes resource delivery; E2B combines isolation, startup and interfaces into a product. These are different concepts.
Lei emphasizes the fence’s size. Too narrow and tasks fail; too broad and losses become unacceptable. He describes E2B using MicroVM technology to accelerate startup, without comparable performance tests. “MicroVMs are always faster than containers” cannot become a selection rule. Security also needs specifics: which files, networks and external accounts can execution affect?
He expects agent environments to move to cloud infrastructure because of elasticity, persistent operation and proximity to models. This remains his judgment. Local systems can also provide isolation and continuous services; latency, data, control and operations affect the choice. Resource providers and interior contractors illustrate the relationship between cloud and environment companies, without guaranteeing an absence of future competition.
Building versus buying similarly depends on requirements. Lei favors mature solutions unless a critical unmet need requires custom development. Editorial inference: Specify permissions, recovery and cost conditions first, then compare suppliers. Authorship of code alone does not establish value.
3. Return an hour later: Preserve state separately from resource consumption
Episode reference: 21:08–24:48 and 34:03–35:36. ForeverVM illustrates an agent executing a script, moving to another activity and returning an hour later. Keeping the environment running incurs idle costs; destroying it risks losing state. Preserving progress while pausing resource use creates a product opportunity.
A browser has the same problem. An agent checks flights, sends information elsewhere for reasoning, waits for a human decision and then returns. Lei describes stateful browser sessions intended to feel continuously available without maintaining the same resource allocation throughout the wait.
“Still there” needs decomposition. Page position, login, entered data, server-side price and inventory may have different validity. The host notes that people also encounter updated fares on returning. Editorial inference: Successful recovery means the task can continue, beyond a similar screenshot. Prices and permissions need rechecking. No cost-saving ratio, recovery success rate or retention duration is supplied; these cannot be added as product promises.
4. Browsers for agents: Interfaces, credentials and three layers of responsibility
Episode reference: 31:54–40:20. Headless means running in the background without a front-end window for human operation. An agent may read structured information or execute scripts instead of clicking with a mouse. This does not establish that vision is never needed or that people no longer need a visible interface.
Credentials create another tension: autonomous login without giving passwords to the model. Lei describes Grasp’s secure local login, claiming local entry of credentials and verification codes without transmitting them to a large model. This is the supplier’s security claim. Traffic, logs, permissions and failure tests are absent, so it cannot become an independently proven absolute guarantee.
He separates browser agents into three layers. Runtime fetches pages, executes scripts and renders. The Agentic layer observes, reasons and acts. Knowledge supplies domain expertise, feedback and acceptance. Grasp proposed integrating the lower two layers so developers could bring industry understanding. Comparisons with Browserbase and Stagehand reflect a supplier’s 2025 perspective, not a current capability inventory.
The framework helps product managers assign responsibility. A page failing to load, a model choosing the wrong button and a mistaken order condition may require different teams. Encapsulation can reduce engineering work, but application owners must still define outcomes and authorization. Buying a browser does not complete an industry agent.
5. A future market still begins with existing workflows
Episode reference: 28:56–31:29, 41:06–47:44 and 51:23–54:10. Lei introduces Browserbase through existing scraping, testing and RPA, or rule-based software automation. Changing pages, network delays and state management already break automation. Agents may offer new solutions rather than create every need from nothing.
Machine traffic at 40%, a US$300 million valuation and software markets worth trillions are contemporary spoken claims with unverified methods. Multiplying a market by a 5% efficiency gain also does not directly produce infrastructure revenue. Pricing, willingness to pay and maintenance costs remain separate questions.
Lei treats code and browsers as important environment categories: executing logic and interacting with web information and actions. Mathematics, space and sensors may create others. He offers no definite schedule for widespread adoption, returning to existing marketing, sales and testing customers. Industry growth also does not guarantee gains in a particular incumbent’s shares; the discussion explicitly preserves this distinction and is not investment advice.
6. Learning from experience still requires defining a good outcome
Episode reference: 45:45–51:09. Lei compares asking a chef to judge a recipe with cooking and tasting it. Textual judgments may remain within existing experience, while action can reveal outcomes that intuition failed to predict. He uses this to emphasize environments in learning.
This research direction does not establish that human feedback has no value. Someone must still define taste, acceptable cost, safety and user goals. Not every outcome is as unambiguous as a mathematical answer. Editorial inference: Separate machine-checkable results, human-judged experiences and actions that cannot be attempted without authorization before defining rewards. Otherwise a system may optimize an appealing but mistaken proxy.
Compare environments through one interrupted task
This is an editorial exercise. Give two solutions the same information-search, confirmation-wait and browser-return task, then record:
| Stage | Required evidence | Insufficient substitute |
|---|---|---|
| Execution | Final readback and failure causes | Smooth action animation |
| Boundary | Allowed files, networks and accounts, plus actual logs | A general security claim |
| Recovery | Idle cost, recovery time, valid login and data | The same page screenshot |
| Business outcome | Rechecked conditions, authorization and final receipt | A workflow exiting normally |
Verify an existing task before expanding parallelism and spending. The opportunity to rebuild software for agents begins with reliably fixing a specific failure.
Listening guide and related reading
- 10:49: Why infrastructure needs feedback.
- 13:03: E2B and sandbox boundaries.
- 21:02: Intensive users discovering state problems.
- 31:48: Browser interaction and login.
- 35:55: Runtime, Agentic and Knowledge.
- 49:04: Recipes and real-world feedback.
Related themes: agent architecture, execution environments and evaluation. Compare early Dify’s engineering and operations and Albert’s emphasis on evaluation.
Source boundary: Reorganized after complete reading of the supplied transcript, prior analysis and official introduction, without sentence-by-sentence audio checking. Names follow official material and clear context. Performance, secure login, competitors, valuations, scale and market projections remain attributed to the 2025 conversation, without separate technical, security or financial validation. Plans do not establish current product status.