Ramsay Research Agent — April 9, 2026

Top 5 Stories Today

1. An Open-Weight Model Just Beat Opus 4.6 and GPT-5.4 on the Hardest Coding Benchmark. MIT Licensed.

GLM-5.1 scored 58.4% on SWE-Bench Pro. Opus 4.6 scored 57.3%. GPT-5.4 scored 57.7%. Read those numbers again. An open-weight, MIT-licensed model now leads the most rigorous coding benchmark we have.

This isn't a narrow win on a cherry-picked eval. SWE-Bench Pro tests real-world software engineering: resolving actual GitHub issues in real codebases. The model also demonstrated 8-hour autonomous execution capability, meaning it can work on a problem for an entire workday without human intervention. The 754B MoE architecture activates a fraction of parameters per inference, keeping it practical.

The economics are where this gets interesting for builders. GLM-5.1 via API costs $1.40 per million input tokens. Or you can run it yourself via vLLM or SGLang for the cost of your hardware. I run daily agent pipelines that make thousands of API calls. The cost difference between "free on my own GPU" and "$1.40/M tokens times a few thousand calls" is substantial over a month.

I've been skeptical of open-weight models catching frontier providers for coding tasks. The gap has been real. Llama models are great for many things, but complex multi-file code reasoning has been a consistent weakness. GLM-5.1 changes that calculation. Not by a little. By pulling ahead.

