Tinderbox Meetup 09AUG26: Tinderbox + Claude: Building a Personal “Web Twin” Summary
| Level | Intermediate |
| Published Date | 8/10/26 |
| Type | Meetup |
| Tags | AI, Claude, IDE, 5CKM, 5Cs of Knowledge Management, Eastgate, Identity Praxis, Inc., Mark Bernstein, Michael Becker, Tinderbox |
| Video Length | 01:43:39 |
| Video URL | https://youtu.be/VIdrGDUCXpo |
| Chat File | TBX Meetup 08AUG26_Chat.txt (6.6 KB) |
| TBX Version | 11.5 |
| Instructor | Michael Becker |
In this Tinderbox Meetup, we explored how Tinderbox and Claude Code can work together as a highly personalized knowledge and development environment. Andreas Grimm demonstrated his “Tinderbox Web Twin”: a locally hosted, browser-based interface built around his Tinderbox data. It lets him search and navigate meetup transcripts and chats, filter and rearrange information, create new visualizations, and use AI to curate material around concepts rather than only known keywords.
What makes the work especially interesting is that Andreas does not consider himself a programmer. He built the system incrementally with Claude by repeatedly asking for the next useful capability: another view, a filter, an export, a different interaction. Over several months, those small steps became a substantial new interface around Tinderbox. The larger lesson was not to copy Andreas’s system, but to use AI as a partner in emergent development: start with a real need, experiment, and let the structure evolve rather than designing everything up front.
Key Learning Outcomes
- Claude can act as a development partner for Tinderbox. A non-programmer can now build meaningful extensions and interfaces without waiting for traditional software development.
- The Web Twin adds another lens on the same knowledge. It does not replace Tinderbox views; it extends how the same underlying information can be searched, filtered, visualized, and manipulated.
- AI makes emergent development practical. Andreas did not begin with a complete specification. The system evolved through repeated small questions, experiments, and refinements.
- Tinderbox can provide structure around fragmented AI work. Claude’s different chats, projects, and modes remain partially siloed; Tinderbox can become a persistent layer for organizing, linking, and visualizing that activity.
- “Ask Claude” is increasingly part of the workflow. Andreas even has Claude create instructional notes and linked maps inside Tinderbox to explain installation and configuration steps.
Consideration
While Andreas’s demonstration is extremely impressive, there remains a significant gap between “look what is possible” and “how do I get started?” His answer is essentially: don’t try to reproduce what I built; start experimenting, ask Claude, and let your own solution emerge. That philosophy makes sense, but it may not provide enough signposting for a beginner.
This exposes a real tension between Andreas’s sincere “just try it” and the audience’s equally legitimate “try what?” Most people are trained to look for instructions, templates, examples, and repeatable steps. Emergent AI-assisted development works differently: someone may arrive at a powerful personal solution through hundreds of small interactions and then struggle to explain how another person should begin.
The session itself illustrated the problem and the opportunity. A simple question about setting up the local web server and a secure environment quickly exposed assumed knowledge about npm, installation, localhost, and configuration, with the practical answer again becoming: ask Claude.
That creates a new learning and documentation challenge. We may increasingly have people with highly capable, personalized AI-built systems who cannot easily reconstruct how they got there, alongside newcomers who do not yet know enough to formulate the right questions.
The community may therefore need something between “copy Andreas” and “just ask Claude”: a lightweight learning scaffold that explains the major components, provides a few safe starting experiments, addresses permissions and security, and shows examples of productive AI interactions.
A useful principle might be:
Start small, understand what you are giving AI access to, solve one problem that matters to you, and let the structure emerge from there.
That preserves Andreas’s core insight while giving newcomers enough of a trailhead to begin.