You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: classify User-Agent mode as interactive/agent/noninteractive
The non-TTY soft signal (pipes, redirects, CI/CD) enables agent-mode
behavior but isn't a confirmed AI agent. Tagging it mode=agent would
conflate genuine agent traffic with CI and piped use in analytics.
Derive a three-value mode= token from the detection reason: agent (only
for explicit --agent/DCI_AGENT_MODE=1 or a known AI-agent env var),
noninteractive (non-TTY soft signal), and interactive (human TTY or
explicit human mode). Runtime behavior is unchanged.
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,7 @@ that is cheap to parse and free of decoration:
92
92
- Default `--output` becomes `toon` (compact, token-efficient) instead of `table`
93
93
- No color, spinners, or other terminal decoration
94
94
- Banners, tips, and status chatter go to **stderr**, leaving **stdout** for data only
95
-
- The request `User-Agent` carries `mode=agent` (human invocations carry `mode=interactive`) so API traffic can be segmented by interface
95
+
- The request `User-Agent` carries a `mode=` token — `agent` (explicit flag/env or a known AI-agent environment), `noninteractive` (piped/redirected output or CI/CD), or `interactive` (human at a terminal) — so API traffic can be segmented by interface
0 commit comments