Twitxy Saved

Felix Meng

Verified account This account is verified. Learn more

@felixmeng_

CEO and Founder of @XTrace_ai | prev @Stanford
San Francisco Joined August 2026
39 Following 22 Followers 20 Posts

Latest posts 5

Pinned post

Felix Meng Verified account @felixmeng_
Hello world!

My old account algo was a mess so this is my new account!

Quick intro if you don't know who I am:
> Founder and CEO of XTrace
> Alum of Stanford and KCL
> prev. Mathworks and Sandia
> now live in SF
Felix Meng Verified account @felixmeng_
I'm excited to be speaking at SF Tech Week on Thursday, Oct 8

@Techweek_ #SFTechWeek
Tristan Gūwalgiya C. Verified account @tristangchen Oct 4
This is the most insightful panel on coding agents for engineers, CTOs, and engineering managers during SF Tech Week 2026.

Next Thursday, Oct 8, I'm hosting: "Unlock the Full Power of Coding Agents: Software Engineering in the Agent Era"

Panelists:
- @austinywang (@cmux)
- Carrick Rogers (Saris AI)
- @felixmeng_ (@XTrace_ai )

What we'll cover:
- How tech leaders keep up with new agent tools that come out every day
- How to stop vibe coding from hurting your team's code quality
- How to keep your agents and your team aligned
​
Sign up: lnkd.in/geSJ8-tN
​
Full calendar: tech-week.com

@Techweek_ #SFTechWeek
View quoted post on X
Felix Meng Verified account @felixmeng_
@Google open-sourced some insane research

What if not just your agent had a harness, but your environment did too?

>Agent harness: frozen LLM → add tools, memory, loops
>EnvHarness: static environment → add states, rules, observations

They got SWE-bench 61.7 → 68.3

links in comments:
Felix Meng Verified account @felixmeng_
Saturday at the OpenStages panel, I shared my thoughts on the next frontier of AI coding agents: memory that is stateful, shareable, and enforceable, not just retrievable.

Most teams already have specs, decisions, and hard-won engineering lessons documented somewhere. But in practice, coding agents can still miss them, operate on stale assumptions, or confidently take the wrong path.

At @XTrace_ai, we’re building what we call harness-level memory:
- Rules trigger at the right point in an agent’s workflow
- Instructions can include scripts and executable code
- Violations can block progress unless there’s a justified override
- Learned engineering context stays valid as the codebase evolves

The goal is to turn tribal knowledge and past mistakes into harness-level memory that every agent and teammate inherits. Each failure and each success gets written back, so the next agent starts ahead of where the last one finished. To me, that is the clearest path to recursive self-improvement.
Felix Meng Verified account @felixmeng_
Bookmark this!

52% of the time, the model ignores your system prompt.

You didn't read that wrong.

Researchers (Amazon + Notre Dame, NAACL 2025) tested 3,538 cases of exactly this. Every model they tried fell apart the moment instructions clashed.

You wrote careful guardrails. The model treats them as a suggestion.

arxiv link in comments: