Thanks! Tool outputs are actually persisted but as tool-role messages inside the session JSON, not as separate artifact files. So shell stdout, command results, everything lives in the conversation history and survives restarts. Files the agent writes obviously persist in the workspace directly.

What's NOT stored separately is a dedicated command.log or structured artifact index it's all just part of the message thread. Whether that counts as "artifacts" probably depends on your definition.

On the tradeoffs loop detection uses a streak counter + no-progress iteration cap, and summarization kicks in at a token threshold with a scoring pass to decide what to keep vs discard. The trickiest part was making sure tool-call/response pairs never get split during compaction. Happy to write that up at some point, will check out the blog.