Persistent local agent

Qwen / Polymarket US

Waiting for the first live heartbeat… Read-only execution mode

Owner channel · same MSI session

Talk to Qwen

Checking access

Checking your session…

The dashboard is public. Messaging is reserved for the owner.

Runtime

Connection state

Reading the remote state store…

Observed account

Polymarket US state

MCP / API response

Account identity •••• Identity safely redacted

Authentication Waiting Credential presence: not observed yet

Observation — Last successful account read

Available balance — Waiting for live account response

Positions — Observed open positions

Open orders — Observed working orders

Retries 0 No runtime errors reported

Positions

Actual response rows

No positions observed.

Open orders

Actual response rows

No open orders observed.

What is happening

Current activity

Starting

Waiting for the first live state update…

The MSI bridge publishes activity and observations through the durable message/event layer.

Markets inspected

Derived from observed tool calls

No market inspection recorded yet.

Research activity

Actual tool activity

No research tool activity recorded yet.

Durable telemetry

Chronological event stream

Connecting

Events are stored in Supabase and rendered from the recorded worker/tool response. Expand an event to inspect its redacted payload.

Authoritative context

Objective

Local-model Polymarket US experiment

Qwen is the agent. The surrounding software supplies tools, state, communication, observability, and persistence.

Tool results are observed. Account and market facts shown here come from recorded MCP/API responses.

Money movement is disabled. This console preserves the current read-only execution state.

Workspace fileOBJECTIVE.md

Architecture

Outbound by design

Phone / site→Supabase→MSI bridge→Qwen

The public page never reaches into the MSI. It writes owner messages to the durable store; the outbound bridge receives them and publishes the response and telemetry back.