Software documentation

The software does not connect brokerage trading accounts or execute trades. Quotes and AI output are research references, not investment advice or promised returns.

These steps describe delivered features. Entries, quotas and service availability follow the installed version and account. Documentation updated 2026-11-02.

The supported platforms are WeChat Mini Program, macOS and Windows. The Mini Program runs inside WeChat; desktop apps are installed on a computer. Their features and data scopes are described separately.

WeChat Mini Program ​

Steps ​

1. Open the officially provided entry inside WeChat. The website's demonstration QR code opens this documentation, not a published Mini Program code.
2. Use Home, Markets or Funds to choose a market or fund. Check source dates and availability before adding an item to a watchlist.
3. Sign in and confirm the relevant business authorization before managing personal watchlists or groups; sign-in alone does not grant that access.

Entry or data problems: check the official entry, network and account status. A desktop installer does not resolve Mini Program entry problems.

Open the Mini Program inside WeChat through its officially provided entry; no macOS / Windows installer is needed. Contact YunStrat Support at admin@yunstrat.com for access information, subject to the actual entry and availability.

• Home, Markets, Funds and Watchlists: these four entries show currently available market overviews, quotes and fund directories. Check source dates, coverage and cache states. The Mini Program overview does not inherit the desktop stock-breadth calculation.
• Personal watchlists and account: public quotes follow current access rules. Personal watchlists and groups require sign-in and explicit business authorization. Use the available account entries for profile, avatar, preferences and history; sign-in does not automatically grant other business access, sync or subscription notifications.
• Device records and data: old device records are not automatically uploaded, migrated or merged. Cloud watchlists are separate from desktop local notes, holdings and model credentials. Check the affected scope before changing records.

Sections 1–8 below apply to macOS and Windows desktop apps. AI conversations, skills, daily reports, personal models, local data controls and import/export, and the software lock are desktop features, not an implied Mini Program feature set.

1. Check desktop installation details ​

Install and start ​

1. Choose macOS or Windows in the download center and check the version, requirements and actual link. If no package is available, use installation enquiries rather than a guessed download URL.
2. Verify the supplied SHA256 when available, follow the system installation flow, and start the app.
3. Inspect market availability first. Sign in and check the relevant permission when you need cloud AI, watchlists or reports; a platform entry does not grant every account all features.

Startup or sign-in problems: send YunStrat Support the system, app version, exact message and reproduction steps, not API keys, Codex authentication files or complete account credentials.

For macOS and Windows, check actual packages, versions and requirements in the download center, and verify SHA256 when supplied. For WeChat, use the Mini Program instructions above, not a desktop installer. Contact YunStrat Support at admin@yunstrat.com for installation questions.

2. Read the workbench and market dates ​

Inspect and refresh quotes ​

1. Choose the market and check the source, trading date, coverage and cache state before comparing indices, stock breadth, sectors or flows.
2. Open a stock and choose a chart period. Use the chart or page refresh button when needed and wait for its success or failure message. Keeping the previous response visible during refresh does not mean new quotes have arrived.
3. Intraday charts show the latest source trading day containing real minute data; a closed market can still show the previous trading day. Automatic minute refresh follows valid open sessions, not lunch breaks or market closures.
4. Index time labels use the device's local timezone; language controls formatting only. Check source trading dates, overnight closing labels and the exchange calendar. Future intraday periods stay blank and unknown sessions remain unconfirmed.

Missing charts: check dates and connectivity. A sector without valid trend data hides its chart and period controls, while refresh and constituent entries remain available. Do not substitute an ETF or stock for missing industry history.

Choose A-share, Hong Kong or US markets to see supported indices, stock breadth, sectors and flows. Local mode and server-market entries retain their own sources and states; one entry's scope does not establish another's coverage.

Stock breadth uses the actual source trading date for gains, losses, unchanged and unconfirmed counts; leaders use valid same-date records. Old dates, absent dates and missing changes stay awaiting confirmation. Source coverage is not complete exchange coverage, and collection dates do not replace trading dates.

Securities charts offer source- and entry-supported intraday, daily, weekly, monthly, quarterly and yearly periods. Check source dates, timezones, adjustment and cache status before comparing. Sector directories paginate; heatmaps show selected sectors. Flow comparisons total positive net amounts and absolute negative net amounts; overlapping sectors make this different from deduplicated market-wide purchases and sales.

US Local mode defaults to industries, with a sector-level option. Directories and members use the same Nasdaq classification; the full directory supports search and pagination. An industry directory is not an industry-index history. Missing same-identity histories and flows stay missing rather than being replaced with ETF or individual-stock series.

3. Separate on-exchange ETFs from fund NAV ​

