This release is a pre-release and may not be stable for production use.
RealSense Copilot is AI pair programming tool for Intel RealSense cameras in your terminal.
RealSense Copilot (based on Aider) lets you pair program with LLMs, to write and edit code in your local git repository. Start a new project or work with an existing git repo. Realsense works best with GPT-4o & Claude 3.5 Sonnet and can connect to almost any LLM.
Getting started
You can get started quickly like this:
$ python -m pip install -U realsense-copilot
# Change directory into a git repo
cd /to/your/git/repo
# Work with Claude 3.5 Sonnet on your repo
$ export ANTHROPIC_API_KEY=your-key-goes-here
$ realsense demo.py
# Work with GPT-4o on your repo
$ export OPENAI_API_KEY=your-key-goes-here
$ realsense demo.py
See the installation instructions and other documentation for more details.
Features
- Run realsense copilot with the files you want to edit:
realsense <file1> <file2> ... realsense demo.py- Ask for changes:
- Detect a person and their distance. Move the robot to the person. Stop when it reaches their feet.
/run python3 demo.py- If the resulting code, outputs a bug, simply add it to the chat by pressing "y" and Realsense will attempt to fix the bug so you can re /run your app.
- Add new features or test cases.
- Realsense will edit your files to complete your request.
- Realsense automatically git commits changes with a sensible commit message.
- Realsense works with most popular languages: python, javascript, typescript, php, html, css, and more...
- Realsense works best with GPT-4o & Claude 3.5 Sonnet and can connect to almost any LLM.
- Realsense can edit multiple files at once for complex requests.
- Realsense uses a map of your entire git repo, which helps it work well in larger codebases.
- Edit files in your editor while chatting with aider, and it will always use the latest version.
Metadata
Release files for realsense-copilot 0.61.1.dev36
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| realsense_copilot-0.61.1.dev36.tar.gz | 39.1 MB | Without provenance | Details for realsense_copilot-0.61.1.dev36.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| realsense_copilot-0.61.1.dev36-py3-none-any.whl | Python 3 | none | any | Details for realsense_copilot-0.61.1.dev36-py3-none-any.whl |
Total release size: 77.3 MB
Release files / realsense_copilot-0.61.1.dev36.tar.gz
| Download URL | realsense_copilot-0.61.1.dev36.tar.gz |
|---|---|
| Size | 39.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41d82b33f9cb4d6b88aa678d910a81674c66537d7e958d540c7135786f6b2656
|
|
BLAKE2b-256 checksum How to use checksums |
d8b84059f008a866615b9bdbacb38137929a38bbf594507b07fbd78c60bf8432
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.6
|
Release files / realsense_copilot-0.61.1.dev36-py3-none-any.whl
| Download URL | realsense_copilot-0.61.1.dev36-py3-none-any.whl |
|---|---|
| Size | 38.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dcfe7848e2cb49d0eb937c4082d188ec22573aa6df38b156b07b5d85bf21af67
|
|
BLAKE2b-256 checksum How to use checksums |
cc6b639458ccac5dd8ef0c2336ce468e6c02fbad495f59b013b2a8ba3e4641ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.6
|
Security for realsense-copilot 0.61.1.dev36
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.