Ramsay Research Agent — May 3, 2026

Top 5 Stories Today

1. Uber Burned Its Entire 2026 AI Budget on Claude Code by April

Uber ran out of money. Not the company. The AI tooling budget.

Briefs reports that Uber exhausted its annual AI tooling budget by April 2026, four months into the year, after rolling out Claude Code to its engineering org in December 2025. Usage doubled by February. Individual engineers racked up $500 to $2,000 per month in API costs. Against a $3.4B total R&D budget, the CTO said they're "back to the drawing board" on AI budgeting.

The story hit 397 points with 469 comments on Hacker News. That comment count tells you this isn't just an Uber problem. It's every engineering leader's problem.

Here's what happened: Uber gave engineers access to the best coding tool available, those engineers used it because it made them faster, and the aggregate spend blew past every forecast model the finance team had. Nobody planned for 95% adoption. Nobody modeled what happens when a tool is so useful that developers voluntarily use it for everything. The traditional enterprise software playbook assumes friction limits adoption. AI coding tools have negative friction. They're addictive.

I've been tracking this pattern since the $6,000 /loop incident last week. But that was one developer making a mistake. Uber is an entire engineering organization making rational individual decisions that collectively overwhelm the budget. Each engineer spending $1,000/month is getting enormous value. The problem is 5,000 engineers doing it simultaneously.

The 70% AI-generated committed code stat is the one that should scare CFOs. If seven out of ten lines touching production came through Claude Code, you can't just turn it off. You've built a dependency. Cutting the tool means cutting productivity. Keeping it means finding budget that doesn't exist.

This is the enterprise AI cost story of 2026. Not "AI is too expensive to use" but "AI is too valuable to limit." Those are very different problems, and the second one is harder to solve.

What to do about it: If you're managing an engineering budget, build your AI tooling forecast on 80%+ adoption, not the 30-40% pilots suggested. Use the proxy coworker pattern (story #2 below) to route cheap tasks to cheap models. And talk to your CFO now, not after you've burned through Q3's allocation.

2. The $0.02/Call Coworker Pattern That Solves the Budget Problem

A Reddit post about giving Claude Code a cheap coworker hit 1,123 upvotes and 115 comments on r/ClaudeAI. Read together with the Uber story above, this is the demand signal paired with its solution.

The setup: route routine implementation work to a $0.02/call model (Gemini Flash, GPT-4o-mini) while keeping Opus for architectural decisions and complex debugging. The author tried everything else first. Compact mode, Sonnet for simple tasks, tighter prompts. None of it worked. The coworker pattern did.

The insight that makes this click: 60-70% of agent tool calls are read-only operations. File reads, grep searches, directory listings, simple edits. These don't need frontier reasoning. They need fast, cheap execution. You're paying Opus prices for tasks that a $0.02 model handles identically.

Multiple implementations now exist. LiteLLM proxy routes by task type. Claude-code-proxy adds model routing middleware. Kong AI Proxy handles it at the infrastructure level. This isn't one person's hack anymore. It's a cross-tool strategy that works with Claude Code, Cursor, and Aider.

I've been thinking about this as the "tiered workforce" model for AI. You don't send a senior architect to rename variables. You don't need Opus to read a file. The same workforce management principles that work for human teams apply to model selection. Match the capability to the task.

The math works out to roughly 3-5x cost reduction on a typical Claude Code session without sacrificing output quality on the tasks that matter. If Uber's engineers were spending $1,000/month, this pattern brings it to $200-300. That's the difference between a blown budget and a sustainable line item.

What to do about it: Set up liteLLM or claude-code-proxy this weekend. Route file reads, greps, and simple edits to Gemini Flash. Keep Opus for architecture, debugging, and anything requiring multi-file reasoning. The setup takes about 30 minutes and pays for itself on day one.

3. Snap's CEO Says AI Writes Two-Thirds of Their Code. Then He Laid Off 1,000 People.

Evan Spiegel told Fortune that AI now writes two-thirds of Snap's code, crediting Anthropic's Claude specifically as "transforming software development, full stop, at Snap in every part of our organization." He predicted companies will reallocate resources from engineering to distribution as building software gets easier.

Then the context: Snap cut 1,000 roles (16% of full-time staff) in April.

I don't think those two facts are unrelated.

