Directories
¶
| Path | Synopsis |
|---|---|
|
Package bench measures what it costs an agent to answer a question with jade's tools versus with ordinary shell and file tools.
|
Package bench measures what it costs an agent to answer a question with jade's tools versus with ordinary shell and file tools. |
|
agent
Package agent runs the release plan's external benchmark: a real agent (Claude Code headless) solving real tasks in a repository Jade was not built in, once per arm — shell tools only, Jade only, and Jade plus shell.
|
Package agent runs the release plan's external benchmark: a real agent (Claude Code headless) solving real tasks in a repository Jade was not built in, once per arm — shell tools only, Jade only, and Jade plus shell. |
|
Package commands implements jade's repo command registry: a small, version-controlled list of named shell commands a project declares once and replays by name thereafter.
|
Package commands implements jade's repo command registry: a small, version-controlled list of named shell commands a project declares once and replays by name thereafter. |
|
Package deps finds the source of a project's dependencies: the crate in the Cargo registry, the module in the Go module cache, the package in node_modules or in the repository's virtual environment.
|
Package deps finds the source of a project's dependencies: the crate in the Cargo registry, the module in the Go module cache, the package in node_modules or in the repository's virtual environment. |
|
Package lsp speaks the Language Server Protocol to real language servers.
|
Package lsp speaks the Language Server Protocol to real language servers. |
|
Package pathguard keeps every file operation inside the workspace.
|
Package pathguard keeps every file operation inside the workspace. |
|
Package project reads .jade/project.json: a repository's own statement of how Jade should build, check and test it, committed next to the code the way an editor keeps its settings in .vscode/.
|
Package project reads .jade/project.json: a repository's own statement of how Jade should build, check and test it, committed next to the code the way an editor keeps its settings in .vscode/. |
|
Package render turns jade's typed responses into plain text for the MCP transport.
|
Package render turns jade's typed responses into plain text for the MCP transport. |
|
Package setup installs what Jade can use but does not ship — language servers today, plugins later — behind `jade-mcp install`.
|
Package setup installs what Jade can use but does not ship — language servers today, plugins later — behind `jade-mcp install`. |
|
Package telemetry records how jade's tools are actually used.
|
Package telemetry records how jade's tools are actually used. |
|
Package textutil holds text-shaping helpers shared by jade's response builders.
|
Package textutil holds text-shaping helpers shared by jade's response builders. |
|
Package toolchain locates external developer tools jade shells out to.
|
Package toolchain locates external developer tools jade shells out to. |
|
transport
|
|
|
Package update tells a user that a newer Jade release exists without getting in their way.
|
Package update tells a user that a newer Jade release exists without getting in their way. |
|
Package writes is the one way Jade changes a file in the workspace (release plan 0.0.7, "One write path").
|
Package writes is the one way Jade changes a file in the workspace (release plan 0.0.7, "One write path"). |
Click to show internal directories.
Click to hide internal directories.