Video summary

I Turned GPT-6 Astra Into a 24/7 Stock Trader (tutorial)

Main summary

Key takeaways

Product Review

Product/Service Reviewed

GPT-6 Astra — an automated “24/7” stock trading agent that uses scheduled routines to research and make trading decisions throughout the trading day, primarily using Alpaca for market data and trading execution.

Key Features Mentioned

AI-driven strategy generation

  • Strategy generation via AI agents: Astra is prompted to research and produce a trading strategy under constraints.

Scheduled “wake-ups” (day-trading oriented)

Astra runs multiple routines during market hours (Central Time), including:

  • 7:45 a.m. Central: read news, check account, choose stocks to watch
  • 9:30 a.m. Central: look for the first qualifying trade
  • 11:00 a.m. Central: review positions; consider the last new trade
  • 1:00 p.m. Central: manage existing positions
  • 2:15 p.m. Central: close remaining positions
  • 2:45 p.m. Central: confirm exit and record results

Stateless continuity using persistent records

Because each scheduled run is designed to be stateless, Astra relies on persistence tools rather than AI memory:

  • Uses persistent files (e.g., strategy doc, progress log, journal, evidence)
  • A progress log / handoff messages mechanism ensures each run continues where the last one left off
  • Designed to avoid repeating trades if runs are interrupted

Safety and failure-handling plan (brainstormed)

The setup includes considerations for edge cases such as:

  • no prior progress record on the first run
  • no chat history available
  • crash after sending an order
  • overlapping runs
  • missing or corrupt data
  • machine/app offline

Trading execution via Alpaca

  • Uses Alpaca API key + secret
  • Supports paper trading first, then switching to real cash

Local vs. cloud scheduled tasks

  • Local runs are preferred to allow using the GPT-6 Astra model + reasoning settings
  • Cloud execution can keep running while the device is offline, but may lack certain configuration options needed for GPT-6 Astra

Notifications automation (ClickUp)

  • Adds scheduled tasks to send updates to ClickUp:
    • midday and end-of-day reports
    • via an internal automation / channel DM
  • Reports are sent even when there are no trades

Remote access / monitoring

  • Phone-to-desktop “remote” mirroring/sync so the user can monitor and manage the agent thread remotely.

Pros (as implied/explicit in the video)

  • Demonstrated strategy performance from a prior challenge: earlier Claude-based results reportedly beat the S&P by a little over 8% after a month.
  • Automation reduces constant monitoring: designed to run scheduled trading routines without continuous manual oversight.
  • Continuity approach reduces randomness: progress logs and handoff instructions aim to make it feel like one continuous agent rather than separate workers.
  • Recovery from interrupted runs: critical actions are recorded so it can continue without accidentally repeating orders.
  • Operational visibility: detailed reporting through ClickUp plus account/trade visibility.
  • Configurable notifications: midday and end-of-day reporting even with no trades.
  • Remote monitoring: check progress while away.

Cons / Limitations Mentioned

  • Not financial advice: cautions against blindly funding with real money.
  • Paper trading recommended first before live trading.
  • Cloud scheduled task limitations: cloud mode is not ideal because it restricts chat/project model/reasoning settings, which is problematic for GPT-6 Astra configuration.
  • Continuity is system-built (manual setup): since scheduled runs are stateless, persistence + handoff must be set up correctly; otherwise behavior may become erratic (“throwing darts at the wall”).
  • Setup overhead and complexity: requires configuring scheduled routines, persistence, Alpaca integration, and ensuring scheduled task threading works properly.

Comparisons Made

  • Against the S&P: prior Claude challenge reportedly outperformed it by “a little over 8%.”
  • Within workflow setup: compares local vs. cloud execution and references similar remote/automation patterns (e.g., “Grok Bot way or Cloud Code remote”).

Ratings / Numerical Scores

  • Performance metric claim: a little over 8% beating the S&P (after one month in a prior challenge)
  • Trading schedule frequency: 6 checks/wake-ups per trading day
  • Challenge constraint: $10,000 and 7 trading days
  • Notification timing: additional updates at 1:00 p.m. and 3:15 p.m. Central
  • Alpaca data plan price mentioned: $99/month for real-time market coverage
    • (the user states they didn’t pay for the earlier 10K challenge, but would for this 7-day run)

Unique Points Mentioned (from subtitles)

  1. Claude-based $10K challenge beat S&P by a little over 8% (leading to the new Astra test).
  2. Goal: demonstrate how to set up Astra for automated trading across a 7-day challenge.
  3. Disclaimer: not financial advice; start with paper trading.
  4. Astra strategy is constrained by $10,000, 7 trading days, and six daily checks.
  5. Astra research process uses ~10 sub-agents and consolidates into a single strategy doc.
  6. Two user paths: outsource strategy research vs. needing faster daily monitoring.
  7. Proposed trading schedule uses specific Central time actions (7:45, 9:30, 11:00, 1:00, 2:15, 2:45).
  8. The strategy is more day-trading than long-term investing.
  9. Continuity problem: each wake-up is stateless.
  10. Continuity solution: shared strategy records + persistent progress log + handoff instructions.
  11. Each routine: read strategy, read portfolio (Alpaca), perform job, update state/progress, then specify next steps.
  12. Without continuity it may behave randomly.
  13. Critical actions are recorded to support recovery from interruptions.
  14. Persistent files include progress log, journal, evidence.
  15. Failure scenarios listed (no progress record, no chat history, crash after sending order, overlap, missing/corrupt data, offline).
  16. A free resource guide/document exists (linked via community) to replicate the system.
  17. Paper trading first, then real money.
  18. Connect Alpaca with API key/secret; avoid exposing keys.
  19. Real account mentioned: $10,000 cash/equity; no positions/open orders at the time shown.
  20. Alpaca real-time coverage discussed: $99/month for real-time data and more API calls.
  21. Other data integrations/providers mentioned alongside Alpaca.
  22. Alpaca connection verified: keys work; Astra can trade.
  23. Local vs. cloud scheduled tasks distinction.
  24. Local scheduling chosen because cloud lacks GPT-6 Astra model/reasoning settings.
  25. Use the same conversation thread across routines to help keep context via system auto-compaction.
  26. Create a dedicated project/folder to isolate trading bot context.
  27. Use a “/goal” prompt to create six scheduled tasks in the same challenge thread.
  28. Routines specify folder/file paths and handoff behavior (startup/end/run handoff).
  29. Add ClickUp notifications (two updates per day).
  30. Reports send even when no trades occur.
  31. Example notification: ClickUp DM showing it was sent by “ChatGPT…”.
  32. Notifications tasks updated at 1:00 p.m. and 3:15 p.m. Central, shifting the midday report.
  33. Routines are paused until the next trading day, then run automatically.
  34. Remote monitoring: phone mirrors/remote into desktop to monitor the same thread.
  35. Plan: monitor for 7 days, then potentially run for multiple months and refine based on mistakes.

Speakers / Contributions

  • Single main speaker: the creator narrates the full setup and rationale.
  • No other distinct speaker perspectives are present in the subtitles.

Original video