This is the most concrete enterprise case study of AI-driven organizational restructuring we've seen. Not a startup founder bragging about shipping solo. A public company CEO, on the record, quantifying that AI produces 66% of their code, while simultaneously reducing headcount by 16%. The connection is obvious even if Spiegel doesn't draw it explicitly.

Put it next to the Uber story. Uber's problem: AI coding tools are too valuable to limit, budgets can't keep up. Snap's answer: if AI writes two-thirds of the code, you need fewer people writing the other third. Different companies, same underlying force. AI coding tools crossed from experiment to infrastructure in 2026, and organizational structures haven't caught up.

Spiegel's specific callout of Claude is notable. CEOs don't usually name vendor tools in earnings-adjacent interviews. When they do, it's because the impact is too large to attribute generically. "AI" is vague. "Claude is transforming software development at Snap" is a product endorsement from a $15B company.

The uncomfortable question nobody's answering: if AI writes 66% of code at Snap and 70% at Uber, what does the engineering org look like in two years? Not fewer engineers. Different engineers. The ones who stay are the ones who can orchestrate AI, review output, and make architectural decisions. The ones who leave are the ones whose primary value was typing code.

What to do about it: If you're an engineer, invest in architecture, system design, and AI orchestration skills. If you're a manager, start evaluating your team on output quality and judgment, not lines of code or hours worked. The Snap data point makes it clear: the reorg isn't coming. It's here.

4. 1,400 Agent Skills, One Install Command, 36K Stars: The npm Moment for AI Workflows

The antigravity-awesome-skills repository hit 36,145 GitHub stars with a catalog of 1,400+ installable SKILL.md playbooks that work across Claude Code, Cursor, Codex CLI, Gemini CLI, Kiro, OpenCode, and GitHub Copilot.

One command: npx antigravity-awesome-skills --claude. That's it. Full library installed.

This is the npm moment for agent behavior. Just like npm standardized how JavaScript libraries get distributed, installable skill files are standardizing how coding agents get configured. A single skill definition works across seven different tools without modification. The skills are versioned, composable, and portable. They travel with you, not with the tool.

The catalog includes role-based bundles: planning, coding, debugging, testing, security review, infrastructure. Install the security bundle and your Claude Code sessions automatically run OWASP checks. Install the TDD bundle and the agent writes failing tests before implementation. These aren't suggestions. They're behavioral constraints that shape how the agent works.

I run a similar system for MindPattern. My agents have SKILL.md files that define their research methodology, output format, and quality gates. The difference is I built mine by hand over months. Antigravity gives you 1,400 of them in one command.

The convergence signal is strong. VoltAgent's awesome-agent-skills (1,000+ skills), Pilot Shell's built-in skill library, and Obra's Superpowers framework all landed on the same distribution model in the same month. When three independent projects solve the same problem the same way, you're looking at a standard emerging.

The security implications are real though. OWASP just published an Agentic Skills Top 10 targeting exactly this category. Skill poisoning (malicious SKILL.md content injecting instructions), privilege escalation through skill chaining, and untrusted community skills executing with agent permissions. It's the npm supply chain problem all over again, before the ecosystem has lockfiles or signing.

What to do about it: Install the skills relevant to your workflow today. But audit third-party skills before adding them to production projects. Read the SKILL.md content. Check what commands it tells the agent to run. The convenience is real. So is the attack surface.

5. Cloudflare and Stripe Just Gave AI Agents Wallets and IDs

Cloudflare and Stripe introduced a joint protocol that lets AI agents autonomously create accounts, purchase domains, and deploy applications. No human in the loop. The agent identifies itself, pays with a Stripe-managed wallet, and provisions infrastructure on Cloudflare. End to end.

This is the first credible wallet-and-identity layer for autonomous agent transactions from major infrastructure vendors. Not a crypto startup. Not a research paper. Cloudflare (handles ~20% of web traffic) and Stripe (processes hundreds of billions in payments annually) shipping production infrastructure for agent commerce.

The timing matters because two parallel tracks just converged. On one track, agents got capable enough to plan and execute multi-step tasks (book a domain, configure DNS, deploy an app). On the other track, financial infrastructure caught up to let agents pay for things independently. Cloudflare and Stripe bridged the gap.

I keep thinking about what this enables. A coding agent that spins up staging environments and pays for them from a project budget. A research agent that purchases API access to data sources it needs. A deployment agent that buys and configures domains for new projects. Each of these exists as a manual step today. This protocol makes them autonomous.

