Agent loop
shippingThe core ReAct loop — prompt, reason, tool, result, next step. Streamed, interruptible, and fully logged.
Every feature carries a status —
shipping is in the binary today,experimental works but rough,planned not yet shipped.The core ReAct loop — prompt, reason, tool, result, next step. Streamed, interruptible, and fully logged.
Targeted patches, multi-file edits, new files. Every change lands in the transcript as a diff summary.
Run shell commands through your $SHELL. Output is captured, streamed back, and written to the session log.
Curated catalog. provider/model IDs. adapter: openai for any compatible endpoint. Credentials stay out of project config. Catalog →
Commands run in your shell on your machine — fastest path, uses the tools you already have installed.
Ephemeral containers for risky work. Workspace mounted in, container torn down with the session. Sandbox polish is experimental.
Offload to remote workers (E2B, Modal, Daytona, custom SSH or container). Tracked by the runtime boundary plan. Runtimes →
Append-only JSONL logs under ~/.glue/sessions/. Resumable across runs. Replay UI is planned. How it works →
Fetch, search, extract, PDF OCR, browser automation. The CDP backend is experimental. Web →
Delegate a sub-task to a separate agent with its own context and tool set. Useful for parallel search or independent investigations.
Discoverable, runnable skill definitions the agent can invoke as first-class tools.
Talk to any MCP server as a tool source. Editor integration, external search providers, custom tool backends.