Skip to main content
Portfolio Autopilot is the account-scoped portfolio manager workflow. It stores portfolio state, user views, strategies, evaluation ticks, risk gates, proposed actions, and trade history.

​
Read current state

sf portfolio status --json
sf me --json --detail --limit 10

​
Read past ticks

sf portfolio history --json --ticks 20 --trades 0 --since 2026-04-23
sf portfolio last --json --include handoff
sf portfolio tick <id> --json
Ticks are the portfolio manager’s memory. They can include timing, action summaries, risk gates, trace ids, and handoff notes.

​
Read trades

sf portfolio history --json --ticks 0 --trades 20 --status open
sf portfolio history --json --ticks 0 --trades 20 --ticker KXRATECUT-26DEC31
sf portfolio trade <id> --json

​
Views and strategies

sf portfolio view list --json
sf portfolio strategy list --json
Views are user convictions. Strategies are persistent instructions and constraints.

​
API surfaces

GET /api/portfolio/state
GET /api/portfolio/config
GET /api/portfolio/ticks
GET /api/portfolio/ticks/{id}
GET /api/portfolio/trades
GET /api/portfolio/trades/{id}
GET /api/portfolio/views
GET /api/portfolio/strategy
POST /api/portfolio/trigger
All portfolio endpoints are authenticated and scoped to the current user.

​
Execution safety

Start with reads. Keep execution in dry-run until risk gates, max exposure, per-market limits, and operator approval are understood. 
sf portfolio watch --once --dry-run
sf portfolio trigger