fix(code-interpreter): use backend timestamp in JS OutputMessage

[lemonzoey]

Summary

The JS Code Interpreter's parseOutput set OutputMessage.timestamp to new Date().getTime() * 1000 — the client-side clock in microseconds — ignoring the timestamp field the kernel sends with every stdout/stderr message.

This diverged from Python (which uses the backend data["timestamp"] directly) and from the documented contract (OutputMessage.timestamp is described as "Unix epoch in nanoseconds"). The JS value was from the wrong clock and the wrong unit.

Fix: read msg.timestamp in the stdout and stderr branches of parseOutput, matching the Python reference implementation. JS-only — Python is already correct.

Closes #1969.

Why this is a real bug (not a pseudo-gap)

• Python reads data["timestamp"] with no fallback, so the kernel always sends timestamp; JS reads msg.text from the same message but drops msg.timestamp.
• Reproduces with no sandbox/API key: feeding parseOutput a stdout message with timestamp: 1234567890 yields ~1791599674953000 (Date.now()*1000), not 1234567890.

Verification

cd packages/code-interpreter-js
pnpm vitest run tests/messaging.test.ts   # 4 passed (2 existing + 2 new)
pnpm run lint      # no new warnings
pnpm run typecheck # passes

New tests assert OutputMessage.timestamp equals the backend msg.timestamp for both stdout and stderr (construct an Execution, feed parseOutput a JSON line with a fixed timestamp, assert the captured message carries it through).

Usage example

import { Sandbox } from '@e2b/code-interpreter'

const sandbox = await Sandbox.create()

await sandbox.runCode('print("hello")', {
  onStdout: (msg) => {
    // Before: msg.timestamp was Date.now()*1000 (client clock, microseconds)
    // After:  msg.timestamp is the kernel's nanosecond timestamp, matching Python
    console.log(msg.line, msg.timestamp)
  },
})

Changeset

@e2b/code-interpreter patch — OutputMessage.timestamp now reflects the backend timestamp instead of the client clock.

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: zhouyi7.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[changeset-bot]

🦋 Changeset detected

Latest commit: 3b31425

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@e2b/code-interpreter	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-10T03:09:33.618631Z	8cd9153	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have @lemonzoey on file. You can sign our CLA at https://e2b.dev/docs/cla . Once you've signed, post a comment here that says '@cla-bot check'

[devin-ai-integration]

🔍 Devin Review: 1 flag

Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

[lemonzoey]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[mishushakov]

the timestamp should be a Date, not str