Open console · YouTrack and Codex await configuration

Synadia NATS Agents

Synadia console in Vue/Bun, a YouTrack gateway and a separate Codex worker, connected through NATS JetStream. Discovery and diagnostic chat are connected. Running YouTrack tasks still needs access configuration.

Repository history: since 22 May 2026. Published version: 7 September 2026.Version d5b786da4 interface screenshots

01 / The task

Synadia, a NATS queue and a Codex worker

A job can take longer than an HTTP request. The gateway puts it in a queue and a worker processes it separately. It needs redelivery and a check against applying a completed result twice.

Use case: Processing issue tracker tasks through a queue and workers.

Work done

  • Webhook → JetStream → worker → result flow.
  • Durable consumer, ACK/NAK, redelivery and completed-job checks.
  • Console and worker deployment, discovery and diagnostic chat checks.

Screenshots

Screens, forms, errors

Screenshots, diagrams and source evidence retain their original language; captions and descriptions are translated.

02 / Technology

Stack

Vue / Bun

Original Synadia interface and WebSocket bridge

NATS / JetStream

Discovery, queue and durable consumers

Node.js / Codex SDK

Separate worker

MCP / REST

YouTrack after access configuration

03 / Decisions

How the project works

  • The original examples/agent-web-ui is served by Bun; scripts/start-production.js starts the processes.
  • The gateway handles webhooks and results; the worker is separate from HTTP and reads a JetStream durable consumer.
  • A separate NATS account is used; subjects youtrack.codex.jobs.komaroff and youtrack.codex.results.komaroff belong to stream KOMAROFF_CODEX.
  • CODEX_DRY_RUN=false and YOUTRACK_DRY_RUN=false. Missing credentials are not replaced with synthetic responses.
  • The console has been open without a password since 7 September 2026. The webhook requires its own token; NATS and the database are not exposed publicly.
Components and integration boundaries
Components and integration boundaries

04 / Verification

Demo workflows

  1. Open the console without signing in; check CONNECTED and the discovered codex NATS agent.
  2. Open the agent, send health and receive a real response about JetStream, subjects and consumers.
  3. After configuring YouTrack and Codex: webhook → job → separate worker → result → write the result to YouTrack.
  4. Check job states, results, redelivery and worker recovery using an agreed test task.

Check results

  • Five sequential HTTPS GET requests from the VPS to itself: 8.9–60.7 ms, all HTTP 200. This is not a load test or an assessment of the external network.
  • No Telegram collection, LLM processing or Codex task ran during the measurements.

Limitations

  • The YouTrack URL and MCP/REST access are not configured. An unreachable placeholder replaces the corporate URL; no requests are sent to the production YouTrack service.
  • Codex/OpenAI access has not yet been provided. Task execution and posting comments to YouTrack have not been verified.
  • Diagnostic health/hooks/jobs responses come from the gateway, not an LLM.
  • Discovery and gateway diagnostics are public. Current Codex Desktop tasks and subagents are not yet connected to the console.
WORK BROADCAST

Connecting to the broadcast…

How the broadcast works ↗

Technical notes

Modules, API, data model, setup and check results.

Documentation →Materials ↓