Mary Baptista Martinez @MaryLBMC

@GergelyOrosz I’ve started requiring my agents to use TDD. I agree that reviewing PRs in the age of AI feels antiquated- I for one would love to see them go away. Sadly, I think they are still necessary. Shifting left is giving me more confidence though I’m still reviewing 🫠

For my first post, I’m sharing a letter @NVIDIA signed on why open models matter. AI will transform every industry, power every company, and be built by every country. Open models strengthen safety and cybersecurity, accelerate innovation and diffusion, and enable sovereignty. The world needs both frontier closed models and frontier open models. images.nvidia.com/pdf/Open-Weigh…

keyboard_arrow_left Previous keyboard_arrow_right Next

@GergelyOrosz I’ve been thinking about this and I think I am going to try adding to my Claude.md to require agents to use TDD as a shift-left strategy. So that bugs are caught early before code review. Obviously not everything is 100% testable so there will be gaps.

So, so excited to put this to work. Have been a @1Password user for years and cannot wait to let my agents use it as well.

1Password @1Password

2 weeks ago

AI agents are booking travel, signing into websites, and acting on your behalf. That creates a new security problem: until now, letting an agent log in meant exposing your credentials to the model. Today, with @AnthropicAI, we're changing that. 1Password for @claudeai lets

keyboard_arrow_left Previous keyboard_arrow_right Next

119 239 2K 539K 1K

Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things. I think many of these automations have become even more important now. This is true for a number of reasons. First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time. Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time! Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation. Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.

We're introducing Claude for Teachers: free access to premium Claude capabilities for verified K-12 educators in the US, with a library of teaching skills and a direct connection to evidence-based curricula, mapped to academic standards in all 50 states. claude.com/solutions/teac…

@SpaceXAI Wow this is really bad and disappointing

@levelsio Why not just use MyFitnessPal? You can scan the items UPC code to get calorie details. If you use an Apple Watch you can get your Total Energy Expenditure. In Health app look at Active Energy + Resting Energy. This is your maintenance calories. Then -500 cals for your goal

@twostraws Thanks for sharing this! Qq: does it also support markdown tables?

@fidjissimo Thank you for your openness with sharing your story. Health is somethingwe cannot ignore. My partner also lives with a chronic disease and it is not easy. One thing that has made a huge difference in her health is working with a naturopathic doctor. I highly recommend it!

@adamlyttleapps Love this! The hard part is getting everything to the finish line

@steipete @ATT Try Mint mobile

This is a new paradigm for interacting with Claude that is significantly more "inline" with all the other human activity org-wide. Once you do all of the under the hood engineering work to make this "just work" (e.g. across tools, integrations, compute environments, memory, security, etc.), Claude basically joins the team in a seamless way - you can talk to it as you would talk to a person and it can help with a very large variety of workloads. Imo this is the 3rd major redesign of LLM UIUX. The first paradigm was that the LLM is a website you go to, the second was that it is an app you download to your computer. This third one is that it is a self-contained, persistent, asynchronous entity with org-wide tools and context, working alongside teams of humans. It really takes a while to wrap your head around it, but it works and it is awesome.

Claude @claudeai

a month ago

Introducing Claude Tag, a new way for teams to work with Claude. In Slack, Claude joins as a team member with access to the channels and tools you choose. Tag Claude in and delegate tasks to it while you focus on other work.

2K 2K 28K 20.6M 12K

On Claude Team and Claude Enterprise, you can now use Claude Code to deploy HTML sites and share these with your teammates! This has changed how we work internally. Artifacts is great format for communicating architecture changes, data analyses, and new prototypes.

Claude @claudeai

a month ago

New in Claude Code: Artifacts. Interactive pages built from your session, like a PR walkthrough or a living project dashboard, shared with your team at a private link. Available in beta on Team and Enterprise plans.

747 1K 19K 5.3M 8K

@om_patel5 Source?

🚨How do you index the entire Linux kernel (28M lines of code) for an AI agent in 3 minutes? You stop letting the agent read files one by one. There is a fascinating new open-source release called codebase-memory-mcp. It's a code intelligence engine that swaps traditional file-searching for high-speed AST knowledge graphs. What makes this project stand out is the research behind it. Evaluated across 31 real-world repositories (detailed in arXiv:2603.27277), the architectural shift yields massive efficiency gains: → 99% reduction in tokens for structural queries → 83% answer quality across complex tasks → 2.1x fewer tool calls required It maps functions, classes, HTTP routes, and cross-service links into a graph. When the agent needs context, it queries the graph directly. Security is prioritized too: everything happens 100% locally on your machine via a single static binary. It runs entirely locally. No Docker, no Ollama, no API keys. You download the binary, restart your agent, and it just works. Are we one good index away from cutting AI dev costs to zero? Paper and Repo links in the thread ↓

Claude Mythos is Insane! ❤️‍🔥Just recorded a 12-min tutorial on how to build animated, award-Winning websites with Claude Fable 5!

Quite strange: @github just logged out all active sessions for all its users.

x.com/i/article/2063…