Terminal workspace

Terminal brings token research, charts, strategy logic and backtesting into one workspace.

Start and continue a conversation

On mobile or in the compact browser shell, the bottom tabs are Chat, Search, Feed, Notifications, and Profile. Chat returns to the active conversation where available; changing tabs does not start a new one. Profile retains the Dashboard workspace. Market search opens an exact asset's chart in a sheet over the current page. It does not automatically switch to Terminal; an explicit Ask about, Chat, Fork or View in Terminal action can open the conversation/editor. See Mobile chart workspace for contextual questions and return controls.

In a populated mobile conversation, message history scrolls beneath the floating input and bottom navigation. Scroll to the end to bring the final message above the controls; the clearance adapts as the input grows or the keyboard changes. The empty-conversation starter remains centered. Desktop conversation layout retains its own controls.

1. Choose Chat beside Trade.
2. Type in Ask Astral anything… and press the send arrow. Enter sends the message when the composer supports it; Shift+Enter adds a line.
3. Use Attach images to attach PNG, JPEG or WebP images before sending. A screenshot can help explain a UI issue; attaching an image does not authorize actions shown in it.
4. Use the intelligence selector (for example Fast) to choose an available option. Availability can depend on the account.
5. Use View chat history to return to a previous session. Start new chat creates a separate conversation; it does not erase account-wide holdings or running strategies.

The active chart supplies context for phrases like “this token.” Name the intended asset, interval and mode when several are involved. Click a linked asset in an answer to open its chart. Ask follow-ups in the same conversation to revise the current strategy.

Before the first message, the standard experience offers major-coin rotation research, small-cap token rotation research, then market research. Six major-coin requests compare Bitcoin, Ethereum and Solana together, replacing the repeated single-coin ideas. The 12 small-cap token requests still cover Solana, Base, Robinhood Chain and Arbitrum, one network per request.

The visible sentence is exactly the message sent on desktop and mobile: each strategy research request is no more than 20 words, with no hidden build recipe. For example: Research 1m rotation: buy the prior minute's worst BTC, ETH or SOL, with stop losses and realistic costs. The messages request research, not an explicit build or new backtest. Source and interface checks do not establish how an agent will implement the request or whether it will earn money.

The blue-chip research group explicitly uses 1m bars and compares BTC, ETH and SOL. Its six ideas vary the entry logic: the previous minute's weakest performer, that loser after a bounce, two falling candles followed by one rising candle, range lows targeting the middle, sharp drops starting to reverse, or a coin rising while others fall. Each retains stop losses and costs. These are distinct research triggers, not six validated trading edges. Define how to choose one holding, break ties and exit if several candidates fit; rotation does not mean three independent strategies or repeated accumulation.

For the previous-minute loser ideas, compare percentage returns over the last completed minute, with observations aligned to that decision. The worst is the lowest percentage return, not the largest dollar-price change; if all three rose, it is the smallest gainer. This ranking applies to those ideas rather than every blue-chip request. The other patterns need their own measurable definitions using completed observations and a stated selection rule. See Previous-minute reversal research.

The separate network-token group retains taking profit after a set holding time if profitable, taking profit at a target, and taking profit when buying fades. Every request includes an entry stop loss and costs. Its bar interval and entry-screen details remain unspecified: it does not inherit the blue-chip previous-minute ranking or 1m cadence. Holding time means age since entry with profitability checked when old enough, not continuous time in profit. Stops remain independent while losing. Network-specific eligibility, data and execution limits still apply.

These research ideas do not establish positive bear-market returns. A bounce during a broader decline may still fail, and a relative winner may stop rising. Cash when no entry qualifies needs actual entry and exit rules in a later build; an absent candidate does not automatically close existing until-exit holdings. Stops do not guarantee fill prices or loss caps.

