jess @_JessicaSachs - Twitter Profile

about 10 hours ago

My OpenAI contract has wrapped up, and I'm looking for my next role. For nearly two years, I've been building robust AI chats, MCP tools, AI UI integrations (MCP Apps), and more. I wrote some of the first Codex plugins: Their plugin evaluator, a comprehensive data visualization plugin, and more. If you or your team are looking for someone to drive your AI efforts – AI powered apps, backend AI processes, code assistant optimizations, AI driven business processes, etc. – I'd love to chat.

3

26

5

9

5K

_jessicasachs retweeted

Justin Schroeder

@jpschroeder

3 months ago

Important takeaways from Claude’s source code: 1. Much of Claude Code’s system prompting is in the source code. This is actually surprising. Prompts are important IP, and I would have thought a sophisticated organization like Anthropic would have performed much or all of their prompt assembly in the server-side harness. 2. Claude Code uses axios, which was also just hacked. Reminder: supply chain attacks are part of closed-source distribution too, and you won’t even know what version of an affected package is being used. 3. The source has a lot of really good comments. These are obviously not for human consumption but for LLMs to understand the purpose of various chunks of code. In the code autocomplete era, most of us engineers hated how many comments were left by LLMs, but perhaps we’ve overcorrected. This looks like a great way to provide context to code outside of the AGENTS.md/CLAUDE.md files. 4. Most folks already know this, but less tools == better results. CC has < 20 tools in normal coding: AgentTool, BashTool, FileReadTool, FileEditTool, FileWriteTool, NotebookEditTool, WebFetchTool, WebSearchTool, TodoWriteTool, TaskStopTool, TaskOutputTool, AskUserQuestionTool, SkillTool, EnterPlanModeTool, ExitPlanModeV2Tool, SendMessageTool, BriefTool, ListMcpResourcesTool, and ReadMcpResourceTool. 5. The “Bash” tool is the crown jewel of Claude Code. A significant amount of deterministic parsing and processing occurs to determine the “type” of commands being run. 6. For better or worse, Claude Code is *all* TypeScript/React with rather explicit Bun bindings. 7. Just because the source is now “available” *DOES NOT MEAN IT IS OPEN SOURCE*. You are violating a license if you copy or redistribute the source code, or use their prompts in your next project! Don’t do that! My overall takeaway: it’s a really well laid-out codebase that is carefully organized to let agents work on it effectively. Direct human intervention here is minimal, but, like with all good projects, the human engineering is still apparent. I’m a bit surprised by some of the shortcuts Claude Code makes, like its prompt assembly being rather messy. Perhaps they have tooling on their side that helps with this introspection, but as it stands, it seems LLMs would struggle to iterate on the prompting because it’s not evident how a given set of parameters assembles a prompt without actually running it. It’s also surprising that the prompts are even in this source code. Keep in mind that even though this is the first time we’ve gotten a proper full-source dump, it has never been impossible to read Claude Code’s prompting since it was part of the actual distributed package — that’s surprising. There might still be a lot of prompting on the server that also gets added (unclear at this point), but there is certainly more than I would have expected in the CLI tool itself.

73

1K

114

1K

254K

_jessicasachs retweeted

J.D. Flynn

@JDDoesDev

5 months ago

IT WORKS! Creodrop works with CUSTOM DOMAINS! This is HUGE! Thanks everyone who was around when this happened. This was AMAZING! https://t.co/slKzGMnj6O

2

1

0

687

jess

@_jessicasachs

Who to follow

Last Seen Users on Sotwe

Trends for you

Most Popular Users