Choose the right research entry ​

1. For exchange prices, open On-exchange ETF in Stock Market and check the code, units and trading date.
2. For open-ended funds, search Fund Market by category, then open fund NAV research in Markets & Research and check the NAV date first.
3. Choose a range and compare the chart with historical NAV records. Managers, fees and disclosed holdings follow the records actually returned by the source.

Different dates: exchange prices and fund NAV are different datasets with different closing and disclosure times. Leave missing records missing rather than deriving undisclosed NAV from prices.

The On-exchange ETF entry in Stock Market offers A-share ETF directories, search, details and watchlists. Prices use CNY per unit and volume uses units. An unknown trading date stays unconfirmed, and exchange prices are not NAV.

Browse all funds or filter by Equity, Mixed, Bond, Index, ETF feeder funds, QDII and FOF. Off-exchange ETF feeder funds show disclosed NAV and its date, not the on-exchange ETF price. Fund details include source-supported managers, fees and disclosed holdings. Hong Kong and US ETF directories are not presented as verified coverage.

Select a fund in Markets & Research to open fund NAV research and review its chart and historical NAV records. The default is the last 3 months; choose 1, 3 or 6 months, 1 or 3 years, or since inception. Fund NAV uses the periods supported by its own entry, separate from the six securities-chart periods. Historical NAV shows the disclosed records retrieved; missing records are not filled in.

4. Choose an AI path ​

Start a conversation or polish a draft ​

1. Choose YunStrat AI or Local / personal models in the research agent. Check the destination, connection and quota before selecting materials.
2. Choose instruments, watchlist items or explicit research materials and enter a question. Use @ to search enabled skill names for the current destination, including multi-word Chinese or English names.
3. Use the relevant Send action; Local / BYOK retains its preview and confirmation. Use Stop when needed, then inspect the returned content and actual task state.
4. Polishing handles only the current input draft. A complete, non-empty result replaces the draft automatically but is not sent automatically; cancellation or failure preserves the original. Review the new draft before sending.

Connection or response problems: check the destination, authorization, quota and model connection. Switching destinations does not migrate the other side's conversations. Enabled decision assistance attaches a validated read-only plan; it does not grant trading or tool permissions.

The research agent's YunStrat AI requires account access, quota and service availability. The service manages the platform default model, not ordinary users. Local / personal models use configured Ollama, your API credentials (BYOK) or Codex connections, according to the relevant entry points and service terms.

The software is free to use. Third-party AI configuration is an optional paid feature. Check the app for its activation process, scope and fee; free features remain available without enabling it. The feature fee is separate from any model usage charges imposed by the provider.

Personal-model API keys are encrypted locally; an imported Codex auth.json is stored locally as plaintext. Read the privacy notice for the storage details before configuring credentials.

Choose an instrument or watchlist item and enter your research question, then review the current destination and selected materials before using the relevant action button. Cloud chat, translation and polishing start directly from those buttons. Local / BYOK requests retain the interface preview and confirmation. Local and cloud conversations are managed separately, with multi-turn history and stop controls. Draft polishing handles only the current chat-input draft. A complete, non-empty result replaces the draft automatically without sending it; cancellation or failure preserves the original. Verify conclusions against original materials.

Cloud memory follows account preferences. A missing setting uses the current default; an explicit off preference is preserved. Watchlist and report access still need their respective business authorization. Enabling memory does not upload all local materials.

5. Preview and install skills ​

Install, enable and mention ​

1. Open the relevant local or cloud skill entry and inspect its text and source. Command installation still requires preview and confirmation.
2. New skills start disabled. Explicitly enable a skill for the current destination before selecting it with @ in a conversation.
3. Lists show 10 skills per page. Select-all applies to the current page; check the total selected across pages before a bulk action. Recheck the list and selection after changing accounts.

Missing from suggestions: check destination, enabled state and whether this is a temporary cloud conversation instead of repeatedly installing the skill.

In the local / personal model or cloud AI skill entry, review the full skill text and source before confirming installation. New skills are disabled by default. Command installation does not run shell, npm or skill scripts, or grant tool, trading or file permissions. Local and cloud skills are stored separately; previewing does not automatically upload other materials.

Where skills are supported, use @ in the conversation assistant to select enabled skills for the current destination. Local and cloud candidates are read separately; the cloud does not automatically read or upload local skills. Temporary cloud conversations do not use research skills. A referenced skill is research-method material, not permission to execute commands or access additional tools.

6. Configure reports and observe actual tasks ​

Schedule, generate and read ​

