Definitely open, I just checked letta's codebase before answering this and wrote the full adapter spec: https://t.co/NbFGm9sTWR
pond would ingest the native transcripts, not the trajectory format, as trajectory is lossy compared to the native transcripts. It truncates tool results and drops system messages, and throwing away sessions data is against pond's philosoph 😉
If you would like this adapter to happen faster, just 👍 the issue. Reactions help me decide what to ship next.
Are you open to adding an adaptor for Letta code or their trajectory format? I use letta a lot and usually use codex, pi, Claude, omp and prime as workers. I’ve got them all aggregating into cass but cass can feel brittle and syncing multiple machine sessions to s3 is really appealing.
weird that there's a "make a lot of money" button and nobody's pressing it
(take your SaaS, make it headless, let agents use it, charge per interaction esp for enterprises)
Plannotator 0.27.0 is out.
Code review is not dead yet.
- Calldiffs by @tanishqk is integrated as an optional lens
- Guides support custom instructions
- Tailscale remote reviews - thanks @nikuscs for the POC that kicked this off & @freak4pc for final encouragement
- Customize review panel: turn off viewed, git add, and disable lens for cleaner UI
Pi - BREAKING:
Pi plan mode has moved from `/plannotator` to `/plannotator-plan-mode` to avoid confusion
CI pipeline hardened.
With all the talk around RLM recently, I installed prime agent and asked it to educate me. Together, we built a skill that uses the rlm pattern to lint claims in any statement or document. Along the way, it educated me to help me understand.
@Hello_World@jack@wesbillman@blocks That’s the part that got me. It didn’t just suggest some code. It diagnosed the missing feature, built it, tested it, installed it, used the app, and verified the result with the restored agents themselves.
This felt like a real step change.
6/6
I screwed up two custom agent configs in Buzz, and the app had no way to restore them. Fizz found a clever way through it, fixed both agents without changing their identities, and honestly blew me away.
@Hello_World@jack@wesbillman@blocks
1/
@Hello_World@jack@wesbillman@blocks Both agents came back with their original identities and settings. No new keys, no duplicates, no sketchy database edit.
The final fix was just restoring two configs. Getting there safely required understanding the whole system and using every tool available.
5/