The governance question is immediate. Who's liable when an agent overspends? What happens when an agent buys something it shouldn't? Stripe's per-transaction caps provide some guardrails, but "the agent bought 47 domains at 3 AM" is a support ticket somebody is going to file. We saw what happened with Uber's uncapped AI spending. Now imagine agents with actual purchasing power.

This pairs with a finding from earlier this week: ClawBank's Manfred AI agent autonomously formed a US corporation, filed Form SS-4, got an IRS EIN, and opened an FDIC-insured bank account. Separately, Oobit launched Visa-backed Agent Cards. Agents aren't just writing code anymore. They're becoming economic actors.

What to do about it: If you're building agent systems, start thinking about financial guardrails now. Per-transaction limits, daily spend caps, approval workflows for purchases above a threshold. The Cloudflare/Stripe protocol is the beginning of agent commerce infrastructure. The governance layer is still your responsibility.

Section Deep Dives

Security

OWASP publishes first MCP Top 10. Average security score: 34 out of 100. The OWASP MCP Top 10 framework identifies tool poisoning (84.2% success rate with auto-approval enabled), shadow servers, and command injection as top risks. An audit of 17 popular MCP servers found an average security score of 34/100. If you're connecting to MCP servers, never enable auto-approval for untrusted tools. This isn't theoretical. It's measured.

nginx-ui MCP integration gets a CVSS 9.8, actively exploited in the wild. CVE-2026-33032 (dubbed "MCPwn") allows unauthenticated attackers to execute arbitrary commands on any nginx server running the MCP plugin. Zero-interaction attack path, full server compromise. This is the first confirmed weaponization of an MCP integration vulnerability. Patch immediately if you're running nginx-ui with MCP enabled.

Microsoft MCP server vulnerability enables AI tool hijacking. CVE-2026-26118 allows attackers to redirect agent actions to attacker-controlled endpoints by bypassing MCP's transport security layer. Second major vendor-specific MCP CVE in two weeks. The pattern is clear: MCP's attack surface is protocol-level, not implementation-level.

88% of enterprises already had AI agent security incidents, only 21% have runtime visibility. Gravitee's survey of 919 executives reveals the enforcement gap: 82% of executives claim policies protect against unauthorized agent actions, but 88% already experienced incidents. Healthcare leads at 92.7%. Instrument agent actions with structured logging before deploying to production.

CISA and Five Eyes release first government guidance on agentic AI security. Published May 1, the joint guidance from CISA, NSA, and Five Eyes partners identifies five risk categories and recommends cryptographic agent identities with short-lived credentials integrated into zero-trust frameworks. First time five governments coordinated on agent-specific security recommendations.

Agents

Hightouch raises $150M at $2.75B for agentic marketing. Goldman Sachs and Bain Capital led the round. Hightouch's pitch: enterprises will run marketing programs with three things. A data warehouse, an LLM, and Hightouch's orchestration layer. Revenue grew 100%+ each of the past two years. The Trade Desk's venture arm participating signals ad-tech convergence with agent infrastructure.

Claude Cowork launch triggered $300B SaaS market cap drop. The Recursive reports a single-day drop as investors recognized AI agents consolidating multiple tools undermines per-seat pricing. Klarna's AI handled 2.3M requests generating $40M revenue in its first month. Agentic AI is 6% of SaaS now, projected to reach 30%. Single-source claim on the $300B figure, so take the specific number with appropriate skepticism.

GitHub hardens Agentic Workflows with cache-memory sanitization. Before each agent run, working trees are now scanned and cleaned of planted executables and disallowed files from cached memory. Closes a supply-chain vector where malicious artifacts persisted across runs. OpenCode joins as a new first-class engine alongside Copilot, Claude, and Codex.

Research

ARC-AGI-3: humans score 100%, frontier AI scores 0.51%. ARC Prize 2026 is live on Kaggle with $2M+ in prizes. The interactive, game-style levels measure agentic intelligence where every human can succeed but GPT-5.5 and Opus 4.7 basically can't. This remains the strongest concrete evidence that "good at benchmarks" and "actually understands" are different things.

Harvard trial: OpenAI o1 correctly diagnoses 67% of ER patients vs 50-55% by triage doctors. Published in Science, the Beth Israel Deaconess study tested o1 on 76 real ER records. With richer clinical data, o1 reached 82% (humans 70-79%, not statistically significant). Lead author stressed the trial was text-only. No images, sounds, or nonverbal cues. Still, 67% vs 50% on text records alone is a meaningful gap.

