Skip to content

Task Execution

A healthy AlphaBase task should render in this sequence:

  1. user prompt accepted
  2. running/streaming state
  3. tool activity and intermediate updates
  4. file/tool outputs
  5. 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

Continuing a Conversation

Describe the current result you want and identify the relevant files. When returning to earlier work, name the task or file explicitly. Review the selected project and model before requesting changes.

Reviewing the Result

Check the actual changed files or artifact preview, the reported validation, and any remaining limitations. A plan describes intended work; inspect the finished output before treating a build request as complete.

When a Task Stops

Inspect Activity and the displayed task status. Review any error, partial files, pending questions, or approvals before continuing or retrying. Provider limits, permissions, and connectivity can prevent completion. A retry alone does not confirm that a usable output exists.

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
  • a task repeatedly re-planning without ever writing output; report this with the task’s terminal status and runtime diagnostics

Use Troubleshooting for investigation flow, and Launch Gates for how this behavior is tested before a release.

Workflows and follow-up work

Use AlphaBase Workflows for persistent multi-stage or scheduled work where supported. Review the objective, project, model or strategy, permission profile, and schedule before starting. On desktop, inspect Activity, Tasks, Output, and Usage, and respond to pending questions or approvals.

Where Continue workflow is available, send an instruction to the existing workflow. Completed, failed, and started review runs can accept follow-up work with their retained history and files. Check status and partial output before retrying; continuation, retry, review, and cancellation have different outcomes.

A workflow captures its permission profile. Changing the default does not retroactively change an already-running workflow. A plan, progress row, or successful tool call alone does not establish completion.

Preview and export on desktop

Open an artifact preview and choose Preview options from the three dots at the end of its toolbar. Depending on the content and host, options include Open with a detected browser, Open source in editor, revealing the local file, copying its path, downloading it, and Export HTML with assets.

For unsaved content, distinguish opening the current preview from Save and open, which persists source first. External-editor actions use the saved local file. HTML export includes captured preview assets; it does not deploy an entire application. If external actions report unavailable native support after an update, restart AlphaBase.

Brief conversational replies may finish without tool calls or an expandable “Worked for” row. Voice-accepted tasks use the normal task runtime; ending audio does not automatically stop accepted work.