The ctx CLI

ctx signs in, uploads, and reads job status. It does not parse, embed, or decide policy.

ctx is a thin client on the caller’s machine. It is Rust, shipped as a native binary. It does not link the parser or the query engine. Parsing, embeddings, SQL, and policy stay on server.

The commands are:

ctx login
ctx ingest
ctx status

ctx login is a browser sign-in, then a stored credential used against api.contextdrive.io. ctx ingest walks a local tree and hashes it. One file asks server for a pending row and an upload grant, writes the bytes to that grant, and commits. Several files are zipped locally, with paths relative to the directory you are in, and sent as one POST …/files with expand set. ctx status reads that job. The laptop path is not an API field.

The ctx repository on main is that client. The three commands above are the contract. ctx login is the open work.

Note

File bytes are not posted to this website and not posted to server as a request body. The grant is the same grant Drive and MCP use. The route is on the HTTP reference. What a person does in Files is on Upload and download.