Documentation
Product Navigation
Astral’s signed-in experience centers on Terminal, Explore, and Dashboard. The app menu adds profile, affiliate, notification, broker, settings, theme, and sign-out actions according to account state and enabled features.
Primary routes
| Route | Purpose |
|---|---|
| /terminal | Start or resume a chat-driven research and strategy session. |
| /terminal/[sessionId] | Open a specific persisted terminal session. |
| /explore | Browse the community home, strategies, indicators, following, and saved content. |
| /dashboard | Monitor widgets and connected account state. |
| /dashboard/accounts/[accountId] | Review an individual account’s summary, activity, orders, positions, and balance history. |
| /u/[handle] | View a public profile and its published work. |
Desktop navigation
The app menu links to Terminal, Dashboard, and Explore. When authenticated it also exposes your public profile, creator or affiliate area, notifications, broker settings when enabled, account settings, theme, and sign out.
Terminal adds a right-side rail for contextual tools. Depending on viewport, account, and enabled features, it can open watchlist, alerts, strategies, portfolio, orders, broker connections, notifications, suggestions, reporting, and settings-related surfaces.
Mobile navigation
On supported mobile app routes, a floating bottom navigation switches among Chat, Explore, and Dashboard. The app menu exposes trading panels such as Alerts, Portfolio, Watchlist, and Orders. Terminal uses mobile-specific drawers and panels rather than reproducing the full desktop grid.
Some dense chart, analysis, replay, and multi-panel workflows remain easier on a larger screen, but mobile is an intentional product surface rather than a desktop redirect.
Sessions and deep links
Terminal sessions preserve the conversation and associated workspace state. Links from saved strategies, Explore details, notifications, and public items can open a specific asset or import path. Check the active session, chart, strategy, symbol, and account after following a deep link.
Public and account routes
Documentation, announcements, pricing, brokerages, MCP setup, security, privacy, terms, and help are public resources. Saving, copying, publishing, following, account monitoring, and trading actions require authentication, and some require a specific entitlement.
How context moves between surfaces
Astral is not a collection of isolated pages. Most routes hand context to another surface:
- An Explore item can open in Terminal with its strategy or indicator context.
- A Terminal result can become a private saved strategy, a public publication, or a deployment.
- A notification can lead back to an alert, strategy, order, or account state.
- A Dashboard strategy or broker widget can open a deeper detail view without changing the underlying record.
- A public profile links to publications, while private strategy and broker records remain in authenticated surfaces.
When a route opens from a card or notification, verify the breadcrumb, selected symbol, active strategy, account scope, and execution mode. The visual transition does not merge records or change ownership.
Choosing the right starting point
| If you want to… | Start in | Why |
|---|---|---|
| Research or build an idea | Terminal | Chat, charts, code, and backtests share one session context. |
| Discover community work | Explore | Public strategies, indicators, profiles, comments, and saved public items live here. |
| Monitor ongoing state | Dashboard | Widgets keep accounts, strategies, charts, and notifications visible together. |
| Inspect a connected account | Dashboard account detail | Balances, positions, orders, activity, and history are scoped to one account. |
| Manage identity or access | Settings | Subscription, notifications, connections, and account controls are account-level. |
Navigation recovery
If you are unsure where an action took you, return to the app menu and reopen the canonical surface. Opening the same saved strategy in a new Terminal session does not delete the earlier session. Likewise, navigating away from a preview does not cancel an already-submitted broker order or stop an active deployment.