How commontoolsinc/labs works
Project type and purpose
• This is a monorepo containing a full-stack application called “Common Labs.”
• Frontend: “Jumble” – a React/TypeScript SPA built with Vite.
• Backend: “Toolshed” – a Deno-based HTTP API.
• Alongside are dozens of shared libraries (memory, llm, runner, builder, charm, identity, iframe-sandbox, etc.), CLI tools, and background services.
File structure
• Top-level folders handle global config, CI/CD (.github/workflows), scripts, tasks, and monorepo tooling (deno.json, dockerignore).
• packages/ contains discrete workspaces:
– toolshed: Deno server implementing routes for AI, storage, auth, health, integrations.
– jumble: React SPA with components, contexts, hooks, styles.
– memory, llm, runner, builder, charm, identity, iframe-sandbox: core libraries encapsulating data storage, LLM prompt logic, recipe execution, code generation, authentication, sandboxed iframes.
– cli, seeder, background-charm-service: developer-facing CLIs and background worker processes.
– ui, html, deno-vite-plugin, deno-web-test, utils: ancillary libraries for rendering, bundling, testing, and utility functions.
README for additional insights
• README emphasizes a two-tier architecture: frontend at http://localhost:5173, backend at http://localhost:8000.
• Toolshed README details API startup; jumble README covers SPA development and environment override for cloud backend.