Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pacjam
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
by
pacjam
9mo ago
Oh interesting - it's just a .mp4. I put it on vercel blob storage just as a fast way to make it easily embeddeded in our CMS system, but I think I put it on the wrong Vercel account and the bucket got rate limited (happened a few hour
2.
▲
by
pacjam
9mo ago
I think it's mostly complimentary, in the same way a linear MCP would be complementary to a MemGPT/Letta-style memory system I guess the main potential point of confusion would arise if it's not clear to the LLM / agent
3.
▲
by
pacjam
9mo ago
Yes! Letta Code also has a "danger" mode, it's `--yolo`. If you're running Claude Code in a sandbox in headless mode, Letta Code has that too, just do something like `letta -p "Do something dangerous (it's just
4.
▲
by
pacjam
9mo ago
Cool, let us know what you think! Would recommend trying w/ Sonnet/Opus 4.5 or GPT-5.2 (those are the daily drivers we use internally w/ Letta Code)
5.
▲
by
pacjam
9mo ago
Yeah exactly - it's all just tokens that you have full control over (you can run CRUD operations on). No hidden prompts / hidden memory.
6.
▲
by
pacjam
9mo ago
I'm curious - how do you currently manage this `llm.md` in the tooling you use? E.g., do you symlink `AGENTS/CLAUDE.md` to `llm.md`? Also, is there any information you duplicate across your project-specific `llm.md` files that cou
7.
▲
by
pacjam
9mo ago
Ah gotcha! In that case, I think Terminal-Bench is currently the best proxy for "how good is this harness+agent combo at coding (quantitatively)" question. I think it used to be SWE-Bench, but I think T-Bench is a better proxy for
8.
▲
by
pacjam
9mo ago
Beads looks cool! I haven't tried it, but as far as I can tell, it's more of a "linear for agents" (memory as a tool), as opposed to baking long-term memory into the harness itself. In many ways, CLAUDE.md is a weak form
9.
▲
by
pacjam
9mo ago
Not sure why Cursor CLI isn't on the leaderboard... I'm guessing it's because Cursor is focused primarily on their IDE agent, not their CLI agent, and Terminal-Bench is an eval/benchmark for CLI agents exclusively. If yo
10.
▲
by
pacjam
9mo ago
> Does somebody have a clear case on why this is something that we should want For coding agents, I think it's clear that nobody wants to repeat the same thing over an over again. If a coding agent makes a mistake once (like `git ad
11.
▲
by
pacjam
9mo ago
IMO context poisoning is only fatal when you can't see what's going on (eg black box memory systems like ChatGPT memory). The memory system used in the OP is fully white box - you can see every raw LLM request (and see exactly how
12.
▲
by
pacjam
9mo ago
I think it cuts both ways - for example I've definitely had the experience where when typing into ChatGPT I know ahead of time that whatever "memory" they're storing and injecting is likely going to degrade my answer, so
13.
▲
by
pacjam
9mo ago
One cool option is having Void-2 run inside the Letta Code harness (in headless mode) on a sandbox to let is have free access over a computer, just to see what it will do while also connected to bluesky
14.
▲
by
pacjam
9mo ago
I think Cameron (Void's handler) has some experience wiring up production Void to his computer via Letta Code
15.
▲
by
pacjam
9mo ago
Thanks for sharing!! (Charles here from Letta) The original MemGPT (the starting point for Letta) was actually an agent CLI as well, so it's fun to see everything come full circle. If you're a Claude Code user (I assume much of HN
16.
▲
by
pacjam
9mo ago
MemGPT was also first a CLI (and Discord bot), truly returning to our CLI roots: https://news.ycombinator.com/item?id=37901902
17.
▲
Letta Code: a memory-first coding agent
(github.com)
6 points
by
pacjam
9mo ago
|
3 comments
18.
▲
How to build the #1 open source terminal-use agent
(letta.com)
2 points
by
pacjam
1y ago
|
0 comments
19.
▲
by
pacjam
1y ago
I'm talking about the Letta part - unless I'm missing something, the RunAgent framework has to communicate with the Letta server over the Letta API (I'm saying that part can be done w/ Python SDKs, TS SDKs, REST APIs, an
20.
▲
by
pacjam
1y ago
This is pretty sweet. The Letta SDKs are actually auto-generated off of the REST API spec, which means that adding an (official) SDK for another language is just a matter of having enough demand to justify the spend to generate it. I did se
21.
▲
Context Engineering for the LLM OS: User vs. Kernel Context
(letta.com)
2 points
by
pacjam
1y ago
|
3 comments
22.
▲
Show HN: Create stateful agents in the cloud in a single API call
(docs.letta.com)
2 points
by
pacjam
1y ago
|
0 comments
23.
▲
by
pacjam
1y ago
check out Letta - the OSS codebase ( https://github.com/letta-ai/letta ) is basically focused on solving the memory/context problem in a generalized way (via "agentic context management"). if you're m
24.
▲
by
pacjam
1y ago
If you're interested in the full schema you can look at the Pydantic models here: https://github.com/letta-ai/letta/blob/main/letta/serialize_... Agent File is intended to support "one thr
25.
▲
by
pacjam
1y ago
Totally agree - a well-defined REST API "standard" for tool listing and tool execution would have been much better. Could extend as needed to websockets for persistent connections / streaming data.
26.
▲
by
pacjam
2y ago
In Letta that's referring to an LLM agent that has persistent memory (eg keep running the agent far beyond its context window limit, but maintain some persistent state to avoid derailment / enable indefinite use / learning ov
27.
▲
by
pacjam
2y ago
indeed - hello there
28.
▲
by
pacjam
2y ago
I'm also not really sure what's going on with the hype wave atm (people like having things to hype?) since MCP has also been around for a bit, seems like a bit of a meme. IMO, the main value (as an agent / AI developer) that
29.
▲
by
pacjam
2y ago
We're working on it, I'm hoping we can get an integration in sometime next week! If you want to track progress on it would recommend joining our Discord. To clarify - by "it", I mean making Letta agents an MCP client, so
30.
▲
by
pacjam
2y ago
> "voice interactive LLM with memory" Our team has been working really hard on a low-latency voice integration that enables (open source) "advanced voice mode", but with long-term memory! If you're interested def
More ›