Introducing Codex Agent Mode for VTX Trading

Provider Mode Remains Unchanged

Provider mode keeps the familiar VTX trading loop:

1. VTX starts an analysis cycle on the configured schedule.
2. VTX prepares the complete prompt and context.
3. The connected model returns its response.
4. VTX validates, executes, and records the decision.

Provider mode remains available for Main, Review, and Screener models. GitHub Copilot also continues to support Provider-mode decisions.

How Agent Mode Works

Agent mode changes who controls the timing and research process.

When an Agent-capable Codex model is selected for Main:

• VTX assigns the running Trader to Codex.
• Codex chooses when it should evaluate the bot.
• Codex requests zero, some, or all available assignment-scoped VTX data.
• Codex can use web research alongside VTX data when useful.
• Codex decides when it has enough information to submit a decision.

VTX does not schedule Agent prompts or force Codex to consume a preassembled context package.

Agent mode is currently available for supported Codex Main models. Review and Screener remain Provider-only.

The Decision Format Is the Same

Provider and Agent mode both return the normal VTX trading decision:

• Symbol
• Action
• Units
• Reasoning
• Tradability

Agent mode therefore does not create a second trading pipeline. The same parser, current-state validation, trading controls, execution rules, history, and audit trail continue to apply.

Codex controls when and how it researches the decision. VTX remains responsible for determining whether that decision is still valid and safe to execute.

It Is Still One VTX Bot

Agent mode does not create a separate Codex bot alongside the VTX Trader.

Codex controls the cadence of the normal running Trader through a limited assignment. Stopping the Trader, changing its model or mode, disconnecting the host, transferring runtime ownership, or revoking access ends that authority.

Old or mismatched decisions cannot silently execute against a different bot state.

Server and Client Mode Support

Agent mode works with both VTX execution modes.

In Server Mode, VTX servers receive the submitted Agent decision and run the normal validation and execution flow.

In Client Mode, the active browser or desktop app must remain the current runtime owner. It receives the Agent instruction and performs the same local validation, execution, and synchronization used by ordinary Client Mode trading.

If the required Client runtime is unavailable, the Agent decision waits rather than bypassing local ownership.

Ask Codex to Install It

You do not need to manually work through every installation command.

Open Codex on the computer that will run the inference host and paste:

Read https://vtxmacro.com/insights#subscription-inference and help me install or update the durable VTX Codex inference service. Confirm that the service is active and registered, then help me choose Provider or Agent mode for Main based on the model’s supported capabilities. Keep Review and Screener in Provider mode. Do not start my Trader until I approve.

Codex can handle the VTX CLI installation, service configuration, updates, and verification. You remain responsible for approving authentication and any action that changes or starts your bot.

After installation, Codex will confirm that:

• The VTX inference host is installed and current.
• The durable service is running.
• The intended Codex account is connected.
• The host is registered with VTX.
• Agent mode is advertised for supported Main models.
• Your Trader remains stopped until you approve starting it.

Choose the Mode That Fits the Bot

Choose Provider mode when you want VTX to control the schedule and prepare every prompt and context.

Choose Agent mode when you want Codex to decide when to act, what VTX data to request, what additional research to perform, and when its analysis is ready to become a trading decision.

In both modes, VTX keeps control of validation, risk, execution, tracking, and the final trading record.