Assess estimated round-trip fees, spread and slippage with disclosed assumptions and no double counting. A positive zero-cost result, many small winning trades or an attractive candle chart does not establish executable net profit. Review declining-market periods separately and retain results from periods not used to choose the rules. Adding stops, changing the entry trigger or changing an exit creates a different variant; a prior result does not validate it. Existing research drafts and saved/deployed strategies are not changed by these suggestions.

Neither group prescribes a position size, profit percentage, holding duration or test dates. Existing sizing, market eligibility and network-specific metric limits still apply unless the user changes them. Solana token rotation means tokens on that network, not native SOL or SOLUSD; the separate major-coin basket explicitly includes SOL. Robinhood Chain means blockchain tokens, not Robinhood stock. Suggestions have no native browser tooltip. See Strategy reference and Backtesting.

New batches avoid repeating known presets until their own pool is exhausted and prefer a different strategy family and token network where possible. This uses preset IDs stored only in this browser tab, separately for the standard and trade-first experiences. Blocked or cleared browser storage can allow repeats. An ordinary rerender does not reshuffle the displayed batch. Trade-first keeps its money-made, small-buy-for-review and strategy-research order; a proposed buy still needs confirmation.

Suggestions do not change saved strategies or grant deployment or trading permission. The same starting ideas appear on desktop/mobile web and in Paper/Real money; actual availability and execution checks still apply. Installed clients can differ by release.

After a reply, suggested follow-ups are written as messages you could send, in the language the assistant is answering you in. Tapping one sends it as your message. They never repeat a request the assistant has just said it cannot do.

Answer a question from the assistant

When the assistant needs a decision it cannot reasonably make for you, it shows a question card in the conversation and waits. The step reads Waiting for your answer and the message box placeholder changes to Astral is waiting: type your answer…. Answer in any of these ways:

• Select one of the card's options. A single-choice option is sent as soon as you select it.
• Type in the card's own answer box and press its arrow.
• Type in the main message box and press the send arrow or Enter. While a question is waiting, what you type there is sent as your answer to that question, not as a new message. You can answer in your own words even when the card lists options.

With nothing typed, the message box button is Stop, which cancels the whole turn rather than answering. The card then shows Answered with your reply. If you do not answer within 5 minutes the card shows This question timed out. Reply in the message box to continue. The assistant then either continues with the safest default and tells you which choice it made, or ends its reply by asking you once in plain text; send your answer as a normal message. Tell the assistant not to ask questions and it chooses reasonable defaults and states them for the rest of that chat. Trade, alert, deployment, publish and stop confirmations are still always shown. This applies on desktop and mobile web in Paper and Real money; installed clients can differ by release.

Images upload before the message is submitted. If an upload is refused or temporarily unavailable, the composer retains its text and images. Follow the retry/quota notice; an upload failure does not mean the assistant received the message.

Understand the panels

Chat contains conversation and tool progress. Trade is an order ticket. The asset list and chart are separate from both. The Code panel displays the current strategy source read-only; ask the agent to change the rules. Expanding a panel changes its visibility, not the strategy. Chart indicators and the strategy's internal calculations are separate unless the agent explicitly edits the strategy.

In the desktop terminal, the chart area shows Loading chart… while its initial or saved chart selection is being restored. No asset chart selected appears after restoration only when the workspace has no chart; use + to choose one. This loading state does not indicate missing market history or a failed order. Chart data can continue loading after the selected asset appears.

The desktop Trade draft follows the active chart tab, including when you switch charts while Chat is visible. Changing chart assets starts a draft for the newly selected asset. Reviews, submitted orders and pending agent proposals retain their original trade details. See manual trading for the asset and account checks.

The agent chooses relevant charts and plots relevant indicators with chart tools. Strategy source/tool events do not automatically retarget charts or extract studies. Mobile web follows confirmed chart actions, not keywords in your message. A saved layout can restore as recorded. Explicitly opening Saved or Deployed can also initialize price charts from known assets, including actual recorded rotating-strategy coins; it does not infer studies from rules. If a study is missing, name its exact asset, interval and complete formula and ask the agent to plot it. This is the same in Paper and Real money; it does not rerun or change the strategy.

