[Feature] feat: OKX live/paper trading execution via OKX Agent Trade Kit (close the backtest → execution loop)

[fanqi1909]

Problem or Motivation

Summary

Vibe-Trading currently uses OKX as a free market data source for backtesting (via the okx loader in backtest/loaders/). This proposal adds the missing execution layer: live and paper trading on OKX via the OKX Agent Trade Kit — an OAuth 2.1-secured MCP server that exposes spot, swap, futures, and algo order tools to any MCP-compatible agent.

Motivation

The current Vibe-Trading loop is:

natural language → strategy → backtest → report

With this addition it becomes:

natural language → strategy → backtest → execute (live or paper)

Users who backtest on OKX crypto data today have no path to execution without leaving Vibe-Trading. This closes that gap natively, without requiring a separate trading terminal.

Proposed Solution

Proposed Implementation

This fits cleanly into two existing contribution categories from CONTRIBUTING.md:

1. New tool — agent/src/tools/okx_trade_tool.py

Wraps the OKX Agent Trade Kit MCP server. Exposes:

• place_order (spot / swap / futures)
• get_positions
• cancel_order
• get_balance
• Simulated trading flag (simulatedTrading=true) for paper mode

2. New skill — agent/src/skills/crypto/okx-live-trading/SKILL.md

Triggers when the user says things like:

• "execute this strategy on OKX"
• "place a BTC long on my OKX account"
• "run this in paper trading mode on OKX"

The skill guides the agent through: confirm signal → preflight check (balance, position size, risk) → require explicit user confirmation → execute.

What We Can Contribute

We are the team that built and maintains the OKX Agent Trade Kit. We are happy to contribute:

• The tool implementation (okx_trade_tool.py)
• The skill definition (SKILL.md)
• Tests covering simulated trading paths (no real money needed in CI)
• Documentation

We would open a PR after discussion here.

Scope & Safety Notes

• No credentials in code — users configure OKX_API_KEY / OKX_SECRET_KEY / OKX_PASSPHRASE in .env, same pattern as existing providers
• Paper trading first — simulatedTrading=true is the default; live trading requires explicit opt-in
• Confirmation gate — the skill enforces a preflight + explicit confirmation step before any order, consistent with Vibe-Trading's existing Shadow Account pattern
• No core module changes — touches only tools/ and skills/, both open for contribution per CONTRIBUTING.md

References

• OKX Agent Trade Kit MCP server: https://www.okx.com/api/v1/mcp/trading-oauth
• Agent Trade Kit cookbook: https://github.com/okx/agent-trade-kit-cookbook
• Existing OKX data loader: agent/backtest/loaders/okx.py

Happy to discuss scope, API surface, or implementation details here before opening a PR.

Area

MCP Plugin

Alternatives Considered

No response

Contribution

• I'm willing to submit a PR for this feature

[warren618]

Thanks for the detailed proposal and for offering to contribute the implementation.

The OKX Agent Trade Kit looks useful, especially for paper/simulated workflows, but I want to be clear about Vibe-Trading's current boundary: this project is research, simulation, and backtesting only. We do not plan to add first-party live trading / real order execution tools into the core agent, including tools that can place, cancel, or manage real exchange orders.

A narrower contribution could still be a good fit if it stays strictly inside a research/simulation boundary:

• paper/simulated trading only, with live trading unavailable from Vibe-Trading
• no real order placement path in the bundled tool or skill
• no credential handling for live trading accounts
• clear docs that Vibe-Trading does not execute live trades
• tests that verify the implementation cannot switch into live mode accidentally

Another possible direction is to keep OKX execution outside this repo as an operator-managed external MCP server. Once MCP client support is stable, advanced users could configure their own execution MCP server locally, but Vibe-Trading would not bundle or advertise live trading as a built-in capability.

So I do not think we should accept the proposed okx-live-trading scope as written. If you are interested in a paper-only / research-only integration, happy to discuss a reduced PR shape here.

For now I am going to keep this issue open for discussion, but live trading support is out of scope for the project.