Tim Olson
47471b7700
- Flink update_bars debouncing - update_bars subscription idempotency bugfix - Price decimal correction bugfix of previous commit - Add GLM-5.1 model tag alongside renamed GLM-5 - Use short Anthropic model IDs (sonnet/haiku/opus) instead of full version strings - Allow @tags anywhere in message content, not just at start - Return hasOtherContent flag instead of trimmed rest string - Only trigger greeting stream when tag has no other content - Update workspace knowledge base references to platform/workspace and platform/shapes - Hierarchical knowledge base catalog - 151 Trading Strategies knowledge base articles - Shapes knowledge base article - MutateShapes tool instead of workspace patch
5.1 KiB
description
| description |
|---|
| Workspace store schema: chartState (symbol/period/time range), indicators, shapes (chart drawings/annotations — see platform/shapes), and WorkspaceRead/WorkspacePatch usage. |
Workspace
The Workspace is the user's current UI context — what they are looking at, what is selected, and what persistent state belongs to their session. It is a collection of named stores that are kept in sync between the web client, the gateway, and the user's sandbox container.
Use WorkspaceRead(store_name) to read any store and WorkspacePatch(store_name, patch) to update it. Patches use JSON Patch (RFC 6902) format.
Stores
chartState — Current chart view (persistent)
Tracks what the user is currently looking at on the TradingView chart.
| Field | Type | Description |
|---|---|---|
symbol |
string | Active trading pair in SYMBOL.EXCHANGE format (e.g. BTC/USDT.BINANCE) |
period |
number | OHLC bar period in seconds (e.g. 900 = 15 min, 3600 = 1 h) |
start_time |
number | null | Unix timestamp of left edge of visible range, or null for auto |
end_time |
number | null | Unix timestamp of right edge of visible range, or null for auto |
selected_shapes |
string[] | IDs of currently selected drawing/annotation shapes |
When the user says "the current chart" or "what's selected", read chartState first.
indicators — Active indicators on the chart (persistent)
A flat map of indicator_id → IndicatorInstance. Each entry represents one study currently plotted on the TradingView chart.
IndicatorInstance fields:
| Field | Type | Description |
|---|---|---|
id |
string | Unique ID for this instance |
pandas_ta_name |
string | Internal name used in strategy/indicator scripts (e.g. RSI_14, custom_MyIndicator) |
instance_name |
string | Human-readable label shown on chart |
parameters |
object | Key/value parameter map (e.g. { length: 14 }) |
tv_study_id |
string? | TradingView study ID (assigned by TV after the study is added) |
tv_indicator_name |
string? | TradingView indicator name for built-in studies |
tv_inputs |
object? | TradingView input overrides keyed by TV input name |
visible |
boolean | Whether the study is visible on the chart |
pane |
string | "price" to overlay on price pane, "separate" for its own panel |
symbol |
string? | Override symbol if different from chartState.symbol |
created_at |
number? | Unix timestamp when added |
modified_at |
number? | Unix timestamp when last changed |
custom_metadata |
object? | Present only for custom_* indicators; drives TradingView custom study construction (see below) |
custom_metadata sub-fields (for custom indicators only):
| Field | Type | Description |
|---|---|---|
display_name |
string | Human-readable indicator title shown in TV |
parameters |
object | Parameter schema: { name: { type, default, description, min?, max? } } |
input_series |
string[] | Input price series required (e.g. ["close"]) |
output_columns |
array | Each entry: { name, display_name?, description?, plot? } where plot has { style, color?, linewidth?, visible? } |
pane |
"price" | "separate" |
Default pane placement |
filled_areas |
array? | Shaded regions between two plots or hlines |
bands |
array? | Horizontal reference lines (e.g. RSI 70/30) |
shapes — Chart drawings and annotations (persistent)
{ "shapes": { "<shape_id>": Shape } }
For the complete shapes reference — all supported types, point counts, override properties, and WorkspacePatch examples — see platform/shapes (MemoryLookup({page: "platform/shapes"})).
indicator_types — Custom indicator registry (persistent)
{ "types": { "<script_name>": CustomIndicatorMetadata } }
Maps custom indicator script names to their CustomIndicatorMetadata (same structure as custom_metadata above). Populated when a custom indicator is created or updated by the indicator agent. The web client uses this to register custom TradingView studies.
strategy_types — Strategy registry (persistent)
{ "types": { "<script_name>": StrategyMetadata } }
Maps strategy script names to their metadata. Used by the web client to know which strategies are available.
research_types — Research script registry (persistent)
{ "types": { "<script_name>": ResearchMetadata } }
Maps research script names to their metadata.
channelState — Connected channels (transient, gateway-only)
Tracks which communication channels (WebSocket, Telegram, etc.) are connected to the current session. Not synced to web clients.
{ "connected": { "<channel_id>": { type, connectedAt, capabilities } } }
Sync Protocol
Stores are kept in sync using JSON Patch (RFC 6902) messages:
- snapshot — full state dump sent on connect or after missed patches
- patch — incremental change with a monotonic sequence number
Stores marked persistent are saved to the user's container at /data/workspace/{store_name}.json and survive session reconnects.