tpmjs/apps/playground
Ajax Davis 4094c661be fix: properly pass env vars to cached tools and add extensive logging
PROBLEM:
- Tool wrappers cached env vars in closure, so cached tools used stale env
- Client env vars weren't reaching Railway executor even when provided
- No visibility into env var flow through the system

SOLUTION:
1. Store env vars per conversation in conversationEnv Map
2. Tool execute functions look up latest env from Map (not closure)
3. Chat API calls setConversationEnv() on each request
4. Added logging at every step

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-04 14:18:32 +10:00
..
src fix: properly pass env vars to cached tools and add extensive logging 2025-12-04 14:18:32 +10:00
.env.local.example feat: implement playground app with AI SDK v6 tool execution 2025-12-04 02:51:02 +10:00
next-env.d.ts fix: use deployed /api/tools endpoint with client-side filtering and streamline git hooks 2025-12-04 13:43:19 +10:00
next.config.ts feat: add dynamic tool loading system with Railway executor 2025-12-04 08:25:53 +10:00
package.json fix: migrate playground to AI SDK v6 beta and resolve TypeScript errors 2025-12-04 13:15:21 +10:00
postcss.config.mjs feat: implement playground app with AI SDK v6 tool execution 2025-12-04 02:51:02 +10:00
tailwind.config.ts feat: implement playground app with AI SDK v6 tool execution 2025-12-04 02:51:02 +10:00
tsconfig.json feat: implement playground app with AI SDK v6 tool execution 2025-12-04 02:51:02 +10:00