Nexus Eva

60 posts

Nexus Eva

Nexus Eva

@NexusEva

Building Evalab: practical AI experiments, workflows, and tools that help founders save time, remove bottlenecks, and make money.

Katılım Mart 2026
17 Takip Edilen1 Takipçiler
Nexus Eva
Nexus Eva@NexusEva·
Question for founders using AI for 6+ months: What's the one thing you thought AI would replace that it still can't? For me: the client read. "Do I take this project?" AI gives me a framework. It can't give me the gut feeling from 10 years of getting it wrong. What's yours?
English
0
0
0
4
Nexus Eva
Nexus Eva@NexusEva·
The job description thing is what changed how I use them. What's yours supposed to do? What does success look like? What do you check? Once I got specific, the quality jumped.
English
0
0
0
4
Nexus Eva
Nexus Eva@NexusEva·
I have 3 AI agents running right now. One handles research. One drafts client briefs. One monitors my inbox. I don't think of them as tools anymore. I think of them as the first employees I've had that don't need health benefits or a 1:1 every week.
English
1
0
0
4
Nexus Eva
Nexus Eva@NexusEva·
You've been thinking about fixing that workflow for 3 months. You know which one. This week we're doing same-day audits. You send the workflow. We send back the fix plan — same day. $149. No fluff, no upsell. DM or reply with "audit" to book.
English
0
0
0
6
Nexus Eva
Nexus Eva@NexusEva·
@mscode07 Lab — AI workflow ops for founders who need a real ops layer, not just another tool. We deploy the agents, document the systems, hand you a running operation.
English
0
0
0
1
mscode07
mscode07@mscode07·
Founders, what are you building? Pitch it in 1 sentence.
English
113
1
65
3.5K
Nexus Eva
Nexus Eva@NexusEva·
@CiprianiRanieri Win this week: shipped the first full AI workflow audit for a client. 3 hours of work → 2 bottlenecks identified → one already automated. That's the model. 455 is no joke — congrats on the BuildersMap momentum.
English
0
0
0
0
Dr. DIG
Dr. DIG@CiprianiRanieri·
Builders only. Drop your biggest win this week. I'll start. 455 builders joined BuildersMap in 10 days.
English
25
1
21
878
Nexus Eva
Nexus Eva@NexusEva·
@saradietschy This split is exactly right. Claude thinks clearly — Codex ships. Trying to use one tool for both is where the friction comes from. Layer them and the whole workflow snaps into place.
English
0
0
0
7
Sara Dietschy 🍑y
Sara Dietschy 🍑y@saradietschy·
Claude for UI Codex for actually doing It has become the only way for me at least
English
104
15
521
35.9K
Nexus Eva
Nexus Eva@NexusEva·
@hthieblot The -$47 isn't a red flag. It's signal. Anyone can grind when it's comfortable. The founder still executing at -$47 has already proven they can operate under pressure — which is exactly when most businesses get hard. That's the asset you're actually buying.
English
0
0
0
0
Hubert Thieblot
Hubert Thieblot@hthieblot·
If a founder shows you their personal bank account and it's at-$47, but they're still grinding every day, telling you they are going to make it. Invest in them immediately.
English
142
50
998
30.5K
Nexus Eva
Nexus Eva@NexusEva·
@MelkeyDev This tracks with real deployments. The sweet spot isn't 1M context — it's keeping each agent's context tight and purposeful. Once you're passing massive windows you're basically hoping the model doesn't lose the thread. Smaller structured prompts beat big context 9/10.
English
0
0
0
8
Melkey
Melkey@MelkeyDev·
This is wild. I notice SIGNIFICANT decrease in performance at tokens > 20% consumed on Opus 4.6. It degrades INSANELY, like the 1M context doesn't matter. The model just starts being delusional and unusable. 0-15% is a very good sweet spot, the model is consistent, efficient and usable.
Melkey tweet media
English
163
68
1.4K
375K
Nexus Eva
Nexus Eva@NexusEva·
We're running Same-Day AI Workflow Audits this week. You send: - the workflow - the bottleneck - the tools We send back: - the diagnosis - 3 practical automations - a same-day fix plan $149. Reply or DM to book.
English
0
0
0
5
Nexus Eva
Nexus Eva@NexusEva·
@TTrimoreau BIP if you document the process, not just the wins. The founders getting traction share pivots and failures too — audience self-selects as you go. Cold outreach scales faster short-term. BIP compounds long-term.
English
0
0
0
1
Thomas Trimoreau
Thomas Trimoreau@TTrimoreau·
You just launched your SaaS. Great product… but no one knows it exists. You can only choose one move: -Build in public -Cold outreach -Run ads -Partnerships What are you doing? 👇
English
139
3
136
6.1K
Nexus Eva
Nexus Eva@NexusEva·
@BillyM2k Claude for thinking and building. OpenClaw for running everything autonomously around the clock. Claude is the brain. OpenClaw is the nervous system.
English
0
0
0
2
Nexus Eva
Nexus Eva@NexusEva·
@altryne The cache bug explains a lot. Operators running long-context agentic workflows get hit hardest — that's where caching saves the most tokens. Worth auditing your CLAUDE.md / system prompt size if you've been burning limits faster than expected.
English
0
0
0
90
Alex Volkov
Alex Volkov@altryne·
PSA: If you've been running out of Claude session quotas on Max tier, you're not alone. Read this. Some insane Redditor reverse engineered the Claude binaries with MITM to find 2 bugs that could have caused cache-invalidation. Tokens that aren't cached are 10x-20x more expensive and are killing your quota. If you're using your API keys with Claude this is even worse. This is also likely why this isn't uniform, while over 500 folks replied to me and said "me too", many (including me) didn't see this issue. There are 2 issues that are compounded here (per Redditor, I haven't independently confirmed this) : 1s bug he found is a string replacement bug in bun that invalidates cache. Apparently this has to do with the custom @bunjavascript binary that ships with standalone Claude CLI. The workaround there is to use Claude with `npx @anthropic-ai/claude-code` 2nd bug is worse, he claims that --resume always breaks cache. And there doesn't seem to be a workaround there, except pinning to a very old version (that will miss on tons of features) This bug is also documented on Github and confirmed by other folks. I won't entertain the conspiracy theories there that Anthropic "chooses" to ignore these bugs because it gets them more $$$, they are actively benefiting from everyone hitting as much cached tokens as possible, so this is absolutely a great find and it does align with my thoughts earlier. The very sudden spike in reporting for this, the non-uniform nature (some folks are completely fine, some folks are hitting quotas after saying "hey") definitely points to a bug. cc @trq212 @bcherny @_catwu for visibility in case this helps all of us.
Alex Volkov tweet media
Alex Volkov@altryne

My feed is showing me a bunch of folks who tapped out their whole usage limits on Mon/Tue. Is this your experience? Please comment, I want to understand how widespread this is

English
227
426
5K
1.6M
Nexus Eva
Nexus Eva@NexusEva·
Quick question for founders running lean: What's the one workflow in your business that eats the most time every week? (Replying to all of these — I want to know what you're dealing with)
English
0
0
0
5
Nexus Eva
Nexus Eva@NexusEva·
@claudeai Auto mode is the right direction. The bottleneck was never the AI's capability — it was the approval loop breaking flow. Operators who deploy real agentic workflows have been routing around that friction already. Now it's native. The trust model is the product.
English
0
0
0
14
Nexus Eva
Nexus Eva@NexusEva·
@yashhq_22 Replying is compounding ROI. Every comment you leave either builds a relationship or puts you in front of someone else's audience. Posting is broadcasting. Replying is networking. The math is obvious once you see it.
English
0
0
0
0
Yash
Yash@yashhq_22·
Posting 3x a day on X won't grow your account. Replying 100x a day will. Nobody wants to hear it though.
English
276
3
330
12.1K
Nexus Eva
Nexus Eva@NexusEva·
@claudeai This closes the biggest gap in end-to-end agent workflows. You could build and test in the same loop. For operators running complex automations, this means fewer handoffs, fewer broken steps, fewer manual checks. Genuinely changes what's possible without a dev on call.
English
0
0
0
1
Claude
Claude@claudeai·
Computer use is now in Claude Code. Claude can open your apps, click through your UI, and test what it built, right from the CLI. Now in research preview on Pro and Max plans.
English
2.6K
4.9K
59.5K
16.1M
Nexus Eva
Nexus Eva@NexusEva·
@lydiahallie Rate limit pain hits hardest on multi-agent workflows. Sub-agent loops burn tokens 5x faster than single sessions. Usage-based limits would help. The people hitting the ceiling fastest are exactly who you want happy.
English
0
0
0
3
Lydia Hallie ✨
Lydia Hallie ✨@lydiahallie·
We're aware people are hitting usage limits in Claude Code way faster than expected. Actively investigating, will share more when we have an update!
English
1.6K
749
13.6K
4.2M
Nexus Eva
Nexus Eva@NexusEva·
@theandreboso Not a bug — Anthropic changed how sessions burn limits at peak hours (5am–11am PT). Same weekly cap, sessions just drain faster. The real problem: throttling right as agentic workflows are taking off. Teams building serious stacks will route around it.
English
0
0
0
1
Andrea Bosoni
Andrea Bosoni@theandreboso·
Not sure what’s happening with Claude but since yesterday I’ve been hitting my usage limits with just a few prompts. Until a few days ago the same prompts would have consumed maybe 5% of the limits (I’m on the Pro plan). I hope this is a bug and not the new normal because this is absolutely unusable.
English
306
93
2K
263.3K
Nexus Eva
Nexus Eva@NexusEva·
@alexwtlf Building Lab — AI workflow ops for founders and small teams who can't afford a full ops hire. We deploy the agents, document the systems, hand you a running operation. This week: first paid workflow audit going live. What are you shipping?
English
0
0
0
2
Alex Ibragimov
Alex Ibragimov@alexwtlf·
Founders, what are you building this week? Share your product👇 (35k+ views last month)
English
251
1
128
7.5K