Browser use commands not visualised in jsonl mode

Open
#17 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Reproduce the issue with the provided JSONL entry containing a browser tool call, then compare its rendering with the same data opened as JSON in the top window. Trace the JSONL visualization path and make browser-use commands appear consistently; done when the example entry is visualized in JSONL mode.

Written by the indexing model from the issue text.

Description

I have a jsonl with browser use such as:

{"id":22,"timestamp":"2025-05-03T13:00:32.154537","source":"agent","message":"Visited http://localhost:8000/mean_time_series.png","cause":21,"observation":"browse","tool_call_metadata":{"function_name":"browser","tool_call_id":"toolu_09","model_response":{"id":"gen-1746270027-xJ5HpJs56Ogxa5E5NQF6","created":1746270027,"model":"anthropic/claude-3.7-sonnet","object":"chat.completion","system_fingerprint":null,"choices":[{"finish_reason":"stop","index":0,"message":{"content":"Now let's view the plots using the browser.","role":"assistant","tool_calls":[{"index":1,"function":{"arguments":"{\"code\": \"goto(\\\"http://localhost:8000/mean_time_series.png\\\")\"}","name":"browser"},"id":"toolu_09","type":"function"}]

but these are not visualised

However if you open it as json using the top window it works

Dominant language
TypeScript
Stars
55
Forks
16
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenHands/trajectory-visualizer

All issues in OpenHands/trajectory-visualizer

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.