Geulbat

The description states Geulbat is an AI workspace that:

• Enables programmatic tool calling (PTC) via JavaScript/TypeScript execution in isolated Docker environments
• Provides live, interactive visualization capabilities within conversations
• Offers long-lived context with append-only transcripts and compaction
• Supports recursive parallel subagents
• Includes open CLI execution for command-line programs
• Combines typed tools, open CLI access, and programmatic tool composition

All these features are described as implemented in a TypeScript monorepo architecture with daemon, React web shell, and shared protocol package.

The description states the project was inspired by the limitation of current AI development tools that invoke one tool at a time, leading to high latency and token usage. The authors claim they wanted to explore:

• An AI that could write programs to orchestrate multiple tools
• Presentation of results as live, interactive visuals within conversations
• A long-lived workspace rather than disposable chat windows

This represents an evolution from simple tool invocation toward programmatic composition and persistent workspaces.

Not evidenced. The description does not identify specific target customers or ideal customer profiles (ICP). No information is provided about who would use this system or what their needs are beyond general AI development tool usage.

Not evidenced. The description provides no information about pricing, business model, monetization strategy, or revenue streams. No commercial aspects of the project are described.

The description states Geulbat is implemented as a strict TypeScript monorepo with:

• Daemon owning model communication, tool execution, PTC Docker runtimes, subagent state, transcript persistence
• React-based web shell for rendering conversations and visualizations
• Shared protocol package for event/data contracts between daemon and client
• PTC code runs in isolated Docker environment with admitted callback boundaries
• Visualization system reuses sandboxed artifact runtime
• Execution surface combines typed tools, open CLI, and programmatic tool calling

Not evidenced. The description is entirely self-reported and unverified, containing no information about revenue, customers, adoption, usage metrics, or product maturity beyond the prototype stage.

Not evidenced. The description does not mention competitors, market positioning, or competitive landscape. No comparison to existing AI development tools or platforms is provided.

• Implementation risk: Described as a prototype with no evidence of production use or traction
• Security boundaries: The description notes challenges in making programmable execution powerful without unrestricted host access
• Governance complexity: Recursive agents require careful governance, but the authors acknowledge they don't want to claim arbitrary recursion is fully governed
• Technical debt: Multiple complex systems (PTC, visualization, long-lived context) are described as implemented but with known challenges
• Unverified claims: All information is self-reported without independent verification

1. What specific tools or use cases does PTC actually support in practice?
2. How many actual implementations of the system exist beyond the prototype?
3. What are the concrete security boundaries and how are they enforced?
4. Has the system been tested with real users or developers?
5. What is the current state of the recursive agent governance implementation?
6. How does the system handle edge cases in long-running executions?
7. What specific development environments or repositories has it been tested with?
8. Are there any known limitations or constraints that prevent production deployment?