execdiff 0.0.5__tar.gz → 0.0.7__tar.gz

{execdiff-0.0.5 → execdiff-0.0.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: execdiff
-Version: 0.0.5
+Version: 0.0.7
 Summary: Passive execution tracing for file and package changes.
 Author-email: Anup Moncy <n93181165@gmail.com>
 License:                                  Apache License
@@ -217,61 +217,56 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Dynamic: license-file
 
-# ExecDiff
+# Monitor AI Tool Workspace Changes
 
-See what AI-generated code will change before running it.
+AI coding tools like GitHub Copilot, Cursor, Replit AI, and agentic workflows install dependencies, modify configurations, and run setup commands in a project workspace.
 
----
+## Tracking Changes Beyond Git
 
-## Problem
+If GitHub Copilot implements a feature like API integration, it may:
 
-AI coding tools and agents today can:
+- Generate code.
+- Install libraries via the terminal.
+- Modify configuration files.
+- Create output files.
 
-- install dependencies  
-- create files  
-- modify configs  
-- run migrations  
-- delete project files  
+But when something breaks after execution, Git only shows code changes — not:
 
-All automatically.
+- newly installed packages
+- runtime-created files
+- deleted files
+- config updates done during execution
 
-When something breaks after execution, tools cannot answer:
+So it’s hard to tell what actually changed after an AI copilot action.
 
-> What exactly changed because of this action?
+Here’s how to capture everything automatically using VS Code (or any IDE with a terminal).
 
-Git tracks source code changes —  
-but it does **not** track execution side effects like:
+---
 
-- newly installed Python packages  
-- runtime-created files  
-- deleted files  
-- modified configs  
+## Step 1: Open Your Project in Your IDE
 
-So tools often fall back to:
+Open your project folder in VS Code (or any IDE).
 
-> regenerate and try again
+Now open the integrated terminal: **Terminal → New Terminal**
 
 ---
 
-## Solution
-
-ExecDiff allows tools to run AI-generated code and observe:
+## Step 2 (Optional): Create a Project-Level Python Environment
 
-> what changed in the workspace because of that execution
+If you want installs isolated to this project:
 
-It detects:
-
-- files created  
-- files modified  
-- files deleted  
-- Python packages installed  
+```bash
+python3 -m venv venv
+source venv/bin/activate
+```
 
-inside a specific workspace  
-during a specific execution window.
+Otherwise, you can skip this step.
 
 ---
 
-## Installation
+## Step 3: Install ExecDiff from Terminal
+
+Run this inside the terminal:
 
 ```bash
 pip install execdiff
@@ -279,134 +274,106 @@ pip install execdiff
 
 ---
 
-## Example
+## Step 4: Start Tracing Before Using Your AI Copilot
 
-Create a test script:
+Create a new Python file in your project: `trace_ai.py` with the code below
 
 ```python
 import execdiff
-import json
-import os
+import time
+
+print("\nStarting AI action trace...\n")
+execdiff.start_action_trace(workspace=".")
 
-os.makedirs("workspace", exist_ok=True)
+input("Tracing is ON. Use your AI copilot now.\n\nPress ENTER here once it's done...")
 
-diff = execdiff.run_traced(
-    "touch workspace/test.txt",
-    workspace="workspace"
-)
+print("\nStopping trace...\n")
+execdiff.stop_action_trace()
 
-print(json.dumps(diff, indent=2))
+print("\nSummary of last AI action:\n")
+print(execdiff.last_action_summary())
 ```
 
-Run:
+Now run this from the terminal:
 
 ```bash
-python test.py
+python trace_ai.py
 ```
 
+Tracing has now started and you’ll see:
+
+```
+Starting AI action trace...
+
+Tracing is ON. Use your AI copilot now.
+Press ENTER here once it's done...
+```
+
+Leave this terminal running.
+
 ---
 
-## API Reference
+## Step 5: Use Your AI Copilot Normally
 
-### `start_action_trace(workspace=".")`
+Now continue development normally inside your IDE using any AI copilot.
 
-Start tracing a workspace for changes. Must be called before any operations.
+For example, ask:
 
-```python
-import execdiff
+> “Create a new feature for loading hello world into a pandas data frame and displaying it. Install the required libraries”
 
-execdiff.start_action_trace(workspace="./my_workspace")
-# ... your code that makes changes ...
-```
+Your copilot may now:
 
-### `stop_action_trace()`
+- generate new code
+- install dependencies
+- modify config files
+- create or delete files
 
-Stop tracing and return a diff of all changes detected. Automatically logs to `.execdiff/logs/actions.jsonl`.
+inside your project workspace.
 
-```python
-diff = execdiff.stop_action_trace()
-# Returns: {"files": {...}, "packages": {...}}
-```
+You don’t need to change anything in your workflow.
 
-### `last_action_summary(workspace=".")`
+Just let your AI copilot run whatever setup it needs internally.
 
-Get a human-readable summary of the last action trace without parsing JSON.
+---
 
-```python
-summary = execdiff.last_action_summary(workspace=".")
-print(summary)
-```
+## Step 6: Stop the Trace
 
-Output example:
-```
-Last AI Action:
+Once it’s done, come back to terminal and press Enter
+
+You’ll get:
 
+```
+Summary of last AI action:
 Created:
 - output.txt
 - data.json
-
+Modified:
+- settings.py
 Installed:
 - requests==2.32.0
 ```
 
-### `snapshot_workspace_state(workspace)`
+This includes:
 
-Take a full metadata snapshot of the workspace (files with mtime/size, installed packages).
+- filesystem changes
+- installed packages
+- deleted files
+- execution-time config updates
 
-```python
-state = execdiff.snapshot_workspace_state(workspace=".")
-# Returns: {"files": {...}, "packages": {...}}
-```
+All changes made during runtime.
 
 ---
 
-## Output Format
-
-### Diff Structure
-
-```json
-{
-  "files": {
-    "created": [{"path": "file.txt", "mtime": 123.45, "size": 1024}],
-    "modified": [{"path": "config.yaml", "before_mtime": 123, "after_mtime": 124, "before_size": 512, "after_size": 1024}],
-    "deleted": [{"path": "old_file.txt", "mtime": 123.45, "size": 256}]
-  },
-  "packages": {
-    "installed": [{"name": "requests", "version": "2.32.0"}],
-    "upgraded": [{"name": "django", "before_version": "3.2", "after_version": "4.0"}],
-    "removed": [{"name": "deprecated_lib", "version": "1.0"}]
-  }
-}
-```
-
-### Log File
+## Automatic Logs
 
-All action traces are automatically persisted to `.execdiff/logs/actions.jsonl`:
+Each AI-driven action is also stored inside:
 
-```json
-{
-  "timestamp": "2026-02-18T18:19:35.872838",
-  "workspace": "/path/to/workspace",
-  "diff": {...}
-}
+```
+.execdiff/logs/actions.jsonl
 ```
 
----
-
-## Use Cases
-
-ExecDiff can help AI coding tools:
-
-- preview changes before applying generated code  
-- detect unintended file or dependency changes  
-- explain execution impact to users  
-- debug failed automation  
-- build undo / rollback systems  
+Now get a running history of what changed in your project after every AI action.
 
 ---
 
-## License
-
-MIT
-
-````
+You can now continue using any AI copilot inside VS Code (or any IDE) normally while ExecDiff captures everything it changes behind the scenes.

execdiff-0.0.7/README.md

@@ -0,0 +1,160 @@
+# Monitor AI Tool Workspace Changes
+
+AI coding tools like GitHub Copilot, Cursor, Replit AI, and agentic workflows install dependencies, modify configurations, and run setup commands in a project workspace.
+
+## Tracking Changes Beyond Git
+
+If GitHub Copilot implements a feature like API integration, it may:
+
+- Generate code.
+- Install libraries via the terminal.
+- Modify configuration files.
+- Create output files.
+
+But when something breaks after execution, Git only shows code changes — not:
+
+- newly installed packages
+- runtime-created files
+- deleted files
+- config updates done during execution
+
+So it’s hard to tell what actually changed after an AI copilot action.
+
+Here’s how to capture everything automatically using VS Code (or any IDE with a terminal).
+
+---
+
+## Step 1: Open Your Project in Your IDE
+
+Open your project folder in VS Code (or any IDE).
+
+Now open the integrated terminal: **Terminal → New Terminal**
+
+---
+
+## Step 2 (Optional): Create a Project-Level Python Environment
+
+If you want installs isolated to this project:
+
+```bash
+python3 -m venv venv
+source venv/bin/activate
+```
+
+Otherwise, you can skip this step.
+
+---
+
+## Step 3: Install ExecDiff from Terminal
+
+Run this inside the terminal:
+
+```bash
+pip install execdiff
+```
+
+---
+
+## Step 4: Start Tracing Before Using Your AI Copilot
+
+Create a new Python file in your project: `trace_ai.py` with the code below
+
+```python
+import execdiff
+import time
+
+print("\nStarting AI action trace...\n")
+execdiff.start_action_trace(workspace=".")
+
+input("Tracing is ON. Use your AI copilot now.\n\nPress ENTER here once it's done...")
+
+print("\nStopping trace...\n")
+execdiff.stop_action_trace()
+
+print("\nSummary of last AI action:\n")
+print(execdiff.last_action_summary())
+```
+
+Now run this from the terminal:
+
+```bash
+python trace_ai.py
+```
+
+Tracing has now started and you’ll see:
+
+```
+Starting AI action trace...
+
+Tracing is ON. Use your AI copilot now.
+Press ENTER here once it's done...
+```
+
+Leave this terminal running.
+
+---
+
+## Step 5: Use Your AI Copilot Normally
+
+Now continue development normally inside your IDE using any AI copilot.
+
+For example, ask:
+
+> “Create a new feature for loading hello world into a pandas data frame and displaying it. Install the required libraries”
+
+Your copilot may now:
+
+- generate new code
+- install dependencies
+- modify config files
+- create or delete files
+
+inside your project workspace.
+
+You don’t need to change anything in your workflow.
+
+Just let your AI copilot run whatever setup it needs internally.
+
+---
+
+## Step 6: Stop the Trace
+
+Once it’s done, come back to terminal and press Enter
+
+You’ll get:
+
+```
+Summary of last AI action:
+Created:
+- output.txt
+- data.json
+Modified:
+- settings.py
+Installed:
+- requests==2.32.0
+```
+
+This includes:
+
+- filesystem changes
+- installed packages
+- deleted files
+- execution-time config updates
+
+All changes made during runtime.
+
+---
+
+## Automatic Logs
+
+Each AI-driven action is also stored inside:
+
+```
+.execdiff/logs/actions.jsonl
+```
+
+Now get a running history of what changed in your project after every AI action.
+
+---
+
+You can now continue using any AI copilot inside VS Code (or any IDE) normally while ExecDiff captures everything it changes behind the scenes.

{execdiff-0.0.5 → execdiff-0.0.7}/execdiff.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: execdiff
-Version: 0.0.5
+Version: 0.0.7
 Summary: Passive execution tracing for file and package changes.
 Author-email: Anup Moncy <n93181165@gmail.com>
 License:                                  Apache License
@@ -217,61 +217,56 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Dynamic: license-file
 
-# ExecDiff
+# Monitor AI Tool Workspace Changes
 
-See what AI-generated code will change before running it.
+AI coding tools like GitHub Copilot, Cursor, Replit AI, and agentic workflows install dependencies, modify configurations, and run setup commands in a project workspace.
 
----
+## Tracking Changes Beyond Git
 
-## Problem
+If GitHub Copilot implements a feature like API integration, it may:
 
-AI coding tools and agents today can:
+- Generate code.
+- Install libraries via the terminal.
+- Modify configuration files.
+- Create output files.
 
-- install dependencies  
-- create files  
-- modify configs  
-- run migrations  
-- delete project files  
+But when something breaks after execution, Git only shows code changes — not:
 
-All automatically.
+- newly installed packages
+- runtime-created files
+- deleted files
+- config updates done during execution
 
-When something breaks after execution, tools cannot answer:
+So it’s hard to tell what actually changed after an AI copilot action.
 
-> What exactly changed because of this action?
+Here’s how to capture everything automatically using VS Code (or any IDE with a terminal).
 
-Git tracks source code changes —  
-but it does **not** track execution side effects like:
+---
 
-- newly installed Python packages  
-- runtime-created files  
-- deleted files  
-- modified configs  
+## Step 1: Open Your Project in Your IDE
 
-So tools often fall back to:
+Open your project folder in VS Code (or any IDE).
 
-> regenerate and try again
+Now open the integrated terminal: **Terminal → New Terminal**
 
 ---
 
-## Solution
-
-ExecDiff allows tools to run AI-generated code and observe:
+## Step 2 (Optional): Create a Project-Level Python Environment
 
-> what changed in the workspace because of that execution
+If you want installs isolated to this project:
 
-It detects:
-
-- files created  
-- files modified  
-- files deleted  
-- Python packages installed  
+```bash
+python3 -m venv venv
+source venv/bin/activate
+```
 
-inside a specific workspace  
-during a specific execution window.
+Otherwise, you can skip this step.
 
 ---
 
-## Installation
+## Step 3: Install ExecDiff from Terminal
+
+Run this inside the terminal:
 
 ```bash
 pip install execdiff
@@ -279,134 +274,106 @@ pip install execdiff
 
 ---
 
-## Example
+## Step 4: Start Tracing Before Using Your AI Copilot
 
-Create a test script:
+Create a new Python file in your project: `trace_ai.py` with the code below
 
 ```python
 import execdiff
-import json
-import os
+import time
+
+print("\nStarting AI action trace...\n")
+execdiff.start_action_trace(workspace=".")
 
-os.makedirs("workspace", exist_ok=True)
+input("Tracing is ON. Use your AI copilot now.\n\nPress ENTER here once it's done...")
 
-diff = execdiff.run_traced(
-    "touch workspace/test.txt",
-    workspace="workspace"
-)
+print("\nStopping trace...\n")
+execdiff.stop_action_trace()
 
-print(json.dumps(diff, indent=2))
+print("\nSummary of last AI action:\n")
+print(execdiff.last_action_summary())
 ```
 
-Run:
+Now run this from the terminal:
 
 ```bash
-python test.py
+python trace_ai.py
 ```
 
+Tracing has now started and you’ll see:
+
+```
+Starting AI action trace...
+
+Tracing is ON. Use your AI copilot now.
+Press ENTER here once it's done...
+```
+
+Leave this terminal running.
+
 ---
 
-## API Reference
+## Step 5: Use Your AI Copilot Normally
 
-### `start_action_trace(workspace=".")`
+Now continue development normally inside your IDE using any AI copilot.
 
-Start tracing a workspace for changes. Must be called before any operations.
+For example, ask:
 
-```python
-import execdiff
+> “Create a new feature for loading hello world into a pandas data frame and displaying it. Install the required libraries”
 
-execdiff.start_action_trace(workspace="./my_workspace")
-# ... your code that makes changes ...
-```
+Your copilot may now:
 
-### `stop_action_trace()`
+- generate new code
+- install dependencies
+- modify config files
+- create or delete files
 
-Stop tracing and return a diff of all changes detected. Automatically logs to `.execdiff/logs/actions.jsonl`.
+inside your project workspace.
 
-```python
-diff = execdiff.stop_action_trace()
-# Returns: {"files": {...}, "packages": {...}}
-```
+You don’t need to change anything in your workflow.
 
-### `last_action_summary(workspace=".")`
+Just let your AI copilot run whatever setup it needs internally.
 
-Get a human-readable summary of the last action trace without parsing JSON.
+---
 
-```python
-summary = execdiff.last_action_summary(workspace=".")
-print(summary)
-```
+## Step 6: Stop the Trace
 
-Output example:
-```
-Last AI Action:
+Once it’s done, come back to terminal and press Enter
+
+You’ll get:
 
+```
+Summary of last AI action:
 Created:
 - output.txt
 - data.json
-
+Modified:
+- settings.py
 Installed:
 - requests==2.32.0
 ```
 
-### `snapshot_workspace_state(workspace)`
+This includes:
 
-Take a full metadata snapshot of the workspace (files with mtime/size, installed packages).
+- filesystem changes
+- installed packages
+- deleted files
+- execution-time config updates
 
-```python
-state = execdiff.snapshot_workspace_state(workspace=".")
-# Returns: {"files": {...}, "packages": {...}}
-```
+All changes made during runtime.
 
 ---
 
-## Output Format
-
-### Diff Structure
-
-```json
-{
-  "files": {
-    "created": [{"path": "file.txt", "mtime": 123.45, "size": 1024}],
-    "modified": [{"path": "config.yaml", "before_mtime": 123, "after_mtime": 124, "before_size": 512, "after_size": 1024}],
-    "deleted": [{"path": "old_file.txt", "mtime": 123.45, "size": 256}]
-  },
-  "packages": {
-    "installed": [{"name": "requests", "version": "2.32.0"}],
-    "upgraded": [{"name": "django", "before_version": "3.2", "after_version": "4.0"}],
-    "removed": [{"name": "deprecated_lib", "version": "1.0"}]
-  }
-}
-```
-
-### Log File
+## Automatic Logs
 
-All action traces are automatically persisted to `.execdiff/logs/actions.jsonl`:
+Each AI-driven action is also stored inside:
 
-```json
-{
-  "timestamp": "2026-02-18T18:19:35.872838",
-  "workspace": "/path/to/workspace",
-  "diff": {...}
-}
+```
+.execdiff/logs/actions.jsonl
 ```
 
----
-
-## Use Cases
-
-ExecDiff can help AI coding tools:
-
-- preview changes before applying generated code  
-- detect unintended file or dependency changes  
-- explain execution impact to users  
-- debug failed automation  
-- build undo / rollback systems  
+Now get a running history of what changed in your project after every AI action.
 
 ---
 
-## License
-
-MIT
-
-````
+You can now continue using any AI copilot inside VS Code (or any IDE) normally while ExecDiff captures everything it changes behind the scenes.

{execdiff-0.0.5 → execdiff-0.0.7}/execdiff.egg-info/SOURCES.txt

@@ -5,4 +5,5 @@ execdiff/__init__.py
 execdiff.egg-info/PKG-INFO
 execdiff.egg-info/SOURCES.txt
 execdiff.egg-info/dependency_links.txt
+execdiff.egg-info/entry_points.txt
 execdiff.egg-info/top_level.txt

execdiff-0.0.7/execdiff.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+execdiff = execdiff.cli:main

{execdiff-0.0.5 → execdiff-0.0.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "execdiff"
-version = "0.0.5"
+version = "0.0.7"
 description = "Passive execution tracing for file and package changes."
 readme = "README.md"
 license = { file = "LICENSE" }
@@ -23,6 +23,9 @@ classifiers = [
 	"Programming Language :: Python :: 3.12"
 ]
 
+[project.scripts]
+execdiff = "execdiff.cli:main"
+
 [tool.setuptools.packages.find]
 where = ["."]
 include = ["execdiff*"]

execdiff-0.0.5/README.md

@@ -1,193 +0,0 @@
-# ExecDiff
-
-See what AI-generated code will change before running it.
-
----
-
-## Problem
-
-AI coding tools and agents today can:
-
-- install dependencies  
-- create files  
-- modify configs  
-- run migrations  
-- delete project files  
-
-All automatically.
-
-When something breaks after execution, tools cannot answer:
-
-> What exactly changed because of this action?
-
-Git tracks source code changes —  
-but it does **not** track execution side effects like:
-
-- newly installed Python packages  
-- runtime-created files  
-- deleted files  
-- modified configs  
-
-So tools often fall back to:
-
-> regenerate and try again
-
----
-
-## Solution
-
-ExecDiff allows tools to run AI-generated code and observe:
-
-> what changed in the workspace because of that execution
-
-It detects:
-
-- files created  
-- files modified  
-- files deleted  
-- Python packages installed  
-
-inside a specific workspace  
-during a specific execution window.
-
----
-
-## Installation
-
-```bash
-pip install execdiff
-```
-
----
-
-## Example
-
-Create a test script:
-
-```python
-import execdiff
-import json
-import os
-
-os.makedirs("workspace", exist_ok=True)
-
-diff = execdiff.run_traced(
-    "touch workspace/test.txt",
-    workspace="workspace"
-)
-
-print(json.dumps(diff, indent=2))
-```
-
-Run:
-
-```bash
-python test.py
-```
-
----
-
-## API Reference
-
-### `start_action_trace(workspace=".")`
-
-Start tracing a workspace for changes. Must be called before any operations.
-
-```python
-import execdiff
-
-execdiff.start_action_trace(workspace="./my_workspace")
-# ... your code that makes changes ...
-```
-
-### `stop_action_trace()`
-
-Stop tracing and return a diff of all changes detected. Automatically logs to `.execdiff/logs/actions.jsonl`.
-
-```python
-diff = execdiff.stop_action_trace()
-# Returns: {"files": {...}, "packages": {...}}
-```
-
-### `last_action_summary(workspace=".")`
-
-Get a human-readable summary of the last action trace without parsing JSON.
-
-```python
-summary = execdiff.last_action_summary(workspace=".")
-print(summary)
-```
-
-Output example:
-```
-Last AI Action:
-
-Created:
-- output.txt
-- data.json
-
-Installed:
-- requests==2.32.0
-```
-
-### `snapshot_workspace_state(workspace)`
-
-Take a full metadata snapshot of the workspace (files with mtime/size, installed packages).
-
-```python
-state = execdiff.snapshot_workspace_state(workspace=".")
-# Returns: {"files": {...}, "packages": {...}}
-```
-
----
-
-## Output Format
-
-### Diff Structure
-
-```json
-{
-  "files": {
-    "created": [{"path": "file.txt", "mtime": 123.45, "size": 1024}],
-    "modified": [{"path": "config.yaml", "before_mtime": 123, "after_mtime": 124, "before_size": 512, "after_size": 1024}],
-    "deleted": [{"path": "old_file.txt", "mtime": 123.45, "size": 256}]
-  },
-  "packages": {
-    "installed": [{"name": "requests", "version": "2.32.0"}],
-    "upgraded": [{"name": "django", "before_version": "3.2", "after_version": "4.0"}],
-    "removed": [{"name": "deprecated_lib", "version": "1.0"}]
-  }
-}
-```
-
-### Log File
-
-All action traces are automatically persisted to `.execdiff/logs/actions.jsonl`:
-
-```json
-{
-  "timestamp": "2026-02-18T18:19:35.872838",
-  "workspace": "/path/to/workspace",
-  "diff": {...}
-}
-```
-
----
-
-## Use Cases
-
-ExecDiff can help AI coding tools:
-
-- preview changes before applying generated code  
-- detect unintended file or dependency changes  
-- explain execution impact to users  
-- debug failed automation  
-- build undo / rollback systems  
-
----
-
-## License
-
-MIT
-
-````