1. Choose scope, time, timezone, calendar and notification mode. A new plan starts enabled and follows global notifications; existing plans retain their timezone and channels. Review each field before saving.
2. Choose the scopes actually offered by the service: stock or fund watchlists, personal cloud watchlists, selected instruments or market overview. When supported, Any market and My positions are available; positions use only your authorized valid cloud holdings, without uploading local data. Market overview still requires a market.
3. Read the returned plan and manual-generation quotas before generating. Defaults are 5 plans and 10 accepted manual tasks per day, subject to account-specific limits; disabled plans still occupy a slot. Acceptance consumes a manual count even if the task fails or is cancelled. Retrying the same operation does not count twice, and model budgets are separate.
4. Follow the real task, then open history and the report. Check source dates, AI use, coverage and citations. Opening an existing report does not generate a new one.
5. Review selected plans before bulk disable, delete or notification changes. After partial failure, reread per-item results rather than repeating successful items. Deleting a plan retains existing reports.

Report and delivery problems: saving, acceptance, completion and notification delivery are separate states. WeChat delivery also needs configured service channels, review and your valid recipient account. Any-market dates use the chosen timezone, while each instrument retains its source date. Cross-market analysis covers at most 100 instruments and marks excess scope incomplete. Price-move explanations separate confirmed facts, unverified factors and unconfirmed causes; missing evidence is not established attribution.

In an eligible account, choose a valid plan, instruments and notification channels, review quota and materials, then explicitly start. Read the returned task date and running, completed or failed state. Acceptance does not establish that generation or notification delivery has finished. Check whether the result used AI: a basic data brief is produced without AI, so task completion does not always mean AI generation.

Retry requires an eligible failure, plan verification and confirmation, and may consume quota. Check current plans when the original plan was deleted or the date changed. Stopping page observation stops local tracking, not the cloud task. Refreshing status does not regenerate a report.

7. Manage watchlists, holdings and monitoring ​

Sync, delete and monitor ​

1. Check the account and sync authorization after creating watchlist items; use immediate sync when needed. Local records, cloud watchlists and holdings have separate scopes.
2. For bulk cloud-watchlist deletion, open My watchlist → Cloud sync → Watchlists retained in the cloud. Select individual items or all loaded records. Load more when offered, then review the count again.
3. Check the exact records in the preview and confirmation dialog, then complete the requested action verification. Only watchlist entries are deleted, not holdings. Local watchlists remain, and corresponding deleted items are excluded from automatic re-upload.
4. Inspect per-batch receipts after partial completion. A later failure does not undo successful batches. Continue the original operation when its result is unknown instead of starting duplicate deletions; reconfirmation submits only remaining records.
5. Before enabling monitoring, check the rule, instrument, quote or NAV date, calendar and notification channel, then read its actual cloud state.

Sync or monitoring problems: check business authorization, source dates and service state first. Selecting all loaded records is not selecting all cloud records; newly arrived records are not added to an earlier selection. Closing the desktop app does not stop cloud monitoring.

Search real instruments for watchlists and manual holdings without connecting a brokerage trading account. Desktop accounts with watchlist authorization synchronize automatically by default, with an explicit off switch and immediate-sync action. Sign-in does not replace business authorization. This entry syncs instrument watchlists, not holding costs, all notes or model credentials. Local records and cloud copies are managed separately; check the deletion scope.

The Monitoring view currently manages cloud rules. Check business access, enabled rules, valid quotes or published fund NAV, trading calendars and selected notification channels. Background services and recipient configuration must also be ready. Stocks use valid open-market periods; funds compare published NAV dates, not intraday estimates. Rule acceptance, condition triggers and notification delivery are different states. Closing the desktop app does not disable a cloud rule, and local system-notification preferences do not replace cloud-channel authorization.

8. Protect and back up records ​

Check before changing records ​

1. Use the relevant data/privacy settings for import and export; confirm the export scope and back up existing research records. Protect exports according to their contents.
2. Before import, check the destination device, account and file origin, then follow the interface's preview or confirmation. Import does not mean cloud records are synchronized.
3. Confirm local cleanup, cloud deletion and account closure separately, including their receipts. The software lock protects local access; it does not revoke cloud tasks.

When requesting help: provide the system and version, entry, steps, message, source date and task state. Mask account identifiers, model keys and personal research materials in screenshots.

Use local import and export to back up existing research records. The former notes entry now opens AI daily reports. Settings group appearance, data privacy and notification diagnostics; account settings show profile, login security and cloud access. The software lock protects local access, not cancellation of accepted cloud tasks or deletion of cloud data. Local cleanup, cloud deletion and account deletion require separate review; use actual service receipts as the record.

Troubleshooting ​

For market issues, check connectivity, source dates, coverage and cache state. For AI or report issues, check account access, quota, service availability and actual task status. See the FAQ and contact details.