You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/basic/ai/ai-chat.mdx
+7-11Lines changed: 7 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -141,17 +141,17 @@ Cuppy, please read the memory for Base ID bsexxxxxxxxxxxx and save the relevant
141
141
142
142
### Handle Long Tasks
143
143
144
-
AI Chat is designed for foreground, interactive work in the visible conversation. Do not rely on background tasks or silent execution inside the chat for long-running work.
144
+
AI Chat can keep a single conversation environment available for about 24 hours, which is enough for most data analysis, file processing, and app-building tasks. Keep long-running work in the current conversation so you can follow its progress and provide input when needed.
145
145
146
146
<Steps>
147
-
<Steptitle="Check whether the task is still running in the foreground">
148
-
If the interface still shows `Thinking`, or progress updates are still being returned, foreground execution is still running. If the task shows `Completed`, the current foreground execution has ended.
147
+
<Steptitle="Follow progress in the current conversation">
148
+
If the interface shows `Thinking` or continues to return progress updates, the task is still running. If it shows `Completed`, the current run has finished.
149
149
</Step>
150
-
<Steptitle="Do not treat temporary content as persistent storage">
151
-
After the AI runtime is restarted, only memory files can be read. Background tasks, temporary files, and intermediate results are not preserved.
150
+
<Steptitle="Save results at useful checkpoints">
151
+
For work with multiple stages, ask Cuppy to write results back to Teable, export them, or generate a downloadable file at key checkpoints. Saved work remains available even if the conversation environment is released later.
152
152
</Step>
153
-
<Steptitle="Split work into batches and agree on visible outputs">
154
-
In the current environment, the conversation environment has idle cleanup and maximum lifetime limits: after foreground execution ends, an idle environment is released after about 30 minutes, and a single conversation environment has an approximate maximum lifetime of 5 hours. Split long-running tasks into smaller batches. Before starting each batch, agree with AI Chat on the visible output for that batch, such as writing results back to Teable, exporting results, or generating a downloadable file. After confirming that output is complete, continue with the next batch.
153
+
<Steptitle="Know when the environment is released">
154
+
A single conversation environment has an approximate maximum lifetime of 24 hours. After foreground execution ends, an idle environment is released after about 30 minutes. Temporary files and unsaved intermediate results are not preserved if the environment restarts.
155
155
</Step>
156
156
</Steps>
157
157
@@ -166,10 +166,6 @@ For long-running or repeatable work, use the feature that matches the workflow:
166
166
</Card>
167
167
</CardGroup>
168
168
169
-
<Note>
170
-
Teable is improving the experience and runtime capability for long-running tasks. At this stage, plan long-running tasks around the limits above.
171
-
</Note>
172
-
173
169
## Prompting Tips
174
170
175
171
-**State the goal first**: In the first message, describe what to do, the relevant conditions, and the expected output. For example, analyze weekly sales trends over the past 3 months, grouped by region, and return a trend table with a short conclusion.
0 commit comments