CLI command
jeden star
Read, dismiss or restart the request for a GitHub star that Jeden makes once, after the fifth successful prompt.
Exact invocation#
jeden star [status|dismiss|reset] [--json]Inputs and options#
- Optional action:
status(the default) reads the request;dismissstops it from being shown;resetsets the count back to zero so the request is made again after five prompts.--jsonprints the same status as one JSON object. - The same verbs are
/star …in a session and the RPC methodsstar/status,star/dismissandstar/reset, which take no parameters.
Output and state effect#
Every successful agent prompt counts, whichever surface sent it: the terminal, jeden run, and session/prompt over RPC, which Jeden Desktop uses. A slash command, --model-only, a continuation of retained work, and a jeden run whose standard error is not a terminal (a script, a pipe, an agent: nobody would read the request) do not count. The prompt that brings the count to five shows the request once: the terminal prints it as a system message under the answer, jeden run prints it on standard error so standard output and --json keep only the answer, and session/prompt returns it as starRequest (text, repository, prompts). The request is the star-request journey every Wisent product walks, run by the shared onboarding runtime (Echo onboarding), and kept per user in ~/.jeden/star-request.json; every verb that writes holds ~/.jeden/star-request.json.lock, so two Jeden processes finishing at once both count. status writes nothing. The status names product, stage (counting, shown or dismissed), actions, threshold, repository and file. The real journey is JEDEN_BIN=… JEDEN_TEST_SOURCE_REVISION=… JEDEN_TEST_PROVIDER_ENDPOINT=… JEDEN_TEST_MODEL=… node tests/star/journey.mjs.
Refusals and boundaries#
- An unknown action is refused as
star: unknown action "<verb>"; usage: jeden star [status|dismiss|reset] [--json]; a second argument asstar: unexpected argument "<argument>"; …. - A journey file that holds no journey state is refused by every verb as
storage unavailable: <file> is not a journey state: <cause>; `jeden star reset` sets it aside and counts from zero;resetmoves it to<file>.unreadable-<uuid>beside it and says so on standard error. An unreadable one names the file and the operating system's cause. - A prompt whose count cannot be kept still returns its answer; standard error says
jeden: this prompt is not counted toward the GitHub star request: <cause>. - Over RPC a parameter is refused as
invalid_params, an unknownstar/…method asmethod_not_foundnaming the three methods, and a journey failure asstar_recordwith the same cause. - A command line of the wrong form (an unknown command or option, a missing, unexpected or invalid argument, a missing confirmation) prints the error and the usage and exits
2; a refusal that retrying unchanged can help (a dependency down or not answering, a rate limit) exits69; any other refusal or failure exits1. A refusal a functionality declares ends withfix: …andcause: <operation>.<cause>, andjeden errors show <operation>lists every cause of that functionality.