Skip to content

Add support for locally exported trajectories #2

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

Merged
merged 15 commits into from
Mar 7, 2025
Merged

Conversation

neubig
Copy link
Contributor

@neubig neubig commented Mar 7, 2025

This PR adds support for visualizing trajectories locally exported from OpenHands.

Changes:

  • Add OpenHands trajectory format converter
  • Add upload functionality for local trajectory files
  • Support viewing OpenHands trajectories in timeline view
  • Add back button to return to repository view
Screen.Recording.2025-03-07.at.10.44.56.AM.mov

- Add OpenHands trajectory format converter
- Add upload functionality for local trajectory files
- Support viewing OpenHands trajectories in timeline view
- Add back button to return to repository view
- Add unit tests for OpenHands trajectory converter
- Add unit tests for trajectory upload component
- Update documentation with OpenHands support details
- Add project structure and usage instructions
@neubig neubig self-assigned this Mar 7, 2025
@neubig neubig changed the title Add support for OpenHands trajectories Add support for locally exported trajectories Mar 7, 2025
- Add specific handling for message types in TimelineStep component
- Update openhands-converter to set correct type for messages
- Add test to verify message labeling
- Add markdown rendering for message content
- Fix type issues in TimelineStep and getStepInfo
- Update tests to verify message display
- Update test to match new message display behavior
- Move mockGetStepInfo to __mocks__ directory to avoid Jest treating it as a test file
@neubig neubig marked this pull request as ready for review March 7, 2025 15:45

// Add any tool metadata
if (event.tool_call_metadata) {
entry.metadata = {
Copy link

Choose a reason for hiding this comment

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

Is it worth dumping the rest of the tool call metadata in here as well? There's some other useful info in there (model info, token counts) that might be nice to have available.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@OpenHands please address this comment

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I opened a new issue #4

Copy link

@csmith49 csmith49 left a comment

Choose a reason for hiding this comment

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

This is cool, I've been building jq commands to get at-a-glance trajectory info but this looks so much easier.

@neubig
Copy link
Contributor Author

neubig commented Mar 7, 2025

@OpenHands please address the comment by csmith49 above suggesting that we visualize more information.

@neubig neubig merged commit 1054aef into main Mar 7, 2025
2 checks passed
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.

3 participants