oy-cli 0.1.1__tar.gz

oy_cli-0.1.1/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+    Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+    stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+    that You distribute, all copyright, patent, trademark, and
+    attribution notices from the Source form of the Work,
+    excluding those notices that do not pertain to any part of
+    the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+    distribution, then any Derivative Works that You distribute must
+    include a readable copy of the attribution notices contained
+    within such NOTICE file, excluding those notices that do not
+    pertain to any part of the Derivative Works, in at least one
+    of the following places: within a NOTICE text file distributed
+    as part of the Derivative Works; within the Source form or
+    documentation, if provided along with the Derivative Works; or,
+    within a display generated by the Derivative Works, if and
+    wherever such third-party notices normally appear. The contents
+    of the NOTICE file are for informational purposes only and
+    do not modify the License. You may add Your own attribution
+    notices within Derivative Works that You distribute, alongside
+    or as an addendum to the NOTICE text from the Work, provided
+    that such additional attribution notices cannot be construed
+    as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "[]"
+replaced with your own identifying information. (Don't include
+the brackets!)  The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

oy_cli-0.1.1/PKG-INFO

@@ -0,0 +1,152 @@
+Metadata-Version: 2.4
+Name: oy-cli
+Version: 0.1.1
+Summary: Tiny local coding CLI with a small tool surface
+Author: oy-cli contributors
+License-Expression: Apache-2.0
+Requires-Python: >=3.14
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: aws-bedrock-token-generator>=1.1.0
+Requires-Dist: diskcache>=5.6.0
+Requires-Dist: httpx>=0.28.1
+Requires-Dist: openai>=1.68.0
+Requires-Dist: rich>=14.1.0
+Requires-Dist: ripgrep>=15.0.0
+Requires-Dist: typer>=0.16.0
+Dynamic: license-file
+
+# oy-cli
+
+Tiny local coding CLI for simple shell interactive code editing and auditing.
+
+`oy` is intentionally small:
+
+- one-shot Typer CLI, not a full TUI
+- decent progress output, not advanced orchestration
+- one main code file as the implementation target
+- intentionally small and auditable
+
+The point is to keep the tool surface boring, explicit, and easy to audit (most existing tools and agents are large/complex or locked to specific providers).
+
+## Design Notes
+
+- follow OWASP-minded secure defaults
+- prefer the grugbrain.dev philosophy: simple, direct, low-magic solutions
+- run inside a locked-down container with limited filesystem, process, and network permissions if you want to use it safely
+- de-scope advanced surfaces like todos, skills, and MCPs (bash is fine, most tools have good CLI interfaces)
+
+## Tool Surface
+
+Initial tools:
+
+- `write`: create new files with `pathlib`
+- `edit`: modify existing files with `pathlib` read/write
+- `patch`: apply unified diffs with `patch` (via subprocess)
+- `list`: list directory contents with `pathlib`
+- `read`: read files with `pathlib`
+- `grep`: search text with `subprocess` + `ripgrep`
+- `glob`: find files and directories with `pathlib.glob`
+- `bash`: run shell commands with `subprocess` via `bash -lc` as a last resort
+- `webfetch`: fetch web content with `httpx`
+
+That is enough for useful local coding work and security audits.
+
+## Known Issues
+
+Some LLMs occasionally emit duplicated tool call arguments. `oy` includes a workaround that detects and recovers from this by hunting for valid JSON around the midpoint of the malformed response.
+
+## Requirements
+
+- Python 3.14+
+- `bash`
+- `patch`
+- `OPENAI_API_KEY` in the environment, OR AWS credentials for automatic Bedrock setup
+
+`ripgrep` is included as a PyPI dependency. If AWS credentials are available (via `AWS_PROFILE`, `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY`, or `~/.aws/credentials`), `oy` will automatically generate Bedrock tokens. If `bash`, `rg`, or `patch` are missing, `oy` exits with install guidance instead of silently falling back.
+
+## Installation
+
+Preferred:
+
+```bash
+uv tool install oy-cli
+```
+
+Alternative:
+
+```bash
+pip install oy-cli
+```
+
+This installs the `oy` command.
+
+## Quick Start using AWS Bedrock (automatic)
+
+If you have AWS credentials configured (via `AWS_PROFILE`, environment variables, or `~/.aws/credentials`), Bedrock is automatically configured:
+
+```bash
+oy models
+oy model moonshotai.kimi-k2.5
+oy "inspect this repository and suggest the smallest safe fix"
+```
+
+To manually export Bedrock tokens (for use in other tools or scripts):
+
+```bash
+eval "$(oy bedrock-token)"
+```
+
+`oy models` uses the OpenAI SDK with `client.models.list()`. `oy model <id>` saves your default model.
+
+With OpenAI-compatible manual creds:
+
+```bash
+export OPENAI_BASE_URL=https://your-endpoint.example/v1
+export OPENAI_API_KEY=...
+oy "summarize this project and list the next changes"
+```
+
+With OpenAI's default API endpoint:
+
+```bash
+export OPENAI_API_KEY=...
+oy "summarize this project and list the next changes"
+```
+
+## Runtime Behavior
+
+- simple CLI flow, no REPL and no TUI
+- simple commands: `oy "..."`, `oy bedrock-token`, `oy models`, `oy model <id>`
+- model chooses from a small set of local tools
+- file operations are scoped to the working directory
+- required tools are checked up front
+- indeterminate progress is shown while waiting on API calls
+- default model/tool budgets are intentionally high for longer build-style runs
+
+## Model Selection
+
+```bash
+oy model
+oy models
+oy model moonshotai.kimi-k2.5
+```
+
+## Security
+
+`oy` can run shell commands and modify files. Treat it like an automation tool with real permissions.
+
+Recommended posture:
+
+- run it in a container or similarly constrained environment
+- mount only the project/dirs you want it to touch
+- avoid broad host access
+- do not expose secrets you do not want shell commands to inherit
+
+## Contributing
+
+Development and release notes live in `CONTRIBUTING.md`.
+
+## License
+
+Licensed under the Apache License 2.0. See `LICENSE`.

