Browser use commands not visualised in jsonl mode
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenHands/trajectory-visualizer
-
demo is not workingOpen
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
dummy issueOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
OpenHands/trajectory-visualizer#24 · 2 comments ·
-
openhands
Difficulty 4/5 3-5 days Newbie friendliness 45/100
OpenHands/trajectory-visualizer#21 · 1 comment · 1 reaction ·
All issues in OpenHands/trajectory-visualizer
Similar issues
-
inference/go type/feature
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
anomalyco/opencode#65148 · 1 comment ·
Maintainers usually reply within 1 day
-
truapi-release
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
paritytech/product-sdk#529 ·
Maintainers usually reply within 1 day
-
Add: Mansudae TVOpenapproved check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
[Perf] Canvas layer composition is quadratic: splitRenderLayers re-copies the node array per nodeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
devlikeapro/waha#2369 ·
Maintainers usually reply within 5 days