jid CLI
The interactive viewer explores JSON with field suggestions so users can verify an agent’s expression and returned data.
- 7,210 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The utility reads local JSON and saves expression history; output can expose selected private fields.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/jidDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The utility reads local JSON and saves expression history; output can expose selected private fields.
This is third-party code. Review the repository files before installing.
What it does
In a large API response, users may know a field name without knowing its full path. In jid they enter path segments, cycle suggestions with Tab and immediately inspect the selection. This supports navigating nested objects and arrays before preparing a final expression for a script. JMESPath functions handle conditions and transformations. Suggestions follow the current data type and show function-argument templates. Up and Down revisit earlier queries, connecting field navigation with formulas in one interface.
Who it is for. Analysts of nested JSON responses refining agent-prepared expressions through interactive inspection.
Good fit when
- An API response has a deeply nested field whose path needs refinement.
- A user wants to inspect an agent-proposed array selection.
- Function suggestions should reflect the current data type.
- A previous expression should be recovered from history.
Not a fit when
- The input is another format not yet converted to JSON.
- Processing must be unattended without terminal interaction.
- One expression must work unchanged in every jq and JMESPath implementation.
Example request
Suggest the path to the required JSON field; I will verify it in jid with completion and return the confirmed result.Limitations
jid accepts JSON in an interactive terminal; convert other formats first. In `.game_indices[*].version[0]`, jid selects the first version object from the combined result. Standard JMESPath applies the index to each projected element and returns [] for this example, so expressions are not portable without verification. Queries confirmed with Enter are retained in local history; avoid passwords and other values that must not remain on disk.
How to disable. Exit jid and inspect redirected output. Clear query history and saved exports when necessary.
FAQ
How do I open a JSON file?
Use `jid < file.json`.
How do I see available fields?
Press `Tab` to show and cycle suggestions.
How do I prevent accidental exit on Enter?
Set `exit_on_enter = false` under `[behavior]` in `config.toml`: Linux uses `~/.config/jid/`, macOS `~/Library/Application Support/jid/`, Windows `%AppData%\jid\`. Then quit with `Ctrl+Q`.
How do I show a function description?
Toggle function-candidate help with `Ctrl+X`.
Are queries saved?
Yes. History is stored locally when confirmed with Enter.
Discussion
No questions or reviews yet.
Related
CLI toolsjnv is an interactive JSON viewer that copies a reviewed filter or its result so a manually checked query can move into a script.
jc converts command output, files and strings into JSON with dedicated parsers for use in scripts and downstream tools.
The CLI selects and changes JSON, YAML and other structured values so agents can transform data with one query language.
The CLI decodes binary formats with jq-style queries so an agent can inspect file structure and extract selected fields.
vi-sql is a terminal SQL client with a built-in MCP server: the agent sees the schema and drafts queries straight in your editor
The SQL client combines terminal database browsing with batch queries for agents using named connections and JSON results.
README in short
Change the history path under `[history]` in `config.toml`. Keybinding settings control query navigation and suggestion selection.