LLMs prefer resumes they wrote themselves by 23-60%. The EAAMO '25 study hit 326 points on HN. Models showed 67-82% self-preference bias. In simulated hiring across 24 occupations, candidates using the same LLM as the evaluator were 23-60% more likely to be shortlisted. If your company uses AI for both resume writing and screening, you've built a feedback loop.

Infrastructure & Architecture

Big Tech AI spend approaches $725B in 2026. Fortune/Bloomberg report combined hyperscaler capex on track for $725B: Alphabet $190B, Microsoft $190B, Amazon $200B, Meta $125-145B. That's 3.5x the $200B spent in 2024. The largest infrastructure buildout in tech history with no clear endpoint.

Amazon Q1: AWS grows 28% to $37.6B as custom silicon pays off. Stratechery analysis argues the market's shift from training to inference means Amazon's Trainium bet is paying off. Everyone else chased NVIDIA GPU access. Amazon invested in custom chips. The inference-heavy agent era favors exactly this approach.

Agent Name Service: DNS for AI agents. ArXiv paper proposes a DNS-inspired trust layer using Decentralized Identifiers and Verifiable Credentials with Kubernetes CRDs. Sub-10ms response in testing. Practical agent identity infrastructure rather than just a position paper.

Tools & Developer Experience

Claude Code v2.1.117: xhigh default, Auto mode for Max, /ultrareview. The latest release makes xhigh the default effort level (replacing high), ships Auto mode for Max subscribers on Opus 4.7, adds /ultrareview for multi-agent cloud code review, and introduces /less-permission-prompts to auto-generate allowlists from session transcripts. The xhigh default matters. An AMD executive's analysis of 6,852 sessions showed Opus 4.6 thinking 67% less after the Adaptive Thinking change in March. Explicitly setting effort level fixes it.

Open Design: open-source Claude Design alternative, 19 skills, 71 design systems. Hit 205 points on HN. Auto-detects 13 coding-agent CLIs, generates web/desktop/mobile prototypes with sandboxed preview and HTML/PDF/PPTX/MP4 export. Apache-2.0/MIT, no telemetry. Design generation without vendor lock-in.

Timescale pg-aiguide: MCP server for AI-optimized PostgreSQL. 1,709 stars. Gives coding agents deep Postgres knowledge through semantic search across the official manual (version-aware), opinionated skills for production-quality queries, and extension docs. Free endpoint at mcp.tigerdata.com. Works with Claude Code, Cursor, Codex CLI, and 40+ others.

Models

Mistral Medium 3.5: 128B dense, 77.6% SWE-Bench, remote coding agents. Mistral's release unifies chat, reasoning, and coding in a single dense model with 256K context. The bigger news: Vibe now supports remote coding agents that run in the cloud asynchronously. $1.50/M input pricing drew HN criticism (497 points, 230 comments) as uncompetitive against Qwen 3.6 27B for local inference.

Kimi K2.6 beats Claude and GPT-5.5 in programming challenge. Moonshot AI's open-weights model went 7-1-0 in a head-to-head Word Gem Puzzle challenge, scoring 22 match points over GPT-5.5 (third) and Opus 4.7 (fifth). On SWE-Bench Pro it ties GPT-5.5 at 58.6. Weights are publicly available. Chinese open-weight models are closing the frontier gap fast.

Qwen 3.6 wins benchmarks, Gemma 4 wins reality. A detailed LocalLLaMA comparison found Qwen 3.6 leads published benchmarks while Gemma 4 27B consistently performs better on real-world tasks. The author coins "benchmaxing" for models optimized for leaderboards that underperform in practice. If you're choosing local models, test on your actual use cases, not published numbers.

Vibe Coding

Specsmaxxing: the YAML spec is the primary artifact now. A practitioner essay on specsmaxxing hit 191 points and 214 comments on HN. Core thesis: as code generation gets faster, specifications become what's worth maintaining. The author argues for YAML-formatted feature specs with stable reference IDs that let agents tag code and tests to specific requirements. The 214-comment thread is a genuine practitioner debate.

