Make sticky notes more useful for documentation inside flows (original) (raw)

Feature Request

To make sticky notes more useful for documentation inside flows:

1. Remove the size constraints so they can be as large as needed
2. Add more colors so more parts of a flow can be easily visually distinguished

Motivation

Executive summary:

As a developer, I would like to be able to document my langflow inside the flow as much as possible. This will enable developers or users to more easily understand complex setups by simply opening the flow, without needing to read additional/external documentation.
Currently, I'm using sticky notes for this.

Use case

I've built a larger multi-agent flow with Langflow, and we've used this to demo to internal stakeholders and are likely to also use this to explain the multi-agent setup to customers.
Sticky notes have proven super useful for visually grouping parts of the flow (e.g., agents or extra input). Some of their current limitations limit this use case, though.

• The current size constraints (800px * 1000px) mean I cannot group larger sections of the flow, e.g. to visually group all agents or all input files.
• The color constraints (only 5 hardcoded colors) mean I cannot distinguish clearly between the many different parts of the flow.

Proposed solution

1. Remove the size constraints

I don't see any downsides with removing the size constraints, though I may be missing something. This is very easy to implement.

1. Add more colors

More hardcoded colors could be added, e.g. going from 5 to 10 would provide a lot more flexibility. I'm not sure if you consider this a sustainable solution though.

1. Add a color picker and support for custom colors

The most flexible solution would be to add a colorpicker, so users of langflow could set their own custom colors. That means that a user could e.g. use Slack's purple color to document the part that uses a Slack MCP server in Langflow or the appropriate blue color for MS Teams.

Your Contribution

I'll work on two separate PRs that implement both parts of this feature request separately, in case only one of them is considered.