Steps, source tags, and cost receipts
Learn about source tags, step trails, export previews, receipt literacy, second-reviewer workflows.
Definition
After each DeepShell for Chrome run you can inspect a plain-English step trail, source tags on claims where relevant, and a settled receipt such as Done · 24s · $0.019. Together they turn an AI answer into something you can defend in a review - without rebuilding a paste archaeology project.
Key takeaways
- Source tags make verification cheap; they do not make verification optional.
- Step trails matter most on long PDFs and multi-step extracts.
- A receipt is authoritative for that run, not a forever price guarantee.
- Second reviewers should click tags, not re-ask from scratch by default.
- Ready-made bots are read-only and run only while Chrome is open. Changes require permission; sending, paying, deleting, and submitting always ask first.
- Start on public pages, then apply the same loop to real work under your data rules.
Source tags that actually open somewhere
Citations should let you check the original source. DeepShell tags claims to tabs you selected so you can land back on the page.
Make a team rule for which claims require a click: anything affecting money, hiring, legal exposure, or public statements.
When you apply this to real DeepShell for Chrome work, keep the select → ask → verify → export → receipt loop intact. If a step feels skippable, it is usually the step that prevents a shallow artefact - especially verification and scope control.
For "Steps, source tags, and cost receipts", write one sentence in your team norm that captures the rule above. Norms that live only in a kickoff meeting evaporate by week three; norms that live next to the process guide stick.
Step trails on long work
Long PDFs and multi-step extracts need a trail of what was consulted. Without it, second reviewers re-do the work.
Use the trail as a teaching tool for juniors: show what good consultation looks like.
When you apply this to real DeepShell for Chrome work, keep the select → ask → verify → export → receipt loop intact. If a step feels skippable, it is usually the step that prevents a shallow artefact - especially verification and scope control.
For "Steps, source tags, and cost receipts", write one sentence in your team norm that captures the rule above. Norms that live only in a kickoff meeting evaporate by week three; norms that live next to the process guide stick.
Export previews
Tables should be previewed before download. Header repair in the panel is cheaper than spreadsheet archaeology.
After download, spot-check three odd cells against the live page every time until the habit is boring.
When you apply this to real DeepShell for Chrome work, keep the select → ask → verify → export → receipt loop intact. If a step feels skippable, it is usually the step that prevents a shallow artefact - especially verification and scope control.
For "Steps, source tags, and cost receipts", write one sentence in your team norm that captures the rule above. Norms that live only in a kickoff meeting evaporate by week three; norms that live next to the process guide stick.
Reading a receipt
Time and cost together tell you whether you over-scoped. A slow expensive compare often means too many tabs or a vague ask.
Receipts are per run. Use them to build an internal price card for common jobs.
When you apply this to real DeepShell for Chrome work, keep the select → ask → verify → export → receipt loop intact. If a step feels skippable, it is usually the step that prevents a shallow artefact - especially verification and scope control.
For "Steps, source tags, and cost receipts", write one sentence in your team norm that captures the rule above. Norms that live only in a kickoff meeting evaporate by week three; norms that live next to the process guide stick.
What receipts are not
Not a compliance certification. Not a guarantee of future price. Not a substitute for your audit tools of record.
They are a product affordance for honesty and budgeting.
When you apply this to real DeepShell for Chrome work, keep the select → ask → verify → export → receipt loop intact. If a step feels skippable, it is usually the step that prevents a shallow artefact - especially verification and scope control.
For "Steps, source tags, and cost receipts", write one sentence in your team norm that captures the rule above. Norms that live only in a kickoff meeting evaporate by week three; norms that live next to the process guide stick.
Worked examples
Public two-tab compare (universal first run)
Any evaluation should start here before confidential data.
- Open two public pages with a numeric or policy difference.
- Select both in DeepShell; ask what differs and what matters.
- Click every tag that would change a recommendation.
- Note the receipt.
What you should see: Source-tagged differences and a settled cost figure.
Second-reviewer drill
Person A runs a compare; Person B only clicks tags.
- A produces a matrix.
- B opens tags for the top three claims and marks confirm/reject.
- Discuss mismatches - usually selection or over-trust, not "AI bad."
What you should see: A review habit that scales without re-doing the whole ask.
Checklist
- the extension’s limits understood by everyone in the pilot.
- Public-page first run completed with a clicked tag and a read receipt.
- Data/confidentiality rules written down for what may be asked.
- Verification rules for consequential claims
- Export spot-check habit defined
- Internal price card started from receipts
Common pitfalls
Fix — Re-scope the evaluation to read/compare/extract/draft/export.
Fix — Click tags on consequential claims every time.
Fix — Build a price card from real runs.
Fix — Preview, then download, then spot-check.
FAQ
Is the receipt a future price guarantee?
No. Authoritative for that run only.
Can I export the trail?
Export notes/sheets from many workflows; keep sources available for audit.
What if a tag is wrong?
Do not share the claim. Tighten selection or quote the exact sentence; re-ask.
Why show time and cost?
To spot over-scoping and to budget.
Do we need tags on every sentence?
On consequential claims, yes. On pure stylistic rewrites, judgement.
How do juniors use trails?
As a review scaffold - click, confirm, annotate.
On deepshell.ai
Related guides
Try DeepShell on one real set of tabs
Free to add · free credits · cost on every receipt.