AI Activity and the Workspace Panel

How to read the AI run status and review outputs, code, terminal output, and plans

In Jinba App Neo, the AI works inside an isolated session environment for each message, performing file operations, code execution, web search, and more. This page explains how to follow what it is doing.

Run status

The AI’s status is shown in the message area in real time.

Indicator	Meaning
Connecting…	Starting the session
Thinking… / Reasoning…	The AI is working out its answer or plan of action
Running tool	Executing a Connector tool, code, or similar
AI running	Work is in progress (changes to “Done” when finished)

Interrupting a run

While the AI is running, an “Interrupt” button is shown. Click it to stop processing at any time. An interrupted chat records “AI run was interrupted”, and you can send follow-up instructions from there.

The workspace panel

Use the “Workspace” toggle in the chat screen to open a side panel showing what the AI has been working on. You can also switch it to full screen.

Tabs

Tab	Contents
Results	A summary of the run’s results
Files (outputs)	Files the AI created. Select one to open a preview, or use “Download all (ZIP)” to grab everything at once
Code	Code files the AI created or edited
Terminal	Commands the AI ran and their output. Output can be shown or hidden
Plan	The work steps the AI laid out. The current step is highlighted
Preview	Rendered previews of HTML and similar formats
Audit log	A record of what was executed

Browser view (a live view of the AI’s browser operations) is coming soon.

Receiving generated files

When the AI creates files, they are listed in the message as “Generated files”. Click to preview, or use the download button to save. For formats that cannot be previewed, download the file to review it.

When a run takes a long time

If a tool run through a Connector is slow to respond, a hint message is shown. If a jinba-flow integration leaves no run history on the jinba-flow side, check that the MCP URL is reachable from outside (Anthropic’s cloud) — localhost and internal-only hostnames cannot be reached.