Docs/UI screenshots v0.3.0 - #34
Merged
Merged
Conversation
For the official demo: run before.py first to show the pain of debugging an MCP agent with zero observability (silent run, then just a final travel brief — no tool log, no per-server attribution, no token counts, no timeline), then run demo.py to show tracesage answering all of it. before.py is byte-for-byte identical to demo.py in agent, query, MCP client, and LLM — the only difference is the five lines of tracesage demo.py adds, so `diff before.py demo.py` shows the exact integration. It loads .env and preflights the LLM key the same way, and ends by listing what you DON'T get without tracing. Also refreshed the trip_demo README: documents the before/after pair, fixes the stale per-server tool counts (2 → 7 each; 21 MCP + 1 local), and adds the LLM token-usage drawer to the "what tracesage shows" table. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…e count Replaced the specific "two lines / five lines" integration claims with "minimal change" phrasing across the README, docs (index, comparison, changelog), and the MCP demo READMEs/scripts. The integration is a couple of imports, the setup calls, and a callbacks= kwarg — counting it as "2" undersold the imports and "5" felt arbitrary; "minimal, mechanical change, no agent rewrite" is both accurate and doesn't pin a number. Kept the inline labels in the gmail demo's code block (# two imports / # two setup lines) since those annotate the actual lines shown, not a marketing count. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The README listed only 8 of the 13 CLI commands as a flat code block, missing the ones that matter most for a demo: `demo` (zero-code "see it working"), and the terminal-native `show` / `watch` / `diff` / `view`. Rewrote it from docs/cli.md into a `demo` quick-start callout plus three grouped tables — inspect in the browser (serve, view), inspect in the terminal (runs, show, watch, diff, stats), and move/retain/diagnose (export, import, gc, doctor, version) — each with its key flags. Verified every command and flag cited (--auth-token, --max-blob-size-gb, --dry-run, --once, --tag, --all, --open) against `tracesage --help`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Type of change
Related issues
Test plan
python -m py_compilepasses on every modified Python fileruff check src/ tests/ tools/is cleanpytest tests/test_<your_module>.pypytest tests/ --ignore=tests/stressResourceWarningduring tests (no leaked DB connections / async tasks)Public-API changes
Screenshots / output
Checklist
CONTRIBUTING.mddocs/changelog.mdunder the next unreleased versiondocs/if user-visible behaviour changedSecurity policy
Supported versions
tracesage is currently in v0.1 alpha. Only the latest minor release receives
security fixes. Once v1.0 ships, the previous minor will receive fixes for
6 months after the next release.
Reporting a vulnerability
Please do not open a public issue for security reports.
Use GitHub's Private Vulnerability Reporting
to send a confidential report. If that is unavailable, email
kjgpta+tracesage-security@users.noreply.github.com with:
Response timeline
issues are scheduled into the next release
applicable
Scope
In-scope:
src/tracesage/)tracesagecommand)Out of scope:
upgrade once a fix is available.
Hardening recommendations
If you operate tracesage in production, please review
docs/production.mdwhich covers:
auth_token