docs: add Flue integration guide - #332
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
beran-t
reviewed
Aug 6, 2026
| query: { metadata: { flueInstance: options.id }, state: ['running', 'paused'] }, | ||
| }).nextItems(); | ||
|
|
||
| // connect() resets the timeout to E2B's 5-minute default, so set it again. |
Contributor
There was a problem hiding this comment.
connect should not reset the timeout. It only extends it if timeout is shorter than used value.
Contributor
Author
There was a problem hiding this comment.
Yep, had it backwards. Checked against prod: 20 min left stays 20 min whether or not I pass a timeout, and 1 min left gets bumped to 5. Fixed in 034eb94.
Heads up, persistence.mdx says the timeout resets on connect — that's where I got it from. Left it for a follow-up.
beran-t
approved these changes
Aug 6, 2026
beran-t
added a commit
that referenced
this pull request
Aug 6, 2026
* docs: correct connect timeout behavior in persistence Connecting to a sandbox does not reset its timeout - it only extends the lifetime (new expiry is the later of the current expiry and now + timeout). Verified against e2b-dev/infra (sandbox_connect.go passes allowShorter=false) and both SDKs. Follow-up to #332. * docs: reword timeout section to open with 'When connecting to a sandbox'
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Flue (the agent framework from the Astro team) ships its E2B support as a blueprint —
flue add sandbox e2bprints a Markdown guide that a coding agent applies, leaving the adapter in the user's repo assrc/sandboxes/e2b.ts. There is no@e2b/fluepackage, so the page is written around that shape: scaffold, add the adapter, write a ~25-line agent, run it.Changes
docs/agents/flue.mdx— new page: comparison against Flue's built-inbash()virtual sandbox andlocal(), project setup, the blueprint step, a one-agent/one-sandbox worked example, sandbox reuse across turns keyed on the agent instance id, custom templates, lifecycle ownership, and troubleshootingdocs.json— register the page in the Agents nav group, after Vercel Eveimages/icons/flue.svg— nav icon, traced from Flue's own markVerification
Everything on the page was executed in a throwaway project against live sandboxes (
@flue/runtime2.0.3,@flue/cli2.0.3,e2b2.38.0, Node 22.23.1 and 24.11.0):flue initfile list,flue add sandbox e2b --print, adapter written verbatim,tsc --noEmitcleanbashtool returned real output from the sandbox, which was then visible viaSandbox.list({ query: { metadata: ... } })exec()doesn't catchCommandExitError, so a failing command reaches the model as a bareexit status 1with stderr dropped. The page carries the fix.mint dev: page, nav entry, icon, and internal links all resolveNote:
mint devcrashes on this repo before serving, on a pre-existing generated filename fromopenapi-public.yml(ENAMETOOLONG ... freeze-the-guest-rootfs-...mdx). Unrelated to this PR; the render check ran on a local copy with only thatsummary:shortened.