Task Execution
What healthy prompt execution looks like across surfaces.
A healthy AlphaBase task should render in this sequence:
- user prompt accepted
- running/streaming state
- tool activity and intermediate updates
- file/tool outputs
- final completion response
Tool Activity Expectations
Good tool timelines are action-oriented and grouped, for example:
- searched workspace
- explored files
- ran shell checks
- applied edits
Output Integrity Checks
If execution is healthy:
- generated code appears in write/edit artifact blocks
- file paths are concrete and openable
- completion message summarizes what changed
Regression Signals
Watch for:
- intermediate response text leaking into final response area
- abrupt termination before terminal completion message
- duplicate thought/response emissions
- disappearing or flickering streamed content
Use Troubleshooting for investigation flow.