Tool step timing and backtest cards

Tool groups show Working… while active and Worked for… afterward. This is the group's elapsed work, including a tool's execution through its recorded result, not just model reasoning or a promise about total request latency. Restored conversations use recorded event times; Work duration unavailable means missing result timing or interrupted work cannot establish the complete elapsed duration. A completed backtest card describes the backtest job, not a successful investment, loaded indicators or a live deployment. Inspect any separate chart/replay loading error and the actual result before proceeding.

Choose Results on a completed backtest card to inspect that recorded run. On mobile web, Backtest results → Analysis / Replay / Code works without an inline chart; Code shows this chat's current strategy source, read-only, and Back to chat returns to the conversation. This is read-only inspection, not a new run or a change to the current strategy. If the archive cannot load, choose Retry for the same run. See Review results and replay.

Interruptions and connection problems

For manual swaps, the recorded input asset is what you sent and the output asset is what you received. Routine settlement acknowledgments use that direction and may omit token quantities when their decimals are unavailable. They do not establish a current wallet balance. The assistant can stay quiet for routine activity; an absent message is separate from chart-fill visibility. Inspect Positions & Orders → Orders for the original order, amounts and status before retrying a trade. See Wallet fill markers.

Choose Stop to request cancellation. The next message remains blocked until the turn reports that it has stopped or finished; sending the cancellation command alone is not confirmation. You can keep drafting while waiting. A rejected send keeps the draft so you can retry after recovery.

If chat reports Chat setup timed out, the pre-send capability check did not finish within 15 seconds. That message has not been sent, and its draft remains in the composer. Wait briefly, then send it again. Stop during this check abandons that unsent attempt; it is different from cancelling an already-submitted turn, which still needs confirmation. Neither outcome undoes earlier orders or backtests. This applies on desktop and mobile web in Paper and Real money; installed clients can differ by release.

Read the chat's reconnect/sign-in notice if a response stops. An interrupted reply is not proof that an action failed or was rolled back. Reopen the session and inspect the relevant saved strategy, backtest or order before requesting it again. The UI may ask whether to continue an interrupted operation; preserve the intended request rather than assuming a fresh conversation has no prior account activity.

If chat reports We're experiencing technical issues. Please try again later., wait and try again later; you can continue in the same conversation. The failed reply does not automatically rerun the whole request. Completed tool actions remain recorded; the error does not undo a saved strategy, completed backtest or submitted order. Check actual order status before repeating a trade request, and do not bypass an unresolved-action or reconciliation hold. These recovery steps apply in Paper and Real money on desktop and mobile web; changing mode or starting a new chat does not reset prior account activity.

In a very long single request, the assistant keeps working by setting aside older tool output from that request; it can look something up again if it needs those details. If chat reports This request has grown too large for the model to continue in one go. Start a new chat, or ask for a smaller piece of the work at a time., start a new chat or split the request into smaller steps. Work the assistant already completed, such as a saved strategy or a finished backtest, stays recorded.

Recover out-of-date chart context or a table with missing cells

If a chart-context warning says the chat is out of date, copy your draft before reloading that same chat. Verify the restored token and interval before sending again. Astral refuses the send rather than silently using a different chart revision. A normal chart change that is still synchronizing can finish without a reload.

A completed table marked incomplete or inconsistent is not a verified result. Missing cells are unavailable, not zero or still-loading final metrics. Ask the assistant to retrieve the exact stored result and show a complete table; do not infer a metric from a similarly named field.

Identify the market

Choose a token from discovery or use exact Solana mint search. Verify network, address and the chart's denomination. Tickers can be ambiguous: search lists same-ticker tokens most-traded first, and the assistant searches every network when you name a token without one, then tells you which network and address it used. Available chart intervals and history depend on the token and source.

Inspect context