oy_cli-0.1.1/README.md

@@ -0,0 +1,134 @@
+# oy-cli
+
+Tiny local coding CLI for simple shell interactive code editing and auditing.
+
+`oy` is intentionally small:
+
+- one-shot Typer CLI, not a full TUI
+- decent progress output, not advanced orchestration
+- one main code file as the implementation target
+- intentionally small and auditable
+
+The point is to keep the tool surface boring, explicit, and easy to audit (most existing tools and agents are large/complex or locked to specific providers).
+
+## Design Notes
+
+- follow OWASP-minded secure defaults
+- prefer the grugbrain.dev philosophy: simple, direct, low-magic solutions
+- run inside a locked-down container with limited filesystem, process, and network permissions if you want to use it safely
+- de-scope advanced surfaces like todos, skills, and MCPs (bash is fine, most tools have good CLI interfaces)
+
+## Tool Surface
+
+Initial tools:
+
+- `write`: create new files with `pathlib`
+- `edit`: modify existing files with `pathlib` read/write
+- `patch`: apply unified diffs with `patch` (via subprocess)
+- `list`: list directory contents with `pathlib`
+- `read`: read files with `pathlib`
+- `grep`: search text with `subprocess` + `ripgrep`
+- `glob`: find files and directories with `pathlib.glob`
+- `bash`: run shell commands with `subprocess` via `bash -lc` as a last resort
+- `webfetch`: fetch web content with `httpx`
+
+That is enough for useful local coding work and security audits.
+
+## Known Issues
+
+Some LLMs occasionally emit duplicated tool call arguments. `oy` includes a workaround that detects and recovers from this by hunting for valid JSON around the midpoint of the malformed response.
+
+## Requirements
+
+- Python 3.14+
+- `bash`
+- `patch`
+- `OPENAI_API_KEY` in the environment, OR AWS credentials for automatic Bedrock setup
+
+`ripgrep` is included as a PyPI dependency. If AWS credentials are available (via `AWS_PROFILE`, `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY`, or `~/.aws/credentials`), `oy` will automatically generate Bedrock tokens. If `bash`, `rg`, or `patch` are missing, `oy` exits with install guidance instead of silently falling back.
+
+## Installation
+
+Preferred:
+
+```bash
+uv tool install oy-cli
+```
+
+Alternative:
+
+```bash
+pip install oy-cli
+```
+
+This installs the `oy` command.
+
+## Quick Start using AWS Bedrock (automatic)
+
+If you have AWS credentials configured (via `AWS_PROFILE`, environment variables, or `~/.aws/credentials`), Bedrock is automatically configured:
+
+```bash
+oy models
+oy model moonshotai.kimi-k2.5
+oy "inspect this repository and suggest the smallest safe fix"
+```
+
+To manually export Bedrock tokens (for use in other tools or scripts):
+
+```bash
+eval "$(oy bedrock-token)"
+```
+
+`oy models` uses the OpenAI SDK with `client.models.list()`. `oy model <id>` saves your default model.
+
+With OpenAI-compatible manual creds:
+
+```bash
+export OPENAI_BASE_URL=https://your-endpoint.example/v1
+export OPENAI_API_KEY=...
+oy "summarize this project and list the next changes"
+```
+
+With OpenAI's default API endpoint:
+
+```bash
+export OPENAI_API_KEY=...
+oy "summarize this project and list the next changes"
+```
+
+## Runtime Behavior
+
+- simple CLI flow, no REPL and no TUI
+- simple commands: `oy "..."`, `oy bedrock-token`, `oy models`, `oy model <id>`
+- model chooses from a small set of local tools
+- file operations are scoped to the working directory
+- required tools are checked up front
+- indeterminate progress is shown while waiting on API calls
+- default model/tool budgets are intentionally high for longer build-style runs
+
+## Model Selection
+
+```bash
+oy model
+oy models
+oy model moonshotai.kimi-k2.5
+```
+
+## Security
+
+`oy` can run shell commands and modify files. Treat it like an automation tool with real permissions.
+
+Recommended posture:
+
+- run it in a container or similarly constrained environment
+- mount only the project/dirs you want it to touch
+- avoid broad host access
+- do not expose secrets you do not want shell commands to inherit
+
+## Contributing
+
+Development and release notes live in `CONTRIBUTING.md`.
+
+## License
+
+Licensed under the Apache License 2.0. See `LICENSE`.

