This looks nice, I wonder if updating styles for o...
# proj-agent-canvas
f
This looks nice, I wonder if updating styles for our current events / observations to something similar will make the interface look better? WDYT @breezy-kilobyte-39430 @elegant-branch-54423? For example, given an example event like:
Copy code
{
  "id": 7,
  "timestamp": "2025-11-11T12:59:06.243737",
  "source": "agent",
  "message": "Added workspace context",
  "cause": 5,
  "observation": "recall",
  "content": "Added workspace context",
  "extras": {
    "recall_type": "workspace_context",
    "repo_name": "",
    "repo_directory": "",
    "repo_branch": "",
    "repo_instructions": "",
    "runtime_hosts": {
      "<https://work-1-legaopitfjacxmkd.prod-runtime.all-hands.dev>": 12000,
      "<https://work-2-legaopitfjacxmkd.prod-runtime.all-hands.dev>": 12001
    },
    "additional_agent_instructions": "",
    "date": "2025-11-11",
    "custom_secrets_descriptions": {},
    "conversation_instructions": "",
    "working_dir": "/workspace/project",
    "microagent_knowledge": []
  }
}
If we can change the existing event style (second screenshot) to something more presentable like the first?
e
The blue border is applied to events related to Plan mode Non-blue borders are events related to Build mode (the default mode)
f
I was more referring to the card style compared to the empty / styleless accordion we have for events
e
Oh gotcha - yeah would like Paul's take on this. I wonder if that makes things cleaner or more cluttered. Not sure.
f
I think in general this would be a great improvement to UI if done right. I have some example screenshots of how a GitHub MCP event might look in the UI in the thread below (https://openhands-ai.slack.com/archives/C06QT0AGY4W/p1762867038593739?thread_ts=1762866806.199259&amp;cid=C06QT0AGY4W)
b
@freezing-spoon-14104 I'm generally in agreement, I wonder if it works in all cases? Meaning if we want to keep some responses simple text rather than be in a box.
f
Probably not all, but IMO we are underutilizing a lot of the data we get from some of these events that could well enough be converted to their own compact components. I can try to gather a better list of this to see what we can turn into more presentable components