Review price, liquidity, volume, transaction activity and holder data where available. Missing data is not zero. Community token conversations and the AI research assistant serve different purposes.

Build through conversation

Describe the selected token, interval, entry, exit and sizing. Inspect the generated code before testing. Ask about unsupported inputs rather than assuming every visible research metric can drive a historical strategy.

Test and save

Run a backtest and read its effective period, warmup and cost assumptions with the results. Save a version to revisit. Saving does not publish, deploy or submit a transaction.

In Strategies, clicking a Saved strategy's name or row opens its details modal; clicking a tracked Deployed strategy opens its Live workspace. ⋮ → Details opens the details modal for either. Choose ⋮ → View in terminal to open a chart workspace: Saved opens its stored code and available results; tracked Deployed opens Live. Alerts-only rows keep their existing controls. Opening saved work without a result does not automatically run a backtest. See Find and reopen saved work.

Strategy opening takes priority over the previous chat's charts. Saved chart targets retain their exact assets and intervals; remaining declared assets use the saved engine interval. Rotating strategies without fixed assets can use actual coins recorded in saved positions, trades or token selections at the recorded cadence. If no coin was recorded, No asset chart selected points to the existing + control. Studies restore only from recorded indicator attachments. A remembered Live session is reused only when it still identifies the selected strategy; an unrelated session does not supply that deployment's charts.

After a confirmed backtest deployment in the same session, the chart shows a compact Live / Backtest toggle. On desktop, hover Live for the strategy name, Paper/Real mode and starting/ready/blocked/paused status; screen readers can access the same details. Backtest shows the backtest saved with the strategy, however the Live view was opened, and is disabled only when the strategy has none. Between the strategy's bar closes, Earnings and Total return, without small Live badges, and the Allocation bar's Open P&L re-price open positions from the live price; Trades counts filled buy/sell orders, while win rate uses completed-position outcomes; the next bar close records the stored value. Quotes expire after 15 seconds without another update and clear on reconnect, account or saved-snapshot changes; the view uses the recorded values until a fresh quote arrives. Reconnect appears with a live-data error in the performance chart and retries data without redeploying. The Pause button in the chart’s top-left action group pauses the strategy after a confirmation; resume, stop and liquidation stay under Strategies → Deployed. Pause keeps the strategy and existing position management and does not liquidate holdings. Publish shares the deployed strategy through the same publication flow as Dashboard → Publish; it does not change the deployment. In Terminal Strategies → Deployed, the strategy name or row opens the Live workspace; ⋮ → Details opens its details modal. Returning reuses the last monitoring session recorded in this browser for that user and strategy run. Opening or switching strategies keeps the desktop Chat sidebar in its current open or collapsed state; use its existing toggle to change it. Mobile web opens the fullscreen strategy chart. A fresh workspace charts open positions, recent trades and named assets within your plan's chart limit; a rotating strategy can use saved-backtest coins as price context until its first actual live asset is recorded. This does not indicate a current holding. Without any recorded coin, it shows Waiting for the first position in the chart area. Later trades leave the chosen charts in place. See Confirm and monitor in Terminal for restoration limits, account checks, navigation and stopping/resume boundaries.

Operate deliberately

Positions & Orders → Positions omits available Cash and funding-stablecoin balances in both Wallet holdings and Strategy positions, for Paper and Real money on desktop and mobile web. Inspect balances and funding actions through Cash or Paper cash in the header, mobile Profile, or Settings → Wallets. Portfolio value still includes cash; a cash-only wallet can have no open positions.

Token positions and the portfolio total use incoming live price updates, with a five-second reference-price fallback for tokens without recent streamed updates while the view is visible. Balance and entry-cost refreshes are separate. See Live token position P/L for connection, pricing and cost-basis limits.

Use the modes available for the token and account. Paper and live activity are distinct. Where wallet functionality is available, review funding and permissions before enabling live activity.

See Strategy workflow, Backtesting and Navigation.