oy_cli-0.1.1/oy_cli.egg-info/PKG-INFO

@@ -0,0 +1,152 @@
+Metadata-Version: 2.4
+Name: oy-cli
+Version: 0.1.1
+Summary: Tiny local coding CLI with a small tool surface
+Author: oy-cli contributors
+License-Expression: Apache-2.0
+Requires-Python: >=3.14
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: aws-bedrock-token-generator>=1.1.0
+Requires-Dist: diskcache>=5.6.0
+Requires-Dist: httpx>=0.28.1
+Requires-Dist: openai>=1.68.0
+Requires-Dist: rich>=14.1.0
+Requires-Dist: ripgrep>=15.0.0
+Requires-Dist: typer>=0.16.0
+Dynamic: license-file
+
+# oy-cli
+
+Tiny local coding CLI for simple shell interactive code editing and auditing.
+
+`oy` is intentionally small:
+
+- one-shot Typer CLI, not a full TUI
+- decent progress output, not advanced orchestration
+- one main code file as the implementation target
+- intentionally small and auditable
+
+The point is to keep the tool surface boring, explicit, and easy to audit (most existing tools and agents are large/complex or locked to specific providers).
+
+## Design Notes
+
+- follow OWASP-minded secure defaults
+- prefer the grugbrain.dev philosophy: simple, direct, low-magic solutions
+- run inside a locked-down container with limited filesystem, process, and network permissions if you want to use it safely
+- de-scope advanced surfaces like todos, skills, and MCPs (bash is fine, most tools have good CLI interfaces)
+
+## Tool Surface
+
+Initial tools:
+
+- `write`: create new files with `pathlib`
+- `edit`: modify existing files with `pathlib` read/write
+- `patch`: apply unified diffs with `patch` (via subprocess)
+- `list`: list directory contents with `pathlib`
+- `read`: read files with `pathlib`
+- `grep`: search text with `subprocess` + `ripgrep`
+- `glob`: find files and directories with `pathlib.glob`
+- `bash`: run shell commands with `subprocess` via `bash -lc` as a last resort
+- `webfetch`: fetch web content with `httpx`
+
+That is enough for useful local coding work and security audits.
+
+## Known Issues
+
+Some LLMs occasionally emit duplicated tool call arguments. `oy` includes a workaround that detects and recovers from this by hunting for valid JSON around the midpoint of the malformed response.
+
+## Requirements
+
+- Python 3.14+
+- `bash`
+- `patch`
+- `OPENAI_API_KEY` in the environment, OR AWS credentials for automatic Bedrock setup
+
+`ripgrep` is included as a PyPI dependency. If AWS credentials are available (via `AWS_PROFILE`, `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY`, or `~/.aws/credentials`), `oy` will automatically generate Bedrock tokens. If `bash`, `rg`, or `patch` are missing, `oy` exits with install guidance instead of silently falling back.
+
+## Installation
+
+Preferred:
+
+```bash
+uv tool install oy-cli
+```
+
+Alternative:
+
+```bash
+pip install oy-cli
+```
+
+This installs the `oy` command.
+
+## Quick Start using AWS Bedrock (automatic)
+
+If you have AWS credentials configured (via `AWS_PROFILE`, environment variables, or `~/.aws/credentials`), Bedrock is automatically configured:
+
+```bash
+oy models
+oy model moonshotai.kimi-k2.5
+oy "inspect this repository and suggest the smallest safe fix"
+```
+
+To manually export Bedrock tokens (for use in other tools or scripts):
+
+```bash
+eval "$(oy bedrock-token)"
+```
+
+`oy models` uses the OpenAI SDK with `client.models.list()`. `oy model <id>` saves your default model.
+
+With OpenAI-compatible manual creds:
+
+```bash
+export OPENAI_BASE_URL=https://your-endpoint.example/v1
+export OPENAI_API_KEY=...
+oy "summarize this project and list the next changes"
+```
+
+With OpenAI's default API endpoint:
+
+```bash
+export OPENAI_API_KEY=...
+oy "summarize this project and list the next changes"
+```
+
+## Runtime Behavior
+
+- simple CLI flow, no REPL and no TUI
+- simple commands: `oy "..."`, `oy bedrock-token`, `oy models`, `oy model <id>`
+- model chooses from a small set of local tools
+- file operations are scoped to the working directory
+- required tools are checked up front
+- indeterminate progress is shown while waiting on API calls
+- default model/tool budgets are intentionally high for longer build-style runs
+
+## Model Selection
+
+```bash
+oy model
+oy models
+oy model moonshotai.kimi-k2.5
+```
+
+## Security
+
+`oy` can run shell commands and modify files. Treat it like an automation tool with real permissions.
+
+Recommended posture:
+
+- run it in a container or similarly constrained environment
+- mount only the project/dirs you want it to touch
+- avoid broad host access
+- do not expose secrets you do not want shell commands to inherit
+
+## Contributing
+
+Development and release notes live in `CONTRIBUTING.md`.
+
+## License
+
+Licensed under the Apache License 2.0. See `LICENSE`.

oy_cli-0.1.1/oy_cli.egg-info/SOURCES.txt

@@ -0,0 +1,10 @@
+LICENSE
+README.md
+oy_cli.py
+pyproject.toml
+oy_cli.egg-info/PKG-INFO
+oy_cli.egg-info/SOURCES.txt
+oy_cli.egg-info/dependency_links.txt
+oy_cli.egg-info/entry_points.txt
+oy_cli.egg-info/requires.txt
+oy_cli.egg-info/top_level.txt

oy_cli-0.1.1/oy_cli.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

oy_cli-0.1.1/oy_cli.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+oy = oy_cli:main

oy_cli-0.1.1/oy_cli.egg-info/requires.txt

@@ -0,0 +1,7 @@
+aws-bedrock-token-generator>=1.1.0
+diskcache>=5.6.0
+httpx>=0.28.1
+openai>=1.68.0
+rich>=14.1.0
+ripgrep>=15.0.0
+typer>=0.16.0

oy_cli-0.1.1/oy_cli.egg-info/top_level.txt

@@ -0,0 +1 @@
+oy_cli