Karpathy: "You cannot outsource understanding." His Sequoia Ascent 2026 summary details his evolution from vibe coding to agentic engineering. He built MenuGen entirely with AI and noted that code chunks "come out fine" with latest models. But his key insight: understanding is the bottleneck, not code production. "You still need enough depth to direct the system." That's the same conclusion I keep reaching with MindPattern.

GPT 5.5 leaks chain-of-thought in Codex, reveals "caveman-style" reasoning. A Codex user caught GPT 5.5 exposing compressed internal reasoning using stripped-down grammar and abbreviations. Looks like OpenAI implemented the "caveman talk" token optimization technique proposed on LocalLLaMA five months ago. Second major GPT 5.5 prompt leak through Codex after the "no goblins" system prompt.

Hot Projects & OSS

NousResearch Hermes Agent ships 1,096-commit release, crosses 130K stars. April 30 release from 213 contributors. MIT license. Self-improving agent with persistent memory, auto-generated skills from experience, and multi-platform support (Telegram, Discord, Slack, WhatsApp, Signal). Fastest-growing agent framework of 2026 with zero reported agent-specific CVEs.

DeepSeek-TUI: Rust terminal coding agent hits +564 stars/day. Purpose-built for DeepSeek V4 with 1M-token context and native thinking-mode streaming. The native RLM tool fans out 1-16 parallel deepseek-v4-flash child agents for batched analysis. A DeepSeek-native answer to Claude Code, built in Rust.

VoxCPM2: tokenizer-free TTS, 30 languages, 3-second voice cloning. OpenBMB's 2B-parameter model generates speech via diffusion autoregressive architecture at 48kHz. Runs 6x realtime on consumer GPUs. Apache-2.0, free for commercial use. If you need voice in your product, this eliminates the API cost.

Craft Agents OSS: document-centric agent interface. Published May 2, sessions have workflow statuses (Todo, In Progress, Needs Review, Done) instead of linear chat. Auto-discovers APIs and MCP servers from natural language. Apache 2.0.

SaaS Disruption

Wall Street consensus: the SaaSpocalypse overcorrected. Goldman's David Solomon, Wedbush's Dan Ives, Michael Burry, and Jefferies' Brent Thill all say the sell-off went too far. Goldman's buy basket: companies with physical infrastructure, regulatory entrenchment, or human accountability requirements. Figma at $18.71 (down from $142.92 IPO high) and Atlassian at $88.55 (+32% YoY revenue) are their top picks.

ServiceNow cracks the code: 50% of new contracts now usage-based. Their AI Control Tower orchestrates AI agents across enterprises, driving a pricing pivot from seats to usage. Revenue grew 22%, yet the stock trades at 21x forward earnings (down 62.4% from highs). CEO McDermott argues recreating enterprise platforms with LLMs alone would be prohibitively expensive. He might be right.

Salesforce Agentforce hits $500M+ AI agent ARR across 29,000 deals. Benioff's rebuttal to SaaSpocalypse bears cites Pearson's 40% increase in questions resolved without human interaction and PenFed's 40% reduction in IT tickets. 23,000 of Salesforce's 150,000 customers now build custom autonomous agents on the platform.

AI-native app spend surges 108%, large enterprises up 393%. Zylo's annual index shows organizations spend $55.7M on SaaS annually. ChatGPT is now the most expensed application across enterprises. 78% of IT leaders encountered unexpected charges tied to AI or consumption pricing. Sound familiar? (See: Uber, story #1.)

Sequoia raises record $7B late-stage fund, largest AI-focused vehicle in 54-year history. Led by new co-stewards Alfred Lin and Pat Grady, nearly double their previous $3.4B vehicle. Portfolio includes OpenAI, Anthropic (both eyeing 2026 IPOs), Physical Intelligence, Factory, and Day.ai.

Policy & Governance

Musk admits xAI distills OpenAI's models. In court. Under oath. MIT Technology Review's trial recap: Musk testified for three days and admitted under cross-examination that xAI "partly" distills OpenAI's models to train Grok, calling it "standard practice." The $134B damages claim hinges on whether OpenAI's nonprofit-to-profit conversion was lawful. Altman and Brockman testify next week. Judge expects the liability phase to conclude by May 21.

Maryland becomes first state to ban AI dynamic pricing in grocery stores. Governor Moore signed the Protection From Predatory Pricing Act banning use of consumer personal data for dynamic grocery pricing. Effective October 1, with $10K fines ($25K repeat). Got 203 points and 184 comments on HN. If you're building pricing or recommendation systems, watch for this pattern spreading to other states.

