christinetyip

4 ms·

1.
by christinetyip 3mo ago
Excited to try out its capability, especially audio and video. It's nice that it has a long context window, but in practice, I find I always have to clear context btw 150k-400k context even if the context window is 1M on paper.
2.
by christinetyip 3mo ago
Have you by any chance also tried GPT-5.6 Sol? Curious how that compares.
3.
by christinetyip 3mo ago
Shameless plug: a friend and I started Superlinear today, a short-form podcast about emerging practices for building with coding agents. Ep 1 is a 13-minute conversation about spatial feedback loops. We talk about how this pattern is showin
4.
Four Practices for Building Better with AI Agents(twitter.com)
4 points by christinetyip 4mo ago|1 comments
5.
by christinetyip 6mo ago
It's been a bit disruptive to my workflows tbh. What alternatives are people using? Sell them to me please
6.
by christinetyip 6mo ago
The github repo isn't public.
7.
by christinetyip 6mo ago
Not leaking codenames is one thing, but explicitly removing signals that something is AI-generated feels like a pretty meaningful shift.
8.
Show HN: Multi-agent autoresearch for ANE inference beats Apple's CoreML by 6×(ensue-network.ai)
6 points by christinetyip 6mo ago|0 comments
9.
by christinetyip 8mo ago
Cool, what’s a good first task to try this on where it’s likely to beat a single agent?
10.
by christinetyip 9mo ago
That makes sense, and I agree that for a single agent using skills well, Claude’s native context handling has gotten much better. This wasn't mentioned in the first post, but the use case we’re focused on isn’t really “Claude forgettin
11.
by christinetyip 9mo ago
I mostly agree with this, if the goal were “better persistent memory inside Claude Code,” that wouldn’t be very interesting. For a single agent and a single tool, keeping project specs and decisions in markdown and explicitly pointing the m
12.
by christinetyip 9mo ago
You’re right that reading the same markdown file is trivial, that’s not the hard part. Where it stopped being trivial for us was once multiple agents were working at the same time. For example, one agent is deciding on an architecture while
13.
by christinetyip 9mo ago
A lot of the discussion here is about memory inside a single tool, which makes sense. I’m curious how people think about portability: e.g. letting Claude Code retrieve context that was created while using Codex, Manus, or Cursor, or sharing
14.
by christinetyip 9mo ago
Yep, parsing logs + async RAG works fine if you’re staying inside a single tool. The issue we ran into when building agent systems was portability. Once you want multiple agents or models to share the same evolving context, each tool recons
15.
by christinetyip 9mo ago
This is fair, many memory projects out there boil down to better summaries or prompt glue without any clear way to measure impact. One thing I’d clarify about what we’re building is that it’s not meant to be “the best memory for a single ag