Parallel Work & Task Progress

TheGitAI can move several safe parts of a task forward without hiding what it is doing. Parallel tool execution shortens research rounds, the task list keeps the larger job legible, and the busy composer lets you queue what should happen next.

Parallel tool calls

When the model requests several independent read-only operations in one round, TheGitAI can execute up to six of them concurrently. Parallel-safe work includes:

• Reading source files and supported documents.
• Searching or listing files and directories.
• Exact and natural-language code search.
• Symbol, hover, and signature lookups.
• Public web searches and page fetches.

Results are recorded in the original call order even if a later call finishes first. Duplicate web requests in the same turn are deduplicated, and concurrent searches share the same cold repository-index build.

Operations that mutate state remain serial. File edits, shell commands, diagnostics, background-job control, undo, and checkpoint restore form a barrier between parallel groups. This keeps approval prompts and repository changes predictable.

Visible task progress

For a multi-step request, the agent can publish a session-local task list. Each item is one of:

• Pending — not started yet.
• In progress — the current active step.
• Completed — finished.

Only one item is active at a time. The current list is replayed to the agent as the turn continues, which helps it reconcile progress instead of abandoning an old plan after context has been compacted. Updates appear in the live working area, and the final readable snapshot remains in the transcript.

The list belongs to the prompt that created it. A new request starts a new task, and /new starts a separate conversation with a fresh active list while the previous session remains saved.

Queue your next message

The composer stays available while the agent is busy. Type a follow-up and press Enter to queue it. TheGitAI holds one queued message and submits it automatically after the current turn finishes.

While a message is queued:

• Press ↑ with an empty composer to recall it for editing.
• Press Enter again to replace or re-queue the edited message.
• Press Esc to cancel only the queued message while the current turn keeps running.

If you cancel the active turn, the queued message is recalled instead of being submitted unexpectedly. Queued messages can include pasted text and image attachments.

Combine all three

A request such as this uses the features together:

Trace the checkout failure, fix it, run the focused tests, then start the app
and verify the route still works.

The agent can map the work into visible steps, inspect independent files in parallel, and launch the app as a background job. While it works, you can queue “review the final diff for unrelated changes” as the next prompt.