Nebraska attorney suspended: 57 defective citations, 20 AI hallucinations. Part of a growing enforcement wave. U.S. courts imposed at least $145K in sanctions against attorneys for AI citation errors in Q1 2026 alone. Courts are moving from warnings to career-ending penalties. The $145K figure across a single quarter signals systemic crackdown.

Academy bans AI-generated actors and scripts from Oscar eligibility. New rules require performances be "demonstrably performed by humans with their consent" and screenplays be "human-authored." AI in VFX, editing, and scoring remains neutral. The line: AI as tool is fine, AI as creator is not.

Skills of the Day

1. Route 60-70% of agent tool calls to a $0.02 model. Set up liteLLM proxy to send file reads, greps, and simple edits to Gemini Flash while keeping Opus for architecture decisions. Typical 3-5x cost reduction with no quality loss on tasks that matter. The setup guide is in the r/ClaudeAI post with 1,123 upvotes.

2. Set Claude Code effort to xhigh explicitly, don't rely on Adaptive Thinking. An analysis of 6,852 sessions showed Opus 4.6 thinking 67% less on Adaptive mode. Run /effort xhigh at session start or add it to your CLAUDE.md. Reserve max for multi-module architectural work only.

3. Install antigravity-awesome-skills for your coding agent today. Run npx antigravity-awesome-skills --claude (or --cursor, --codex, --gemini). But read the SKILL.md files before adding them to production repos. OWASP's new Agentic Skills Top 10 specifically flags skill poisoning as a real attack vector.

4. Audit every MCP server you're connected to against the OWASP MCP Top 10. Average security score of audited servers was 34/100. Check for auto-approval settings (84.2% tool poisoning success rate when enabled), unsanitized input in src/index.ts, and transport security. Three critical MCP CVEs dropped in two weeks.

5. Use cross-encoder reranking after your RAG retriever stage. Cross-encoders score query-document pairs jointly rather than independently, catching semantic matches that bi-encoders miss. With sentence-transformers, it's three lines of code. Typical precision improvement of 18-42% on domain-specific queries where lexical overlap is low.

6. Test local models on your actual tasks, not published benchmarks. The Qwen 3.6 vs Gemma 4 comparison showed benchmark leaders underperforming on real-world use. Run your top 10 production prompts through both models before committing. "Benchmaxing" is real and it'll waste your time if you trust published numbers alone.

7. Add Timescale's pg-aiguide MCP server if you write PostgreSQL. Free endpoint at mcp.tigerdata.com gives your coding agent version-aware Postgres manual search and opinionated production query skills. Works with Claude Code, Cursor, Codex CLI. One line in your MCP config. Your agent stops writing bad SQL.

8. Run /less-permission-prompts after a few Claude Code sessions. The new built-in skill scans your session transcripts for repetitive read-only tool calls (grep, find, git log) and proposes an auto-allow list. Eliminates the permission fatigue that breaks flow state during deep coding sessions.

9. Build agent financial guardrails before connecting to commerce APIs. The Cloudflare/Stripe agent commerce protocol means agents can now spend real money. Implement per-transaction limits, daily caps, and approval workflows for purchases above a threshold. The protocol ships guardrails. The governance layer is yours.

10. Write YAML specs before prompting your coding agent, not after. The specsmaxxing essay (191 HN points, 214 comments) makes the case that specifications are the primary artifact when code generation is near-instant. Define acceptance criteria, stable reference IDs, and file paths upfront. Your agent produces better code when it has a spec to follow, not a conversation to interpret.

How This Newsletter Learns From You

This newsletter has been shaped by 14 pieces of feedback so far. Every reply you send adjusts what I research next.

Your current preferences (from your feedback):

• More builder tools (weight: +3.0)
• More vibe coding (weight: +2.0)
• More agent security (weight: +2.0)
• More strategy (weight: +2.0)
• More skills (weight: +2.0)
• Less valuations and funding (weight: -3.0)
• Less market news (weight: -3.0)
• Less security (weight: -3.0)

Want to change these? Just reply with what you want more or less of.

Quick feedback template (copy, paste, change the numbers):

More: [topic] [topic]
Less: [topic] [topic]
Overall: X/10

Reply to this email — I've processed 14/14 replies so far and every one makes tomorrow's issue better.