Give Genny the terminal and ask her to investigate an open-source project. She downloads the code and returns an explanation of its architecture, strengths, and tradeoffs.
The terminal is part of the shared workspace, not a separate session you have to translate into chat. You can follow the work and use the analysis to decide what deserves a closer look.
Read transcript
Genny, can you go ahead and take over my terminal here? I just let you drive and go ahead and find and download the DeepSeek harness as a subdirectory of code. Give me an analysis of it and let me know what it does well. What's interesting? Downloaded the official DeepSeek harness to users shared lantern house slash code slash deep seek dash harness. It's a full agent platform with web, headless, SDK, and ACP modes, not merely a DeepSeek API wrapper. Its strongest ideas are the genuinely replaceable plugin architecture, replayable event source sessions, carefully ordered parallel tool execution, layered approval and sandbox policies, and built-in support for MCP, E2B, workflows, goals, sub-agents, Codex, and Claude code. The engineering is unusually rigorous and heavily tested, but it's still version 0.1.3-alpha.1. Explicitly unaudited, extremely complex, and not yet something I'd trust as a production security boundary.