Gemini

Following our previous discussion on the RoleEngine Core, it’s time to bridge the gap between a raw CLI “brain” and a real-world communication platform: WeChat. In VisAgent, we don’t believe in heavy, bloated frameworks. Instead, we use a CLI-Native Bridge pattern. This post explores how we connected the “Clawbot” (our WeChat interface) to a hand-rolled Gemini CLI kernel. The Request Flow: From Chat to CLI The architecture is a chain of specialized tools, each doing one thing well. Here’s how a message travels from your phone to the AI: ...

[!TIP] Objective: Build an Agent engine with state management and isolation by wrapping a CLI (e.g., gemini CLI) without framework reliance. 1. Why CLI Over Frameworks? VISAGENT’s philosophy is CLI-Native. Directly wrapping a CLI (like gemini CLI) offers superior control and transparency: Atomicity: Each call is a single inference step. State Transparency: Session resume/suspension is strictly controlled by paths and the Resume flag. Isolation: Permission sandboxing is achieved through native OS tools. 2. Core Wrapper: RoleEngineBase Execution is triggered via subprocess. To prevent Shell parameter overflow from long Prompts, we use stdin for transmission: ...