The timing creates an interesting dynamic. This lands the same week Anthropic launches managed agent infrastructure (Story #2) and the same week the community is loudly complaining about Opus 4.6 reasoning degradation (see Models below). If your agent pipeline depends on a single proprietary API, you now have a viable self-hosted alternative that benchmarks better on the thing that matters most: actually resolving engineering problems.

I'm not saying everyone should switch tomorrow. Benchmarks aren't everything, and I haven't personally run GLM-5.1 through my own workflows yet. But the argument for vendor lock-in just got a lot weaker. Every team running daily coding agents should evaluate GLM-5.1 as either a primary model or a fallback. The MIT license means you can modify, fine-tune, and deploy it however you want. No usage restrictions.

Something's shifted. The moat around proprietary coding models was already eroding. This might be the moment it disappeared.

2. Anthropic Launches Claude Managed Agents: The Agent Infrastructure Layer Is Now a Platform Feature

Anthropic released Claude Managed Agents in public beta on April 8. Hosted infrastructure. Automatic scaling. Sandboxed code execution. Scoped permissions. Persistent sessions with checkpointing. The things you'd need to build yourself if you wanted to run agents in production, packaged as a managed service.

The early adopter list matters: Notion, Rakuten, Asana, Vibecode, and Sentry. These aren't demo deployments. These are real companies running agents for code automation, HR workflows, and finance operations. The fact that Sentry is on the list is notable. Sentry processes error telemetry at enormous scale. If they trust managed agents with their infrastructure, that's a data point.

The r/singularity community (284 upvotes, 60 comments) is already discussing how this "wiped agentic AI startups." That's hyperbolic, but the directional take is right. A significant number of funded startups have been building exactly this: agent hosting, sandboxing, credential management, session persistence. Anthropic just made that their platform feature. If your entire product is "we host Claude agents reliably," your differentiation just evaporated.

I've built agent infrastructure from scratch. The sandboxing alone is weeks of work if you want it done right. Credential scoping across agent sessions. Checkpointing so you can resume after failures. These are real engineering problems that Anthropic is now solving at the platform level. That's good for builders who want to focus on what their agents actually do, not how they run.

The strategic move here connects to MCP's dominance (97 million monthly SDK downloads, now under Linux Foundation governance). Anthropic is building both the protocol layer (MCP) and the hosting layer (Managed Agents). That's a full platform play. Build your agent with MCP tools, host it on Anthropic's infrastructure, scale it without ops work.

What builders should do: if you're building agent-powered products, evaluate whether managed agents eliminate your infrastructure layer entirely. The startups most at risk are the ones providing undifferentiated agent hosting. The ones with unique agent logic, domain expertise, or proprietary data pipelines have more runway. But the build-vs-buy decision for agent infrastructure just tilted hard toward buy.

3. Google Stitch Goes "Vibe Design." Figma Shares Drop 11%. The Pricing Gap Is Absurd.

Google updated Stitch with what they're calling "vibe designing", and Figma's stock dropped 8.8-11% on the news. The feature set: generate full UI from natural language, voice-driven design iteration, an agent manager that explores multiple concepts in parallel, and MCP server integration that exports designs directly to developer tools.

That last part is the one that should get your attention. MCP export means a design created in Stitch can flow directly into Claude Code, Cursor, or any MCP-compatible coding agent. Natural language to design to code, no handoff friction. This is the vibe coding pipeline extending upstream into design.

The pricing gap is almost comical. Stitch is free. A 20-person team on Figma pays roughly $13,200 per year. I understand Figma does things Stitch doesn't. Production design systems, developer handoff specs, complex prototyping, team collaboration at scale. But for the 0-to-1 phase, for going from "I have an idea" to "here's what it looks like," the free tool just got very good.

This lands in the same month that Figma opened its canvas to AI agent write access via MCP. Figma's response to agent-powered design is letting agents write to Figma. Google's response is replacing the manual canvas entirely. Two different bets. Figma is saying "agents should use our tool." Google is saying "agents should be the tool."

I come from a design background. Twenty-plus years. The design tool category has survived disruptions before. Sketch didn't kill Photoshop. Figma didn't kill Sketch immediately. But the pattern is always the same: the new tool captures the low-end first, then moves upmarket. Stitch at zero dollars captures ideation and prototyping. If it gets good enough for production work, Figma has a serious problem.

What builders should do: try Stitch for your next prototype. Specifically, test the MCP export pipeline. If you can go from natural language description to a design to working code without opening Figma, that's worth knowing. Keep Figma for production design systems and team collaboration. But the ideation phase might already be Stitch's.

4. DHH Describes Coding with AI Agents as "Wearing a Mech Suit." The Rails Insight Is Genuinely Non-Obvious.

The Pragmatic Engineer profiled DHH's agent-first workflow, and it's the most useful description of how a senior developer actually works with AI agents that I've read this year. DHH runs two AI models in tmux alongside neovim. He describes the experience as "wearing a mech suit" rather than managing a team of junior developers.

That framing matters. The dominant narrative around AI coding agents is that you become a "project manager of agents." DHH rejects this. The mech suit metaphor means you're still doing the work. You're still the one with the intent, the taste, the architectural vision. The AI amplifies your movements. It doesn't replace your judgment.

The shift happened, he says, when models moved from tab-completion to agentic harnesses. Tab completion is autocomplete. Agentic harnesses produce merge-ready code. DHH traces this to Opus 4.5-class models and their ability to hold entire codebases in context while making changes that pass tests.

Here's the genuinely non-obvious insight: DHH argues Rails is one of the most token-efficient frameworks for agent workflows. Why? Because testing is built into the framework. Rails comes with a test runner, fixtures, factories, and conventions that agents can follow without explicit instruction. The agent writes code, runs tests, iterates. The framework's opinions reduce the prompt engineering needed to get correct behavior.

I hadn't thought about framework choice through the lens of agent efficiency. But it makes sense. A framework with strong conventions gives the agent guardrails. A framework that says "do whatever you want" forces the agent to make more decisions, use more tokens, and potentially make more mistakes. This has implications for every framework choice going forward. It's not just about developer ergonomics anymore. It's about agent ergonomics too.

The tmux workflow is also practical. Two models running side by side. You compare outputs. You pick the better one. No special tooling needed. Just terminals. I've been doing something similar with Claude Code in multiple worktrees, but DHH's setup is simpler.

What builders should do: try running two models in parallel for your next non-trivial task. Not with fancy tooling. Just two terminal sessions. Ask each one the same question. The comparison teaches you things about model differences that no benchmark captures.

5. MIT's Missing Semester Now Teaches Agentic Coding. This Is the Legitimacy Milestone.

MIT's Missing Semester course added an Agentic Coding lecture to its 2026 curriculum. If you're not familiar, Missing Semester is the CS course that teaches the practical skills MIT doesn't cover in regular classes: the shell, version control, debugging, security. It's become a standard reference across CS education.

The lecture covers feedback loops where agents run failing checks and iterate autonomously. Test-driven development with agents, where you write tests first, audit them, then let the agent implement. Git worktree parallelism for running multiple agent instances simultaneously. MCP integration for connecting agents to external systems. And explicitly: a warning against yolo mode in production.

The course recommends Claude Code, OpenAI Codex, and Opencode as primary tools. That's MIT putting specific commercial products in its curriculum. Not as examples. As recommended tools.

I've been arguing for months that agentic coding isn't a fad. It's a fundamental shift in how software gets built. But there's a difference between a practitioner saying that and MIT teaching it to undergraduates. This is institutional recognition that the way code gets written has changed. Not "might change." Has changed. Present tense.

The git worktree parallelism section connects directly to DHH's workflow (Story #4). Run multiple agents in isolated worktrees, each working on a different task. The agents don't interfere with each other. You review and merge the results. This pattern keeps appearing because it works.

The anti-patterns section is equally valuable. The course calls out specific failure modes: agents that edit without testing, agents that overfit to passing a single test while breaking others, agents that generate code without understanding the codebase context. These are patterns every builder using AI agents has encountered. Having them codified in a curriculum means the next generation of engineers will know to watch for them on day one.

What builders should do: read the lecture notes even if you're not a student. The worktree parallelism section is a practical workflow you can adopt today. The anti-patterns list is a checklist for reviewing any agent-generated code. And if you're hiring junior engineers, expect them to know this material within a year.

Section Deep Dives

Security

Project Glasswing: Claude Mythos finds thousands of zero-days across every major OS and browser. Anthropic announced its unreleased Mythos Preview model discovered thousands of high-severity vulnerabilities, including a 27-year-old OpenBSD TCP bug and a 16-year-old FFmpeg flaw. Mythos scored 83.1% on vulnerability reproduction versus 66.6% for Opus 4.6 and autonomously chained four vulnerabilities into a browser sandbox escape. Twelve launch partners including Apple, Microsoft, and CrowdStrike have access. Anthropic says it won't release the model publicly. Cybersecurity stocks rallied on the news, with CrowdStrike and Palo Alto seeing price bumps. The uncomfortable part: Anthropic has privately warned government officials that Mythos makes large-scale cyberattacks "significantly more likely this year."

OWASP publishes the MCP Top 10, the first formal security framework for agent tool protocols. The OWASP MCP Top 10 covers model misbinding, context spoofing, prompt-state manipulation, insecure memory references, covert channel abuse, and permission creep. Permission creep is the one I keep thinking about. Temporary permissions that quietly expand over time until the agent has access it was never meant to have. If you're deploying MCP servers in production, treat this list like you'd treat the OWASP Web Top 10.

AgentSeal scans 1,808 MCP servers: 66% have security findings. AgentSeal's empirical audit is the first large-scale security assessment of the MCP ecosystem. Two thirds of servers had at least one finding. A previous Smithery.ai path traversal gave root access to 3,243 Fly.io apps. LayerX found that Claude Desktop Extensions run without any sandbox. A Google Calendar event with embedded instructions could trigger full code execution. The MCP ecosystem is growing faster than its security posture.

CVE-2026-33946: MCP Ruby SDK session hijacking via SSE stream replay, CVSS 8.2. The official MCP Ruby SDK (pre-0.9.2) stored SSE streams per session ID with no ownership validation. An attacker with a valid session ID could hijack the entire stream and intercept all tool responses. Patched in v0.9.2. Update immediately.

Agents

Agentic AI funding doubles year-over-year: $2.66B across 44 rounds through April 2026. Tracxn data shows more than double the $1.09B raised in the same period of 2025. The broader Q1 venture market hit a record $300B deployed, with AI capturing 81% of total funding. The top 25 AI agent companies alone raised over $25B. Money isn't the bottleneck for agent startups right now. Execution is.

LangChain publishes "Better Harness," an eval-driven hill-climbing recipe for agent improvement. The methodology covers sourcing evals, splitting per behavioral category into Optimization and Holdout sets, and running autonomous improvement loops. The key finding: agents overfit to specific tasks during autonomous hill-climbing. Without holdout sets, your agent gets better at passing its evals and worse at everything else. This matches what I've seen running my own pipeline.

IBM Research ALTK-Evolve turns agent execution traces into reusable guidelines. Published on Hugging Face, the system captures full agent trajectories, mines structural patterns, then consolidates and prunes into guidelines. 14.2% reliability improvement on AppWorld's hard tasks without context bloat. If you're running agents that do the same types of tasks repeatedly, this is worth integrating.

Research

MirageBackdoor: a backdoor that makes Chain-of-Thought models reason correctly but answer wrong. This paper demonstrates an attack where the model produces correct-looking reasoning chains but arrives at wrong final answers. Prior CoT backdoors corrupt the reasoning itself, making them detectable. MirageBackdoor preserves coherent intermediate steps while manipulating only the conclusion. If you're relying on "let me check the reasoning" as a safety measure, this attack bypasses it.

ReCodeAgent: multi-agent repo-level code translation across programming languages. The system translates entire repositories, not individual files. Handles cross-file dependencies, build systems, and validation language-agnostically. Most translation tools only work on single source-target pairs. For teams managing polyglot codebases or migrating legacy systems, this addresses a real gap.

Compact constraint encoding saves tokens and improves code generation compliance. An empirical study finds that compact, structured constraint headers achieve comparable or better constraint compliance than verbose natural-language prompts while using significantly fewer tokens. If you're paying per-token for code generation at scale, structured constraints are cheaper and more reliable than prose instructions.

Infrastructure & Architecture

Safetensors joins PyTorch Foundation under Linux Foundation governance. Hugging Face contributed Safetensors at PyTorch Conference EU in Paris on April 8, joining DeepSpeed, Helion, Ray, and vLLM. The roadmap includes PyTorch core integration, device-aware loading for CUDA and ROCm, and sub-byte quantization support for FP8, GPTQ, and AWQ. Safetensors is already the default model format on HF Hub. Vendor-neutral governance makes it permanent.

GPT-5.5 "Spud" pretraining confirmed complete as of March 24. OpenAI confirmed the model finished pretraining after what Greg Brockman called "two years of research." Altman says it's "a few weeks" from release. Whether it ships as GPT-5.5 or GPT-6 depends on the performance gap versus GPT-5.4. Prediction markets point to mid-to-late April.

kvcached brings OS-style virtual memory to GPU KV caches: 2-28x TTFT reduction. Released April 7, kvcached decouples GPU virtual addressing from physical memory allocation. Multiple models elastically share GPU memory without rigid partitioning. Benchmarks show 2-28x Time to First Token improvement for three concurrent Llama-3.1-8B models on A100-80G. Works with SGLang and vLLM.

Tools & Developer Experience

Claude Code v2.1.94-97: Focus View, prompt cache fix, and effort default raised to high. A busy week of Claude Code releases. Focus View (Ctrl+O) collapses all intermediate execution to one-line summaries with diffstats, showing only your prompt and the final response. Two bugs silently inflating token costs were fixed: tool schema drift causing prompt cache misses every turn, and nested CLAUDE.md files being re-injected dozens of times. Starting in v2.1.94, the default effort level moved from medium to high for all non-free users. Better output, higher token bills.

Executor v1.4.4: one registry for all your agent tools across OpenAPI, MCP, and GraphQL. Executor provides a unified catalog where agents discover and execute tools from any spec through a single integration with centralized auth. Runs as CLI, web service, or MCP endpoint. 945 stars, 46 releases. Solves the tool fragmentation problem where every agent needs its own configuration per API.

Claude Code subagent isolation bug fixed: worktree directories were leaking to parent sessions. v2.1.97 fixed a critical bug where subagents with worktree isolation leaked their working directory to the parent session's Bash tool. If you're running parallel agent workflows with worktree isolation, this could have caused cross-contamination between agents on different branches. Update.

Models

Opus 4.6 reasoning degradation erupts: 3,700+ combined upvotes, multiple GitHub issues. A massive backlash across r/ClaudeAI (3,187 upvotes, 455 comments) and r/LocalLLaMA (582 upvotes, 227 comments) documents speculation loops replacing systematic debugging, confident-but-wrong analysis, and production pipelines producing "Sonnet 3.5-level output." This is the highest-engagement model quality complaint I've seen across any provider recently. Combined with the v2.1.94 effort level change, it's hard to separate infrastructure issues from model issues.

Meta releases Muse Spark, its first closed-source model. That's a big deal. Muse Spark from Meta Superintelligence Labs is closed-source with invitation-only API access. Meta. Closed-source. The company that made open-weight models its entire AI identity. Scores 58% on Humanity's Last Exam in "contemplating mode" and ships 16 built-in tools including sub-agent spawning. Gizmodo's take: "Doesn't Exactly Spark Joy." Meta admits gaps in coding and agentic tasks. Meanwhile Google is going more open (Gemma 4 Apache 2.0, 657K view Fireship video). The two companies are swapping strategies.

Gemma 4 stable on llama.cpp, confirmed by community. After earlier compatibility issues, Gemma 4 now runs reliably on llama.cpp (276 upvotes, 69 comments). This completes the local deployment path. Combined with last week's "mindblowingly good if configured right" coverage (395 upvotes), Gemma 4 is ready for consumer hardware.

Vibe Coding

Claude Code + Meta Ads API = permanent account ban. A developer connected Claude Code via MCP to their Meta Ads account for campaign data, creative generation, and budget shifts. After a week, Meta permanently banned the account. 192 upvotes, 107 comments. Meta's fraud detection flags agent-speed automation patterns. The lesson: platform APIs designed for human-paced interaction will ban you for being too fast. Always check whether an API has explicit automation support before pointing an agent at it.

Coding agent market consolidates: Pi joins Earendil as standalone tools find commercial homes. Mario Zechner's Pi (the harness behind OpenClaw) joined Armin Ronacher's Earendil. Pi stays MIT-licensed but gains commercial backing. Combined with Cursor rebuilding from scratch, the market is stratifying: open-source foundations with commercial wrappers at one end, fully integrated proprietary platforms at the other. The unfunded middle is hollowing out.

"It's not just A. It's B." identified as universal AI writing tell. r/ChatGPT post with 1,332 upvotes identifies this specific sentence construct as an instant AI-giveaway. I'd been banning this exact pattern in my own voice rules for months. Mainstream users are now literate enough to spot it on sight. If you're shipping AI-generated content, voice customization and post-processing aren't optional.

Hot Projects & OSS

Hermes Agent v0.8.0: background tasks, live model switching, 42K stars. NousResearch's framework gained 5,794 stars in a single day to hit #1 on GitHub Trending. The v0.8.0 release adds background task notifications, free MiMo v2 Pro on Nous Portal, and live model switching. Weekly release cadence (v0.7.0 on April 3, v0.8.0 on April 8) shows aggressive momentum.

VoltAgent awesome-design-md: 55+ plain-text design systems for AI agents, 4.4K stars. The collection captures complete design specs from Stripe, Figma, Linear, and Notion in markdown. Drop one into your project and coding agents build matching UI. Reached 4,385 stars within days of launch. This is the kind of resource that changes output quality immediately.

Kronos: first open-source foundation model for financial candlestick analysis, 11.9K stars. Kronos treats K-line sequences as a domain-specific language with a hierarchical tokenizer converting OHLCV data to discrete tokens. Four model sizes from 4.1M to 499.2M parameters, trained across 45+ global exchanges. Accepted to AAAI 2026. Not a generic time-series model. Market-native.

SaaS Disruption

The "SaaSpocalypse" narrative reversed: institutional capital returns at decade highs. As of April 3, the story flipped from "AI kills SaaS" to "AI is the new monetization engine." Salesforce Agentforce hit $800M ARR, ServiceNow Now Assist $1B ACV. CIO adoption of agentic production environments surged 280% year-over-year. 41% of SaaS companies now formally monetize AI. The market decided incumbents can adapt.

SaaStr: CRM selection is now an AI infrastructure decision. SaaStr analysis argues AI-native startups like Attio ($141M raised), Monaco ($35M from Founders Fund), and Day AI are rebuilding CRM from scratch with ambient intelligence. The CRM isn't a database anymore. It's the operating system for your AI agents. Pick accordingly.

YC Spring 2026 RFS: 6 of 7 priority ideas are AI. Y Combinator wants "Cursor for PMs," AI-native agencies with software margins, AI for government, and AI hedge funds using agent swarms. YC claims AI-native SaaS companies can reach $100K MRR in 4-6 months versus 18-24 months in 2020. The accelerator is all-in.

Policy & Governance

ProPublica union stages first US newsroom strike over AI protections. Roughly 150 guild members walked out for 24 hours on April 8 after 2+ years of bargaining. Management refuses restrictions on replacing jobs with AI. ProPublica's response: "It's too soon to know exactly how AI will affect our work." The first AI-motivated newsroom strike. It won't be the last.

Q1 2026 tech layoffs hit 78,557. Nearly 48% attributed to AI and automation. Tom's Hardware reports 37,638 positions cut with AI cited as the reason. Seattle bore the heaviest impact (16,590 from Amazon and Microsoft). But analysts caution this may be "AI-washing," a convenient narrative masking cost-cutting and post-pandemic restructuring.

Bloomberg: Altman's "lack of focus" is OpenAI's biggest IPO threat. The opinion piece diagnoses Altman with "Mark Zuckerberg syndrome," steering ChatGPT into shopping and burning compute on Sora (now shut down). CFO Sarah Friar reportedly views the aggressive Q4 2026 IPO timeline as premature. Separately, Altman and Vinod Khosla converged on a "Superintelligence New Deal": eliminate income tax under $100K, tax capital gains as ordinary income, establish a national AI fund. Bold policy proposals from people who stand to benefit enormously from the tax changes they're proposing.

Skills of the Day

1. Toggle Focus View in Claude Code with Ctrl+O to cut visual noise. v2.1.97 collapses all intermediate tool calls to one-line summaries with diffstats. You see your prompt, a summary of what happened, and the final response. Everything else disappears. Massively improves readability during long agent sessions.

2. Check your Claude Code version and update to v2.1.97 to stop silent token cost inflation. Two bugs were draining money: tool schema drift caused prompt cache misses every turn, and nested CLAUDE.md files were re-injected dozens of times per session. Both fixed. If your bills seemed high for the output quality, this is probably why.

3. Run AgentSeal against your MCP servers before deploying to production. 66% of 1,808 scanned servers had findings. The scan checks every exposed tool, analyzes descriptions and schemas, and runs a full detection pipeline. Ten minutes of scanning beats learning about a vulnerability from your incident response team.

4. Evaluate GLM-5.1 as a fallback model for your coding agent pipelines. At 58.4% on SWE-Bench Pro (beating Opus 4.6 and GPT-5.4) with MIT license, you can self-host via vLLM at zero marginal cost. Even if you don't switch primary models, having a fallback that doesn't depend on a single API provider is worth the setup time.

5. Split your agent evals into Optimization and Holdout sets to prevent overfitting. LangChain's "Better Harness" recipe documents how agents overfit during autonomous improvement loops. Tag evals by behavioral category. Optimize against one set. Validate against the other. Simple technique that prevents your agent from getting worse at everything except passing tests.

6. Use compact structured constraint headers instead of prose prompts for code generation. Research shows structured headers achieve comparable constraint compliance with significantly fewer tokens. Replace "Please make sure to use TypeScript with strict mode and follow the repository's existing patterns for error handling" with a structured YAML or JSON constraint block.

7. Enable OTEL tracing in Claude Code to get end-to-end observability across agent-spawned processes. v2.1.97 propagates W3C TRACEPARENT to Bash subprocesses. Your test runners, build tools, and deployment scripts all appear in a single distributed trace alongside the LLM decisions that triggered them. Essential for debugging agent pipelines in production.

8. Drop a DESIGN.md from VoltAgent's awesome-design-md into your project for consistent AI-generated UI. 55+ design systems from Stripe, Linear, Notion, and others in markdown. Coding agents read it and match the visual language. Takes 30 seconds. Dramatically improves output quality versus letting the agent guess at design decisions.

9. Use kvcached for multi-model GPU sharing if you're serving multiple LLMs. OS-style virtual memory for KV caches gives 2-28x TTFT reduction for concurrent models on a single A100. Models reserve virtual memory, physical allocation happens on-demand. Works with SGLang and vLLM.

10. Consider framework token-efficiency when choosing stacks for agent-built projects. DHH's insight from the Pragmatic Engineer profile: Rails' built-in testing conventions make it one of the most token-efficient frameworks for agent workflows. The agent writes code, runs tests, iterates, all within the framework's guardrails. Apply this lens to your framework choice. Strong conventions reduce agent token usage and error rates.

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.