Feature Updates
- Chat-first workspaces now open the first project conversation directly when opening Teable or a space, without showing an intermediate page or repeatedly prompting users to update the layout.
- Query dependencies can now be retrieved through Teable CLI, MCP, and generated clients, with filtering by table and field and enforcement of existing access permissions.
- Added field-level impact analysis to identify apps and queries affected by schema changes, respecting app visibility permissions.
- App Builder chats started from Base conversations now support OneDrive authorization without clearing or restarting the chat. Authorization prompts remain available throughout the conversation.
Bug Fixes & Improvements
- Improved the chat-first layout on screens 640px wide or narrower. The mobile navigation drawer now closes after navigation. Conversations fill the chat page, while resource and app pages provide an on-demand bottom chat drawer to keep app previews visible at all times.
- Fixed an issue where “Open in project” repeatedly opened the mobile chat drawer and changed the user’s desktop docking preference.
- Teable CLI 0.6.47 reduces startup memory usage and improves the reliability of help, validation, and individual commands.
- When CLI read results or table output are too large, output is now truncated or the request is rejected with a clear error message suggesting pagination or fewer fields, rather than terminating unexpectedly. Node.js heaps smaller than 64 MB are not supported.
- Improved the accuracy of cell values returned by the CLI.
- Invalid or expired OAuth refresh tokens now return a clear 401 response instead of a server error.
- Conditional lookup and Rollup filter conditions are now validated when fields are created or updated. Unsupported operators and incomplete values are rejected with specific validation errors, rather than causing generic calculation failures later.
- Improved the timeliness and reliability of query dependencies when apps are published concurrently.
- Model selections are now saved per chat and applied consistently to directly sent, queued, and steering messages, including in App Builder and routine conversations. The selector shows the model actually in use, including model changes during a response. If the selected model is unavailable, the administrator-configured default model is used instead.
- Fixed an issue on iPad where reopening a chat through a deep link could incorrectly display “New chat” and the default model.
- AI context tags now remain stable when selected records or cells refresh. Detail cards prioritize readable table names, record titles, and selected field values over internal identifiers.
- Improved platform security and reliability.