From 6f37c432cf2fa7744edd057e85f366c0ca2cceac Mon Sep 17 00:00:00 2001 From: rxgrant <6995442+rxgrant@users.noreply.github.com> Date: Sun, 31 May 2026 12:31:46 +0000 Subject: [PATCH 1/6] Introduce jp-tools and RFDs in readme. README did not mention how to install jp-tools. While the JP project does not commit to delivering jp-tools in current form, the binary is needed for understanding configuration and development until replaced by other options. --- README.md | 46 +++++++++++++++++++++++++++++++++++++--------- 1 file changed, 37 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 92f814d3..92976737 100644 --- a/README.md +++ b/README.md @@ -16,21 +16,30 @@ Visit [jp.computer] to learn more. ## Philosophy -JP is built to be: **[provider-agnostic][1]**, because your workflow shouldn't -be coupled to any single LLM backend; **[private and secure by default][2]**, -with no implicit network access or silent tool execution; a **[proper Unix -citizen][3]** as a single static binary that composes with pipes, respects your -shell, and stays out of your way; **[extensible][4]** through sandboxed plugins; -**[configurable][5]** where it matters; and finally, **[open-source and -independent][6]**, holding no allegiance to any LLM provider, funded without the -enshittification of VC money, just striving to be great — thanks to and for its -users. +JP is built to be: **[provider-agnostic][1]**, + because your workflow shouldn't be coupled to any single LLM backend; +**[private and secure by default][2]**, + with no implicit network access or silent tool execution; +a **[proper Unix citizen][3]** + as a single static binary that composes with pipes, respects your shell, and stays out of your way; +**[extensible][4]** through sandboxed plugins; +**[configurable][5]** where it matters; +and finally, **[open-source and independent][6]**, + holding no allegiance to any LLM provider, + funded without the enshittification of VC money, and + just striving to be great — thanks to and for its users. When you adapt your programming tooling and workflow to JP, you are ensuring that you will have access to all of the frontier models, all of the local-first open source inference runtimes, and all of the major inference aggregation services. +## Architecture / Tool Calling + +JP's architecture routes to explicitly configured helper binaries as its list of tools the LLM may call upon. +The current self-dev configuration uses a sub-project, `jp-tools`, (invoked through the justfile) to satisfy all the binaries required for understanding code, modifying files, interacting with version control, generating RFDs covering new features, filing Github issues, and making selected shell operations. +JP does not need any tools to operate, but you will want at least a subset of the `jp-tools` colletion for your valid developer configuration. + ## Getting Started JP is in active development. @@ -69,6 +78,13 @@ List and select conversations: % jp conversation use ``` +Install `jp-tools` from a local clone: + +```sh +git clone https://github.com/dcdpr/jp.git +cargo install --locked --path jp/.config/jp/tools +``` + Configure your JP workspace: ```sh @@ -89,3 +105,15 @@ See what else you can do: [6]: docs/README/open-source.md [jp.computer]: https://jp.computer/ [reach out to us]: https://jp.computer/contact + +## Roadmap + +JP's direction is planned in the open through Requests for Discussion (RFDs), +short design documents that precede any significant change. +The RFD index ([on the web][rfds via web] / [in this repo][rfds local]) +is the canonical, always-current view of what's proposed, in progress, and decided. +If you want to understand where JP is headed or influence where it goes next, +start there. + +[rfds via Web]: https://jp.computer/rfd/ +[rfds local]: docs/rfd/ From 6eb8f4b509c3375738d6e860903407c3b1fe987e Mon Sep 17 00:00:00 2001 From: rxgrant <6995442+rxgrant@users.noreply.github.com> Date: Sun, 31 May 2026 12:43:50 +0000 Subject: [PATCH 2/6] run comfort --- README.md | 63 +++++++++++++++++++++---------------------------------- 1 file changed, 24 insertions(+), 39 deletions(-) diff --git a/README.md b/README.md index 92976737..39e254d6 100644 --- a/README.md +++ b/README.md @@ -5,40 +5,39 @@ > Built to integrate into your existing workflows, providing a secure, powerful > and flexible pair-programming experience with LLMs. -Visit [jp.computer] to learn more. +Visit [jp.computer](https://jp.computer/) to learn more. > [!NOTE] > This project is in active development. > Expect breaking changes. > What is documented here is subject to change and may not be up-to-date. > Please consult the [installation instructions](#getting-started) to get -> started, and [reach out to us] if you need any assistance, or have feedback. +> started, and [reach out to us](https://jp.computer/contact) if you need any +> assistance, or have feedback. ## Philosophy -JP is built to be: **[provider-agnostic][1]**, - because your workflow shouldn't be coupled to any single LLM backend; -**[private and secure by default][2]**, - with no implicit network access or silent tool execution; -a **[proper Unix citizen][3]** - as a single static binary that composes with pipes, respects your shell, and stays out of your way; -**[extensible][4]** through sandboxed plugins; -**[configurable][5]** where it matters; -and finally, **[open-source and independent][6]**, - holding no allegiance to any LLM provider, - funded without the enshittification of VC money, and - just striving to be great — thanks to and for its users. +JP is built to be: **[provider-agnostic][1]**, because your workflow shouldn't +be coupled to any single LLM backend; **[private and secure by default][2]**, +with no implicit network access or silent tool execution; a **[proper Unix +citizen][3]** as a single static binary that composes with pipes, respects your +shell, and stays out of your way; **[extensible][4]** through sandboxed plugins; +**[configurable][5]** where it matters; and finally, **[open-source and +independent][6]**, holding no allegiance to any LLM provider, funded without the +enshittification of VC money, just striving to be great — thanks to and for its +users. When you adapt your programming tooling and workflow to JP, you are ensuring that you will have access to all of the frontier models, all of the local-first open source inference runtimes, and all of the major inference aggregation services. -## Architecture / Tool Calling - -JP's architecture routes to explicitly configured helper binaries as its list of tools the LLM may call upon. -The current self-dev configuration uses a sub-project, `jp-tools`, (invoked through the justfile) to satisfy all the binaries required for understanding code, modifying files, interacting with version control, generating RFDs covering new features, filing Github issues, and making selected shell operations. -JP does not need any tools to operate, but you will want at least a subset of the `jp-tools` colletion for your valid developer configuration. +[1]: docs/README/providers.md +[2]: docs/README/privacy-and-security.md +[3]: docs/README/workflow-integration.md +[4]: docs/README/extensibility.md +[5]: docs/README/configuration.md +[6]: docs/README/open-source.md ## Getting Started @@ -46,7 +45,7 @@ JP is in active development. Install from source: ```sh -% cargo install --locked --git https://github.com/dcdpr/jp.git jp_cli +% cargo install --locked --git https://github.com/dcdpr/jp.git ``` Initiate a new workspace in an existing directory: @@ -78,13 +77,6 @@ List and select conversations: % jp conversation use ``` -Install `jp-tools` from a local clone: - -```sh -git clone https://github.com/dcdpr/jp.git -cargo install --locked --path jp/.config/jp/tools -``` - Configure your JP workspace: ```sh @@ -97,23 +89,16 @@ See what else you can do: % jp help ``` -[1]: docs/README/providers.md -[2]: docs/README/privacy-and-security.md -[3]: docs/README/workflow-integration.md -[4]: docs/README/extensibility.md -[5]: docs/README/configuration.md -[6]: docs/README/open-source.md -[jp.computer]: https://jp.computer/ -[reach out to us]: https://jp.computer/contact - ## Roadmap JP's direction is planned in the open through Requests for Discussion (RFDs), short design documents that precede any significant change. -The RFD index ([on the web][rfds via web] / [in this repo][rfds local]) -is the canonical, always-current view of what's proposed, in progress, and decided. +Rather than mirror a roadmap here that would drift out of date, we keep it where +the work actually happens: the RFD index ([on the web][rfds via web] / [in this +repo][rfds local]) is the canonical, always-current view of what's proposed, in +progress, and decided. If you want to understand where JP is headed or influence where it goes next, start there. -[rfds via Web]: https://jp.computer/rfd/ +[rfds via web]: https://jp.computer/rfd/ [rfds local]: docs/rfd/ From e8bbfe031b11cceed0dbc75b5c75af04234a839c Mon Sep 17 00:00:00 2001 From: rxgrant <6995442+rxgrant@users.noreply.github.com> Date: Sun, 31 May 2026 12:56:23 +0000 Subject: [PATCH 3/6] run comfort on intended changes --- README.md | 63 ++++++++++++++++++++++++++++++++++--------------------- 1 file changed, 39 insertions(+), 24 deletions(-) diff --git a/README.md b/README.md index 39e254d6..92976737 100644 --- a/README.md +++ b/README.md @@ -5,39 +5,40 @@ > Built to integrate into your existing workflows, providing a secure, powerful > and flexible pair-programming experience with LLMs. -Visit [jp.computer](https://jp.computer/) to learn more. +Visit [jp.computer] to learn more. > [!NOTE] > This project is in active development. > Expect breaking changes. > What is documented here is subject to change and may not be up-to-date. > Please consult the [installation instructions](#getting-started) to get -> started, and [reach out to us](https://jp.computer/contact) if you need any -> assistance, or have feedback. +> started, and [reach out to us] if you need any assistance, or have feedback. ## Philosophy -JP is built to be: **[provider-agnostic][1]**, because your workflow shouldn't -be coupled to any single LLM backend; **[private and secure by default][2]**, -with no implicit network access or silent tool execution; a **[proper Unix -citizen][3]** as a single static binary that composes with pipes, respects your -shell, and stays out of your way; **[extensible][4]** through sandboxed plugins; -**[configurable][5]** where it matters; and finally, **[open-source and -independent][6]**, holding no allegiance to any LLM provider, funded without the -enshittification of VC money, just striving to be great — thanks to and for its -users. +JP is built to be: **[provider-agnostic][1]**, + because your workflow shouldn't be coupled to any single LLM backend; +**[private and secure by default][2]**, + with no implicit network access or silent tool execution; +a **[proper Unix citizen][3]** + as a single static binary that composes with pipes, respects your shell, and stays out of your way; +**[extensible][4]** through sandboxed plugins; +**[configurable][5]** where it matters; +and finally, **[open-source and independent][6]**, + holding no allegiance to any LLM provider, + funded without the enshittification of VC money, and + just striving to be great — thanks to and for its users. When you adapt your programming tooling and workflow to JP, you are ensuring that you will have access to all of the frontier models, all of the local-first open source inference runtimes, and all of the major inference aggregation services. -[1]: docs/README/providers.md -[2]: docs/README/privacy-and-security.md -[3]: docs/README/workflow-integration.md -[4]: docs/README/extensibility.md -[5]: docs/README/configuration.md -[6]: docs/README/open-source.md +## Architecture / Tool Calling + +JP's architecture routes to explicitly configured helper binaries as its list of tools the LLM may call upon. +The current self-dev configuration uses a sub-project, `jp-tools`, (invoked through the justfile) to satisfy all the binaries required for understanding code, modifying files, interacting with version control, generating RFDs covering new features, filing Github issues, and making selected shell operations. +JP does not need any tools to operate, but you will want at least a subset of the `jp-tools` colletion for your valid developer configuration. ## Getting Started @@ -45,7 +46,7 @@ JP is in active development. Install from source: ```sh -% cargo install --locked --git https://github.com/dcdpr/jp.git +% cargo install --locked --git https://github.com/dcdpr/jp.git jp_cli ``` Initiate a new workspace in an existing directory: @@ -77,6 +78,13 @@ List and select conversations: % jp conversation use ``` +Install `jp-tools` from a local clone: + +```sh +git clone https://github.com/dcdpr/jp.git +cargo install --locked --path jp/.config/jp/tools +``` + Configure your JP workspace: ```sh @@ -89,16 +97,23 @@ See what else you can do: % jp help ``` +[1]: docs/README/providers.md +[2]: docs/README/privacy-and-security.md +[3]: docs/README/workflow-integration.md +[4]: docs/README/extensibility.md +[5]: docs/README/configuration.md +[6]: docs/README/open-source.md +[jp.computer]: https://jp.computer/ +[reach out to us]: https://jp.computer/contact + ## Roadmap JP's direction is planned in the open through Requests for Discussion (RFDs), short design documents that precede any significant change. -Rather than mirror a roadmap here that would drift out of date, we keep it where -the work actually happens: the RFD index ([on the web][rfds via web] / [in this -repo][rfds local]) is the canonical, always-current view of what's proposed, in -progress, and decided. +The RFD index ([on the web][rfds via web] / [in this repo][rfds local]) +is the canonical, always-current view of what's proposed, in progress, and decided. If you want to understand where JP is headed or influence where it goes next, start there. -[rfds via web]: https://jp.computer/rfd/ +[rfds via Web]: https://jp.computer/rfd/ [rfds local]: docs/rfd/ From 65e4384dca9d944b6a3d81814a20895572cf7204 Mon Sep 17 00:00:00 2001 From: rxgrant <6995442+rxgrant@users.noreply.github.com> Date: Sun, 31 May 2026 13:03:12 +0000 Subject: [PATCH 4/6] keep trying --- README.md | 56 +++++++++++++++++++++++++++++-------------------------- 1 file changed, 30 insertions(+), 26 deletions(-) diff --git a/README.md b/README.md index 92976737..f142bf4d 100644 --- a/README.md +++ b/README.md @@ -14,31 +14,44 @@ Visit [jp.computer] to learn more. > Please consult the [installation instructions](#getting-started) to get > started, and [reach out to us] if you need any assistance, or have feedback. +[jp.computer]: https://jp.computer/ +[reach out to us]: https://jp.computer/contact + ## Philosophy -JP is built to be: **[provider-agnostic][1]**, - because your workflow shouldn't be coupled to any single LLM backend; -**[private and secure by default][2]**, - with no implicit network access or silent tool execution; -a **[proper Unix citizen][3]** - as a single static binary that composes with pipes, respects your shell, and stays out of your way; -**[extensible][4]** through sandboxed plugins; -**[configurable][5]** where it matters; -and finally, **[open-source and independent][6]**, - holding no allegiance to any LLM provider, - funded without the enshittification of VC money, and - just striving to be great — thanks to and for its users. +JP is built to be: **[provider-agnostic][1]**, because your workflow shouldn't +be coupled to any single LLM backend; **[private and secure by default][2]**, +with no implicit network access or silent tool execution; a **[proper Unix +citizen][3]** as a single static binary that composes with pipes, respects your +shell, and stays out of your way; **[extensible][4]** through sandboxed plugins; +**[configurable][5]** where it matters; and finally, **[open-source and +independent][6]**, holding no allegiance to any LLM provider, funded without the +enshittification of VC money, and just striving to be great — thanks to and for +its users. When you adapt your programming tooling and workflow to JP, you are ensuring that you will have access to all of the frontier models, all of the local-first open source inference runtimes, and all of the major inference aggregation services. +[1]: docs/README/providers.md +[2]: docs/README/privacy-and-security.md +[3]: docs/README/workflow-integration.md +[4]: docs/README/extensibility.md +[5]: docs/README/configuration.md +[6]: docs/README/open-source.md + ## Architecture / Tool Calling -JP's architecture routes to explicitly configured helper binaries as its list of tools the LLM may call upon. -The current self-dev configuration uses a sub-project, `jp-tools`, (invoked through the justfile) to satisfy all the binaries required for understanding code, modifying files, interacting with version control, generating RFDs covering new features, filing Github issues, and making selected shell operations. -JP does not need any tools to operate, but you will want at least a subset of the `jp-tools` colletion for your valid developer configuration. +JP's architecture routes to explicitly configured helper binaries as its list of +tools the LLM may call upon. +The current self-dev configuration uses a sub-project, `jp-tools`, (invoked +through the justfile) to satisfy all the binaries required for understanding +code, modifying files, interacting with version control, generating RFDs +covering new features, filing Github issues, and making selected shell +operations. +JP does not need any tools to operate, but you will want at least a subset of +the `jp-tools` colletion for your valid developer configuration. ## Getting Started @@ -97,21 +110,12 @@ See what else you can do: % jp help ``` -[1]: docs/README/providers.md -[2]: docs/README/privacy-and-security.md -[3]: docs/README/workflow-integration.md -[4]: docs/README/extensibility.md -[5]: docs/README/configuration.md -[6]: docs/README/open-source.md -[jp.computer]: https://jp.computer/ -[reach out to us]: https://jp.computer/contact - ## Roadmap JP's direction is planned in the open through Requests for Discussion (RFDs), short design documents that precede any significant change. -The RFD index ([on the web][rfds via web] / [in this repo][rfds local]) -is the canonical, always-current view of what's proposed, in progress, and decided. +The RFD index ([on the web][rfds via web] / [in this repo][rfds local]) is the +canonical, always-current view of what's proposed, in progress, and decided. If you want to understand where JP is headed or influence where it goes next, start there. From 6ed2c75aa194161a4842b0afa9770cb11020dc86 Mon Sep 17 00:00:00 2001 From: rxgrant <6995442+rxgrant@users.noreply.github.com> Date: Sun, 31 May 2026 13:06:03 +0000 Subject: [PATCH 5/6] preserve links at bottom pattern --- README.md | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index f142bf4d..0e240228 100644 --- a/README.md +++ b/README.md @@ -14,9 +14,6 @@ Visit [jp.computer] to learn more. > Please consult the [installation instructions](#getting-started) to get > started, and [reach out to us] if you need any assistance, or have feedback. -[jp.computer]: https://jp.computer/ -[reach out to us]: https://jp.computer/contact - ## Philosophy JP is built to be: **[provider-agnostic][1]**, because your workflow shouldn't @@ -34,13 +31,6 @@ that you will have access to all of the frontier models, all of the local-first open source inference runtimes, and all of the major inference aggregation services. -[1]: docs/README/providers.md -[2]: docs/README/privacy-and-security.md -[3]: docs/README/workflow-integration.md -[4]: docs/README/extensibility.md -[5]: docs/README/configuration.md -[6]: docs/README/open-source.md - ## Architecture / Tool Calling JP's architecture routes to explicitly configured helper binaries as its list of @@ -119,5 +109,13 @@ canonical, always-current view of what's proposed, in progress, and decided. If you want to understand where JP is headed or influence where it goes next, start there. +[1]: docs/README/providers.md +[2]: docs/README/privacy-and-security.md +[3]: docs/README/workflow-integration.md +[4]: docs/README/extensibility.md +[5]: docs/README/configuration.md +[6]: docs/README/open-source.md +[jp.computer]: https://jp.computer/ +[reach out to us]: https://jp.computer/contact [rfds via Web]: https://jp.computer/rfd/ [rfds local]: docs/rfd/ From d9e74d2da2c65a5cef98ad0db39b8c924b44fdf9 Mon Sep 17 00:00:00 2001 From: rxgrant <6995442+rxgrant@users.noreply.github.com> Date: Sun, 31 May 2026 13:09:22 +0000 Subject: [PATCH 6/6] keep trying --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0e240228..30ab32d6 100644 --- a/README.md +++ b/README.md @@ -41,7 +41,7 @@ code, modifying files, interacting with version control, generating RFDs covering new features, filing Github issues, and making selected shell operations. JP does not need any tools to operate, but you will want at least a subset of -the `jp-tools` colletion for your valid developer configuration. +the `jp-tools` collection for your valid developer configuration. ## Getting Started