cancho-tools

peek 0.1.0

Read a range of a file -- lines with numbers and offsets, or bytes -- with its size, a binary flag and a cursor to the rest; head, tail, sed -n, cat -n and wc -l in one call.

peek [--root DIR] [--lines A:B | --bytes A:B] [--max-bytes N] [--max-line-bytes N] [--count-lines] [--format json|text] PATH
output
one JSON document
schema
peek.v1
reversibility
reversible-cheap
guarantees
deterministic, idempotent, bounded_memory
concurrency
read-only: it never writes, so any number may run at once
confinement
beneath: with --root, paths are checked lexically against it and then opened beneath it one component at a time, following no symbolic link (path.symlink), so nothing outside the root is reachable through one; without it, a reader opens the path as given, links and all, and a writer still follows no link in the file's own name
reads the environment
no
reads the clock
no
compiler
de4e52fd8180
for an agent
SKILL.md (peek skill)

Authority

Derived by cancho authority from the source, embedded in the binary, and checked against tools.toml's ceiling in CI. Every label is bounded.

What the row cannot say:

Operands

OperandRoleHow manyMeaning
PATHpath-read1the file to read

Flags

FlagKindRoleDefaultMeaning
--rootpathrootresolve PATH relative to this directory and refuse paths outside it
--lines -ntextnone1:100the lines A:B to return, 1-based and inclusive, A: runs to the end of the file or the budget
--bytes -ctextnonethe bytes A:B to return, 0-based and end-exclusive
--max-bytesnatnone65536the most text returned, past it the answer is truncated with a next cursor (ceiling 16777216)
--max-line-bytesnatnone1048576the longest line returned whole, a longer one is limit.line-too-long (ceiling 16777216)
--count-linesboolnoneread to the end and report total_lines
--formatchoice:json/textnonejsonjson for a program, text (cat -n) for a person

Limits

LimitDefaultCeiling
max-bytes65,53616,777,216
max-line-bytes1,048,57616,777,216

Exit codes

CodeNameMeaning
0SUCCESSwhat was asked was done; zero matches is success
1GENERAL_ERRORthe operating system failed mid-operation, or the tool caught a bug in itself
2INVALID_ARGSthe invocation is malformed or names something of the wrong kind; nothing was read
3NOT_FOUNDa named input does not exist
4PERMISSION_DENIEDthe operating system refused, or the tool's own confinement did
8PRECONDITION_FAILEDthe answer is no, or a limit was reached

Rules (20)

Match on rule, not on the message. A retry repair is an argv that can be run as it stands, and never widens what the tool may touch.

RuleExitRepairWhen
args.unknown-flag2sometimesa flag that is not in the tool's table
args.missing-value2nevera flag that takes a value was given none
args.bad-value2nevera flag's value is not of the flag's kind
args.unexpected-value2nevera flag that takes no value was given one
args.duplicate-flag2neverthe same flag was given twice
args.conflict2nevertwo flags that exclude each other were both given
args.missing-operand2neveran operand the tool needs was not given
args.too-many-operands2nevermore operands than the tool takes
path.empty2neveran empty path
path.dotdot2sometimesa path with a `..` component
path.absolute2alwaysan absolute path where one relative to --root is wanted
path.outside-root4neveran absolute path that is not under --root
path.too-long2nevera path longer than 4096 bytes
path.symlink4nevera path that runs through a symbolic link, which the tool does not follow
io.not-found3nevera named input does not exist
io.not-a-directory3nevera path runs through something that is not a directory
io.is-a-directory2nevera directory where a file is wanted
io.permission-denied4neverthe operating system refused access
io.read-failed1neverthe operating system failed a read
limit.line-too-long8sometimesa line longer than --max-line-bytes

Evidence

each gate is a test in cancho-tools/tests/conformance, run by CI on the commit this binary was built from:

Agent in the loop: not run: no claim that this tool is more agent-friendly than the incumbents is made (cancho docs/agent-toolbox.md section 7.2).