Skip to content

feat: add idle app status #18415

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat: add idle app status #18415

wants to merge 2 commits into from

Conversation

code-asher
Copy link
Member

@code-asher code-asher commented Jun 17, 2025

"Idle" is more accurate than "complete" since:

  1. AgentAPI only knows if the screen is active; it has no way of knowing if the task is complete.
  2. The LLM might be done with its current prompt, but that does not mean the task is complete either (it likely needs refinement).

The "complete" state will be reserved for future definition.

Additionally, in the case where the screen goes idle but the LLM never reported a status update, we can get an idle icon without a message, and it looks kinda janky in the UI so if there is no message I display the state text.

Closes coder/internal#699

@code-asher code-asher changed the title feat: add idle AI agent status feat: add idle app status Jun 17, 2025
"Idle" is more accurate than "complete" since:

1. AgentAPI only knows if the screen is active; it has no way of knowing
   if the task is complete.
2. The LLM might be done with its current prompt, but that does not mean
   the task is complete either (it likely needs refinement).

The "complete" state will be reserved for future definition.
@code-asher code-asher force-pushed the asher/idle-agent-status branch from 4b4786a to c649ea1 Compare June 17, 2025 20:15
The status row looks janky with just the icon.  We can get into a "no
message" state if the LLM never reported a status update.
@code-asher code-asher force-pushed the asher/idle-agent-status branch from c649ea1 to 86cf445 Compare June 17, 2025 20:22
@code-asher code-asher requested a review from hugodutka June 17, 2025 20:40
Copy link
Contributor

@hugodutka hugodutka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, pending the down migration

@@ -0,0 +1 @@
-- It is not possible to delete enum values.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that's true. These steps should revert the enum to its original set of values:

  1. Replace any occurences of new enum values with different values
  2. Rename the enum to something else
  3. Re-create the original enum
  4. Update columns to use the new enum
  5. Drop the renamed enum

Here are the SQL statements you'd use: https://blink.so/chat/Revert-Enum-Value-in-Postgres-5vVDbfY5A7ZOLPxyuqVgsG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update the status in the Tasks page from Complete to Idle for Agents waiting on input
2 participants