monroewalker
Joined 6 years ago
Joined 6 years ago
"When we started the log analysis, we first used frontier models behind commercial APIs. This did not work: the analysis requires submitting large volumes of real attack commands, exploit payloads, and C2 artifacts, and these requests were blocked by the providers' safety guardrails, which cannot distinguish an incident responder from an attacker. We ran the forensic analysis instead on GLM 5.2, an open-weight model, on our own infrastructure. This had a second benefit: no attacker data, and none of the credentials it referenced, left our environment."
It’s just a basic IntelliJ plugin which provides an infinite canvas to add code bookmarks to. I work on a large code base and often have to take on tasks involving lots of unfamiliar areas of code and components which influence each other only through long chains of indirection. Having a visual space to lay things out, draw connections, and quickly jump back into the code has been really helpful
The canvas and UI is built using Java AWT since that’s what IntelliJ plugins are built on, but it occurred to me that I could just throw in a web view and use any of the existing JS libraries for working on an infinite canvas. React Flow has seemed like the best option with tldraw being what I’d fallback to.
But then.. if the canvas is built with web technology then there’s no reason to keep it just within an IntelliJ plugin vs just a standalone web app with the ability to contain generic content that might open files in IntelliJ or any other editor. I’m pretty sure the “knowledge database on a canvas” thing has been done a number of times already so I want to also see if there are existing open source projects that it’d be easy enough to just add a special node type to
This was great for me though because this is something I've had in mind for a while but never considered quite useful enough to be worth the time it'd take to learn about IntelliJ plugin development + the Java AWT knowledge required to create a canvas app like this
The demo interactions are recorded, which is mentioned in their disclaimer under the demo UI. What isn't mentioned though is that they include past conversations in the context for the model on future interactions. It was pretty surprising to be greeted with something like "welcome back" and the model being able to reference what was said in previous interactions. The full disclaimer on the page for the demo is:
" 1. Microphone permission is required. 2. Calls are recorded for quality review but not used for ML training and are deleted within 30 days. 3. By using this demo, you are agreeing to our "
edit: Actually this has been posted quite a few times already and had good visibility a couple days ago: - https://news.ycombinator.com/item?id=43200400 Others: https://hn.algolia.com/?q=sesame.com
Post content:
_____
I wish we didn’t need these again, but here is the honest version of Anthropic’s biology announcement (Caveat: I haven’t worked in bioinformatics for many years.) The good: Anthropic ran ~950 Claude agents over a large biological sequence database. Claude searched, wrote code, compared sequences and genomic neighborhoods, and found an interesting pattern that apparently had not been noticed before: a known reverse transcriptase associated with another gene and a repetitive DNA array.
That is cool. Automating this kind of open-ended bioinformatics search at scale is useful, and Claude may have found a lead a human would have missed.
But: Claude did not do a biological experiment. It searched databases and analyzed data.
Humans then took the candidate into the wet lab. And the wet-lab result so far is modest: they showed that the repeat array produces short RNAs.
We still don’t know what the system does. No function, mechanism, phenotype, targeting, defense activity, or programmability has been demonstrated.
This is also where the CRISPR framing gets ahead of the result. Right now, “it has some features reminiscent of known programmable systems” is a hypothesis for what to investigate next, not a discovery that it behaves like CRISPR.
And there is a missing baseline: bioinformatics has had tools for finding unusual gene neighborhoods and candidate systems for years. The interesting comparison is 950 Claude agents vs. an expert using the best existing computational pipelines - not Claude vs. someone manually looking through 200,000 sequences.
So my honest announcement would be:
Claude autonomously found an interesting candidate for a previously uncharacterized biological system. A small human wet-lab experiment confirmed that part of the candidate is expressed. We don’t yet know what it does.
That is a good result.
But in a regular biology lab, this isn’t the finished paper. It is the result you show at lab meeting and say: “This looks interesting. Now we need to figure out what the hell it does.”
Maybe that next step leads to a major discovery. But that discovery hasn’t happened yet.