Since prompt caching won't work across different models, how is this approach better than dropping a PR for the other harnesses to review?

▲

dchu17 3 hours ago | parent [-]

Sorry, I may be misunderstanding the question.

The way this works is that it stores workstreams and session state in a local SQLite DB, and links each ctx session to the exact local Claude Code and/or Codex raw session log it came from (also stored locally).

What do you mean by prompt caching?

▲

Wowfunhappy 3 hours ago | parent [-]

Prompt caching is done on the provider side. If you send two requests to a provider in short succession and the beginning of your second request is the same as your first (for example, because your second request is the continuation of an ongoing chat), the repeated tokens are much less expensive the second time.

Obviously, your tool does not provide this. But I think GP is undervaluing the UX advantages of having your conversation history.

	▲	buremba 2 hours ago \| parent [-]
		Yes that's it. I actually just ask codex/claude code to look up the session id when I want to resume sessions cross harness, it's just jsonl files locally so it can access the full conversation history when needed.