docs: add FLUJO client configuration - #2690
Draft
flujo-app wants to merge 1 commit into
Draft
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
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
1 participant
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.
Adds FLUJO to the client configuration guide in alphabetical order. The instructions cover an existing Chrome instance, separate executable/arguments in FLUJO's Standard IO form, and verification with the built-in tool tester.
Validated in an isolated Debian 12 cloud environment:
The full-repository npm run format did not finish in this 2GB VM: ESLint exceeded the default Node heap, and a 1536MB heap retry was killed. The changed Markdown file passes its scoped formatting check.
The FLUJO data directory and browser profiles were fresh; the installed FLUJO/Node runtime was reused. This verifies the existing-browser connection route, not automatic Chrome launch, performance tracing, or model chat.
Genuine screenshots and test details.
Prepared and tested with Codex assistance for the FLUJO project. Submitted as a draft; the Google CLA has not been signed.