- login tool was calling api.login() which did not exist in unified_api,
causing AttributeError on every invocation. Now calls login_to_schwab
directly with proper credential fallback to config.json.
- upload_cookies hardcoded 'cookies.json' instead of get_cookies_path(),
and did not handle wrapped export formats ({cookies: [...]}). Both fixed.
- Result envelopes now match the standard {success, data, error, error_type,
retryable} shape used by other tools.
Add diagnostic logging to the MCP login tool handler:
- Log whether username/password were provided explicitly
- If falling back to config, log the resolved config path and whether it exists
- This complements upstream scraper v0.6.18 credential diagnostics
Bumps version to 0.2.1.
Temporarily switch from the local schwab-browser sidecar to the
browserless endpoint used by the working CLI (browser.local.ben.io).
This tests whether /assert 403 is caused by browser environment drift.
- Set up logging.basicConfig() at module load so scraper logs reach stderr
(visible in docker logs instead of silently dropped)
- Replace StringIO-only capture with TeeHandler that writes to BOTH stderr
and the StringIO buffer, so logs remain visible in docker while also
being returned in tool responses
- Add explicit 'LOGIN TOOL CALLED' and 'DEBUG MODE ENABLED' log lines
at the start of the login tool so users can verify logging is active
Scraper debug output goes to stderr which is invisible in MCP stdio mode.
Add capture_logs context manager that attaches a StringIO handler to the
schwab_scraper logger during tool execution, then includes captured logs
in the response envelope when debug=True or on failure.
Applied to login() and refresh_session() which are the critical paths
for authentication diagnostics.
actions/checkout@v3's Basic auth header pattern fails with 403 when
accessing a different private repository. Switch to a plain git clone
with the CRT_READ_ONLY token embedded in the HTTPS URL.
Patch RequestResponder.respond() and cancel() at startup to handle
the race where a notifications/cancelled arrives between handler
return and respond(), which crashes the session with
"AssertionError: Request already responded to".
Also improve build.sh to handle registry push failures gracefully
and auto-restart the container after building.
- Dockerfile now installs schwab-scraper from vendor/ dir (no git needed)
- Upgrade playwright to latest to match browserless chromium container
- CI workflow checks out schwab-scraper into vendor/ before build
- Add scripts/build.sh for local builds via docker-test
- Add curl to runtime image for compose healthcheck
- Increase memory limit to 512M for large account position scraping
- Update schwab-scraper to f52774b (optimized lot extraction polling,
faster account switching with selector-based waits)
- Install curl in Docker image so compose healthcheck works
- Remove bundled schwab_scraper/ source (now installed via git dep)
- Increase memory limit to 512M for large account position scraping
