Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Comment
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor node reference
  4. /Comment
IntermediateLast verified Sep 30, 2026

Comment

Adds a non-executable note to the graph.

On this page
  1. When to use
  2. Example
  3. Record a decision for a reviewer
  4. Common problems
  5. Next steps

Adds a non-executable note to the graph.

When to use

Use it to explain intent, assumptions, or a section of a complex graph to future readers.

Example

Place a short note beside a risk branch explaining why both outcomes are handled.

Try it here

Explore Comment

Adds a non-executable note to the graph.

Exercise steps
  1. Edit the annotation text in Inspector.
  2. Move the comment on the canvas; it does not create an execution path.
Event TriggerComment
Graph preview — a diagram of the example

Record a decision for a reviewer

Next to an RSI Condition with a literal threshold of 60, write a comment such as Threshold 60 is the experiment's chosen sensitivity; reassess after comparing runs. This explains why the number is there without asserting that 60 is optimal or profitable. Comment has no control or data ports, so it cannot change the Condition outcome or receive a connection. If you change the threshold to 65, update the comment so the graph's explanation remains truthful. Use the editable parameter for the rule and the comment for its rationale.

Common problems

Comments do not validate, connect, or execute. Keep them current and never store secrets or personal information in them.

Next steps

Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Comment
Activation role
No activation role
Category
Meta
Availability
Tactical and Portfolio
Modes
Tactical and Portfolio
Required plan
None
Behavior
Adds an annotation
Control inputs
0
Output data types
None

Parameters

NameInput typeRequirementDefaultOptions and constraints
NoteLong textRequiredNot setNone

Primary parameters

  • Note

Outcomes

None

Data inputs

None

Data outputs

None

Related documentation

  • Add, move, duplicate, and remove nodesUse the palette and canvas to organize the graph without losing the meaning of its paths.
  • Backtests and responsible useInterpret simulated results with appropriate limits and avoid treating them as predictions or advice.
  • Nodes, parameters, outcomes, and portsRead the parts of a node and understand what to configure or connect.

On this page

1 / 5
  1. When to use
  2. Example
  3. Record a decision for a reviewer
  4. Common problems
  5. Next steps

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary