Field notes · No current affiliate relationship
Claude
A capable long-form reasoning and writing surface that has been part of my model comparison set, though not my current default.
How it fits my stack
Why this tool is here
I have used Claude, but it is not the tool I reach for most often now. I am keeping the assessment honest: this is a capable product in my broader experience, not a claim that I currently use every surface every day.
Direct Claude use outside GitHub Copilot and BNDT.ai. Inside Copilot, GitHub owns the repository workflow; inside BNDT.ai, BNDT owns the wearable data, session, retention, and structured-output workflow.
I am publishing this as field notes rather than inflating it into a definitive review. The experience label above says how far I have taken the tool; the decision below says the job I would give it today.
The decision
Where it earns—or loses—a place
Experience boundary
What this note rests on
- Model comparison work
- Long-form drafting and analysis
- Prior mobile and desktop use
Operating model
How I would use it
- 01Assign a distinct review role
- 02Provide the source boundary
- 03Compare the result with the primary workflow
- 04Record why one answer changed the decision
Review queue
What the full review still has to prove
- Does it produce a better result than the current tool on one defined, repeatable job?
- Can I reproduce the result with realistic inputs rather than a friendly demo?
- What breaks, how visible is the failure, and can another operator recover the work?
- Do the real limits, data path, and operating cost change the recommendation?
Same category
Compare the role, not the logo.
These tools sit near Claude in the working stack, but they do not necessarily solve the same job.