Bug Report: Deployment blocked by lib/teable.ts template error & Claude Opus 4.6 credit loop

Teable Discussions
1

Hello Teable community and team!

Introduction & Use Case I recently migrated a complex multi-agent pipeline into Teable, building an ERP system for stock media creators. It uses 5 custom prompt generators, integrates external APIs (Gemini, Straico, Airbrush), and utilizes Kanban/Gallery views. The database architecture is excellent and handles the relational complexity perfectly. However, I encountered a critical issue during the final deployment stage.

Bug Report: Deployment Failure All attempts to publish the app via the built-in deployment mechanism fail during the Vercel build process.

  • Root Cause: The system-generated template file lib/teable.ts contains the line: import "../temp.ts".

  • Technical Issue: Modern Next.js bundlers (Webpack/Turbopack) cannot resolve modules with explicit .ts extensions.

  • The Blocker: The AI Builder does not have permission to edit this system file to fix the syntax.

The Consequence: AI Credit Loop Because the AI Builder cannot access the root cause, asking it to fix the deployment error forces it into an infinite loop. The underlying model (Claude Opus 4.6) wastes massive computational power re-analyzing the entire codebase and attempting irrelevant fixes (like downgrading React or Next.js versions), only to fail the build again. I lost over 1,000 credits purely on these futile automated attempts to bypass a system-level bug.

Ideas / Feature Requests

  1. Template Fix: Please remove the .ts extension in the lib/teable.ts template so apps can compile correctly.

  2. Credit Reimbursement: I request a refund of the credits wasted by the AI Builder’s deployment loops.

  3. Flexible Billing: Currently, purchasing a credit top-up requires an active monthly ($6) or annual ($60) subscription. Allowing one-off credit purchases would prevent development from halting entirely when limits are reached.

Thank you for your hard work on the platform. Looking forward to deploying my app once this is resolved!

2

Sorry for the trouble, and thanks for flagging this. Could you please share the app link with us? We’ll start looking into it once we have it.

3

What exact link can I send you if the app is not published? I found 3 real errors and was able to publish the app manually after downloading an archive with its code beforehand. These were not the errors the platform agent pointed out. And they were very simple syntax errors, which took only a couple of minutes to fix.

4

https://edustyle-project.vercel.app/ This is the application that I published after fixing the actual errors in the code through manual project upload to Vercel.

5

Hi Oleksandr,

Glad you got it deployed! Nice to see you downloaded the archive and tracked down the actual errors yourself.

That said, AI can make mistakes — for the most part the AI Builder handles things well, but it’s not always going to get it right, and manual judgment is still part of the process. The credits used during those attempts reflect real AI work, even when the direction wasn’t right.

We’re continuously working on improving the agent to make its output more stable and consistent — that’s very much our focus going forward.

Thanks for documenting everything so thoroughly.