Set up your trading workspace with TradeAssembly and Jev

This is the first chapter of Trading with Jev, a series on using an agent and TradeAssembly to build, test and understand your own trading workflow.

Today you’ll use Codex to connect TypeSafe’s Jev model through TradeAssembly, find the tool that defines a strategy’s fields, and follow one call from Jev’s choice to Core’s answer. You’ll learn what the agent, Jev and Core each do, and how to read the model’s confidence before the agent takes the next step.

If your agent guesses the fields, you can end up with rules TradeAssembly can’t use. We’ll ask the product for its rules and have the agent explain them. You don’t need a broker account or an order to complete this exercise.

Before you start

Use TradeAssembly from its official release, connected to Codex. This walkthrough assumes your version includes the Jev integration. Ask the agent to check that in the first two steps.

You’ll also need an API that offers Jev: TypeSafe’s API or a model router. We’re using OpenRouter because it’s convenient. Your API provider needs to work with TradeAssembly’s Jev integration. Connect its credential through the supported setup; don’t paste your API key into the chat.

1. Check the connection

TradeAssembly Core is the local software your agent calls. Before asking the agent to do anything with a strategy, make sure that connection works.

Prompt

Check my local TradeAssembly connection. Show me the version and find the tool that returns the strategy fields. Don’t create a strategy or connect a broker.

Result

In our test, Core reported version 0.1.0. It offered 149 tools, including tradeassembly.strategy.schema.

Explanation

tradeassembly.strategy.schema returns the fields we need. A schema describes the fields a strategy must contain. By getting it from TradeAssembly, the agent can use the product’s rules instead of making up its own.

If the tool is missing, have the agent check the installation instructions for your release before continuing.

2. Connect Jev

Codex handles the conversation. Jev answers a specific question with a structured result. Here, it will choose between two actions: schema retrieves the strategy fields; review stops and asks you to review the request.

Prompt

Check whether this TradeAssembly version supports Jev through my chosen API provider. If it does, set up the plugin through TradeAssembly and check that it’s enabled. Show me the result. If something’s missing, tell me what I need.

Result

Our test used OpenRouter. Core installed Jev plugin 0.1.1, created the jev-schema instance, configured it and enabled it. The plugin check passed.

Explanation

The agent does the setup through TradeAssembly. You don’t write a script or change your trading rules. We’ve tested the OpenRouter path; another provider needs its own check.

Next, we’ll make one call to Jev and see what it returns.

3. Ask for the strategy fields

Give the agent a question it can answer without touching an account.

Prompt

Show me the fields needed to write a TradeAssembly strategy. Use Jev to choose between schema and review. Show me its answer and confidence. Call the strategy schema tool only if Jev chooses schema with confidence of at least 0.8. Otherwise, stop and ask me to review it. Stop if the answer is invalid, too.

Result

Jev chose schema with confidence 0.99. It returned these probabilities:

{"schema": 0.99, "review": 0.01}

The agent then called tradeassembly.strategy.schema. Core returned StrategySpec, with 13 fields, 10 of them required.

Explanation

Jev chose the next action. TradeAssembly supplied the fields. You can see both results, rather than taking the agent’s word for what happened.

The confidence number is Jev’s answer, not a guarantee that it’s right. We chose 0.8 for this example. Below that, the agent stops for your review. Our live call took the schema route; separate tests checked the low-confidence, review and invalid-answer cases.

flowchart TD
    A[Ask for strategy fields] --> B[Jev chooses a route]
    B --> C{Schema with at least 0.8 confidence?}
    C -->|Yes| D[Core: fields]
    C -->|No or invalid| E[Review]

4. Have the agent explain the result

A list of field names isn’t much use until you know what they mean. Let the agent walk you through them.

Prompt

Explain the name, allocation, variables and stages fields TradeAssembly returned. Use plain English. Point out where I’ll need to supply my own rules. Don’t choose trades or create a strategy.

Result

The schema included name, allocation, variables and stages among its required fields. It allows no extra fields at the top level.

Explanation

The names give you a starting point. A strategy needs a name. Its allocation chooses a method, such as relative weights or a formula. Relative weights describe proportions between targets. Each target uses selector_ref to identify what the weight applies to and relative_weight to give its proportion. Its variables hold values your rules use. Its stages cover jobs such as checking inputs, evaluating rules, sizing and handling exits.

You haven’t written a strategy yet. You’ve found out what TradeAssembly expects one to contain. Keep the returned fields with the Jev answer so the agent can use them when you’re ready to supply your rules.

No strategy was created or activated in this test. No orders were submitted.

Where Relay comes in

You don’t need a broker connection to finish this exercise. When you move on to paper trading, Relay can help connect TradeAssembly to your provider. It’s an optional paid companion.

Ask the agent to check permission to use Relay and the broker connection separately. In our staging test, permission passed, but the broker connection failed with plugin_oauth_relay_rejected. Permission to use Relay did not prove the broker connection completed.

That’s the useful question to carry into paper trading: did the connection finish? Have the agent show you the answer before you ask it to work with the account.

Tested versions

Tested October 2, 2026: Core 0.1.0 development build (3abf3e052b93, with the Jev integration change), Warden 0.1.0 (be9ac371e1e2) and Jev plugin 0.1.1, using SDK 0.1.0. OpenRouter returned typesafe/jev-1.13-20260917.

The separate staging connection test used Core 0.1.0, Warden 0.1.0 and Alpaca plugin 0.1.17. Relay’s deployed version was not confirmed.

Continue the series

This is chapter 1 of Trading with Jev. Next in the planned series: Run your first Jev-assisted workflow in TradeAssembly. We’ll build on this connection check with one small task, then work through its inputs and result.

Browse all TradeAssembly articles, or join the TradeAssembly waitlist for Core and Relay launch updates and new chapters.