git-juggler 0.2.16__tar.gz → 0.2.17__tar.gz

{git_juggler-0.2.16 → git_juggler-0.2.17}/.gitignore

@@ -25,7 +25,8 @@ secrets.env
 .vscode/
 *.sw?
 
-# Personal task notes (see CLAUDE.md)
+# Local assistant/project notes
+CLAUDE.md
 todo.txt
 
 plans/

{git_juggler-0.2.16 → git_juggler-0.2.17}/PKG-INFO

@@ -1,9 +1,28 @@
 Metadata-Version: 2.5
 Name: git-juggler
-Version: 0.2.16
+Version: 0.2.17
 Summary: A local Git dashboard for people juggling agents and too many repos.
+Project-URL: Homepage, https://github.com/franz38/git-juggler
+Project-URL: Repository, https://github.com/franz38/git-juggler
+Project-URL: Issues, https://github.com/franz38/git-juggler/issues
+Project-URL: Releases, https://github.com/franz38/git-juggler/releases
 License-Expression: MIT
 License-File: LICENSE
+Keywords: agents,dashboard,git,repositories,terminal
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Web Environment
+Classifier: Framework :: FastAPI
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Version Control :: Git
 Requires-Python: >=3.10
 Requires-Dist: fastapi>=0.110
 Requires-Dist: gitpython>=3.1
@@ -30,6 +49,14 @@ Watch agents work live, follow every repo’s git graph, and catch what changed
 - Connects GitHub Actions and Jenkins runs to commits and active pipelines.
 - VS Code-compatible themes.
 
+## Privacy / local-first
+
+- Runs locally and binds to `127.0.0.1` by default.
+- No telemetry or analytics are built in, and none are planned.
+- Repo scanning and Claude/OpenCode session tracking read local files on your machine.
+- Git mutations run through visible terminal commands, so you can see the exact command and output.
+- Network requests are only used for features you configure, such as CI integrations.
+
 ## How to install
 
 git-juggler is published on PyPI. The recommended way to install it is with
@@ -46,7 +73,7 @@ to seed the initial search path; after that, search paths are managed in the app
 from the welcome wizard or Settings.
 
 - `--host HOST` changes the bind host from the default `127.0.0.1`.
-- `--port PORT` changes the backend port from the default `8000`.
+- `--port PORT` changes the backend port from the default `8788`.
 - `--no-open` disables opening the app in your browser automatically.
 
 If you don't have pipx yet:
@@ -85,7 +112,7 @@ Use the dev script to start both the backend and frontend dev servers:
 ```
 
 - `path-to-scan` is optional. On first run, it seeds the folder whose immediate children are scanned for Git repos.
-- `--port PORT` is optional. It changes the backend port from the default `8000`; if you use it, update `src/frontend/vite.config.ts` locally so Vite proxies `/api` and `/ws` to the same port.
+- `--port PORT` is optional. It changes the backend port from the default `8788`; the dev script passes the selected port to Vite automatically.
 - `--no-open` disables opening the app in your browser automatically.
 
 Or run them manually in two terminals:
@@ -99,7 +126,7 @@ python3 -m venv .venv
 ```
 cd src/frontend
 npm install
-npm run dev                                     # http://localhost:5173 (proxies /api and /ws to :8000)
+npm run dev                                     # http://localhost:5173 (proxies /api and /ws to :8788)
 ```
 
 Open http://localhost:5173.
@@ -113,7 +140,7 @@ cd src/frontend && npm install && npm run build
 cd ../.. && .venv/bin/git-juggler <path-to-scan> [--no-open]
 ```
 
-The backend serves the built frontend in this mode, so only port 8000 is needed.
+The backend serves the built frontend in this mode, so only port 8788 is needed.
 By default, it opens the app in your browser.
 
 ## Build a Python package

{git_juggler-0.2.16 → git_juggler-0.2.17}/README.md

@@ -17,6 +17,14 @@ Watch agents work live, follow every repo’s git graph, and catch what changed
 - Connects GitHub Actions and Jenkins runs to commits and active pipelines.
 - VS Code-compatible themes.
 
+## Privacy / local-first
+
+- Runs locally and binds to `127.0.0.1` by default.
+- No telemetry or analytics are built in, and none are planned.
+- Repo scanning and Claude/OpenCode session tracking read local files on your machine.
+- Git mutations run through visible terminal commands, so you can see the exact command and output.
+- Network requests are only used for features you configure, such as CI integrations.
+
 ## How to install
 
 git-juggler is published on PyPI. The recommended way to install it is with
@@ -33,7 +41,7 @@ to seed the initial search path; after that, search paths are managed in the app
 from the welcome wizard or Settings.
 
 - `--host HOST` changes the bind host from the default `127.0.0.1`.
-- `--port PORT` changes the backend port from the default `8000`.
+- `--port PORT` changes the backend port from the default `8788`.
 - `--no-open` disables opening the app in your browser automatically.
 
 If you don't have pipx yet:
@@ -72,7 +80,7 @@ Use the dev script to start both the backend and frontend dev servers:
 ```
 
 - `path-to-scan` is optional. On first run, it seeds the folder whose immediate children are scanned for Git repos.
-- `--port PORT` is optional. It changes the backend port from the default `8000`; if you use it, update `src/frontend/vite.config.ts` locally so Vite proxies `/api` and `/ws` to the same port.
+- `--port PORT` is optional. It changes the backend port from the default `8788`; the dev script passes the selected port to Vite automatically.
 - `--no-open` disables opening the app in your browser automatically.
 
 Or run them manually in two terminals:
@@ -86,7 +94,7 @@ python3 -m venv .venv
 ```
 cd src/frontend
 npm install
-npm run dev                                     # http://localhost:5173 (proxies /api and /ws to :8000)
+npm run dev                                     # http://localhost:5173 (proxies /api and /ws to :8788)
 ```
 
 Open http://localhost:5173.
@@ -100,7 +108,7 @@ cd src/frontend && npm install && npm run build
 cd ../.. && .venv/bin/git-juggler <path-to-scan> [--no-open]
 ```
 
-The backend serves the built frontend in this mode, so only port 8000 is needed.
+The backend serves the built frontend in this mode, so only port 8788 is needed.
 By default, it opens the app in your browser.
 
 ## Build a Python package

git_juggler-0.2.17/pyproject.toml

@@ -0,0 +1,53 @@
+[project]
+name = "git-juggler"
+dynamic = ["version"]
+description = "A local Git dashboard for people juggling agents and too many repos."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "MIT"
+keywords = ["agents", "dashboard", "git", "repositories", "terminal"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Web Environment",
+    "Framework :: FastAPI",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: MacOS",
+    "Operating System :: Microsoft :: Windows",
+    "Operating System :: POSIX :: Linux",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development :: Version Control :: Git",
+]
+dependencies = [
+    "fastapi>=0.110",
+    "uvicorn[standard]>=0.29",
+    "gitpython>=3.1",
+    "pywinpty>=2.0; sys_platform == 'win32'",
+]
+
+[project.scripts]
+git-juggler = "git_juggler.main:cli"
+
+[project.urls]
+Homepage = "https://github.com/franz38/git-juggler"
+Repository = "https://github.com/franz38/git-juggler"
+Issues = "https://github.com/franz38/git-juggler/issues"
+Releases = "https://github.com/franz38/git-juggler/releases"
+
+[build-system]
+requires = ["hatchling", "hatch-vcs"]
+build-backend = "hatchling.build"
+
+[tool.hatch.version]
+source = "vcs"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/backend/git_juggler"]
+artifacts = ["src/backend/git_juggler/frontend_dist/**"]
+
+[tool.hatch.build.targets.sdist]
+artifacts = ["src/backend/git_juggler/frontend_dist/**"]

{git_juggler-0.2.16 → git_juggler-0.2.17}/scripts/dev.sh

@@ -1,10 +1,10 @@
 #!/usr/bin/env bash
 # Runs the backend and frontend dev servers together, both hot-reloading.
-# See CLAUDE.md's "How to run locally" section for the equivalent manual steps.
+# See README.md's "Dev mode" section for the equivalent manual steps.
 set -euo pipefail
 
 ROOT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-BACKEND_PORT=8000
+BACKEND_PORT=8788
 OPEN_BROWSER=1
 
 usage() {
@@ -12,8 +12,7 @@ usage() {
   echo "  path-to-scan    optional: directory whose first-level children get scanned for git repos." >&2
   echo "                  Only used to seed the config on first run; scan paths are otherwise" >&2
   echo "                  managed in the app (welcome wizard / Settings)." >&2
-  echo "  --port PORT     backend port (default: 8000). If you change this, also update" >&2
-  echo "                  src/frontend/vite.config.ts's proxy target -- don't commit that change." >&2
+  echo "  --port PORT     backend port (default: 8788)." >&2
   echo "  --no-open       don't open the app in a browser automatically." >&2
 }
 
@@ -115,7 +114,7 @@ fi
 BACKEND_PID=$!
 
 echo "Starting frontend dev server..."
-(cd "$ROOT_DIR/src/frontend" && npm run dev) &
+(cd "$ROOT_DIR/src/frontend" && GIT_JUGGLER_BACKEND_URL="http://127.0.0.1:$BACKEND_PORT" npm run dev) &
 FRONTEND_PID=$!
 
 if [ "$OPEN_BROWSER" = "1" ]; then
@@ -125,11 +124,6 @@ fi
 echo ""
 echo "Backend:  http://127.0.0.1:$BACKEND_PORT"
 echo "Frontend: http://localhost:5173  <- open this"
-if [ "$BACKEND_PORT" != "8000" ]; then
-  echo ""
-  echo "NOTE: backend is on a non-default port. Update the proxy target in" \
-       "src/frontend/vite.config.ts to http://127.0.0.1:$BACKEND_PORT (local-only change, do not commit)."
-fi
 echo ""
 echo "Press Ctrl+C to stop both."
 

{git_juggler-0.2.16 → git_juggler-0.2.17}/src/backend/git_juggler/main.py

@@ -45,7 +45,7 @@ def parse_args(argv: list[str] | None = None) -> argparse.Namespace:
         help="Directory whose first-level children will be scanned for git repos (default: cwd)",
     )
     parser.add_argument("--host", default="127.0.0.1")
-    parser.add_argument("--port", type=int, default=8000)
+    parser.add_argument("--port", type=int, default=8788)
     parser.add_argument("--reload", action="store_true", help="Enable dev auto-reload")
     parser.add_argument("--no-open", action="store_true", help="Do not open the app in a browser")
     args = parser.parse_args(argv)

{git_juggler-0.2.16 → git_juggler-0.2.17}/src/frontend/vite.config.ts

@@ -1,13 +1,16 @@
 import { defineConfig } from 'vite'
 import solid from 'vite-plugin-solid'
 
+const backendUrl = process.env.GIT_JUGGLER_BACKEND_URL ?? "http://127.0.0.1:8788"
+const backendWsUrl = backendUrl.replace(/^http/, "ws")
+
 export default defineConfig({
   plugins: [solid()],
   server: {
     proxy: {
-      "/api": "http://127.0.0.1:8000",
+      "/api": backendUrl,
       "/ws": {
-        target: "ws://127.0.0.1:8000",
+        target: backendWsUrl,
         ws: true,
       },
     },

git_juggler-0.2.16/CLAUDE.md

@@ -1,101 +0,0 @@
-# git-juggler
-
-## How to run locally
-
-Dev mode (hot reload on both sides):
-
-```
-python3 -m venv .venv
-.venv/bin/pip install -e .
-.venv/bin/git-juggler <path-to-scan> --reload   # http://127.0.0.1:8000
-```
-
-```
-cd src/frontend
-npm install
-npm run dev                                     # http://localhost:5173 (proxies /api and /ws to :8000)
-```
-
-Open http://localhost:5173 — that's the app, hot-reloading both frontend and backend.
-
-- `<path-to-scan>` is the directory whose first-level children get scanned for git repos (e.g. `~/Documents/2026`).
-- If port 8000 is unavailable on this machine (it can be occupied by unrelated local processes), run the backend with a different `--port` and update `src/frontend/vite.config.ts`'s proxy target to match — but don't commit that port change, it's a local workaround, not a project default.
-- Single-port production mode (backend serves the built frontend, no Vite) is documented in `README.md`.
-- Unless explicitly told otherwise, run both the backend and frontend from
-  the primary checkout on the `main` branch — not from a
-  `.claude/worktrees/*` copy. Worktrees exist to isolate one task's
-  in-progress changes; they don't reflect what's actually landed on `main`,
-  so running (or leaving running) a dev server out of one can silently show
-  stale or unrelated behavior for work that's already merged.
-
-## Architecture guideline: git mutations go through the terminal only
-
-All UI-triggered git actions (e.g. right-click on a commit → Checkout) must be
-executed via the frontend terminal (`runInTerminal` in `src/frontend/src/state/store.ts`),
-not via a dedicated backend API endpoint.
-
-- The backend only ever performs **read** operations on repos (GitPython,
-  used for the commit graph, repo listing, branch/tag/stash info, etc.).
-- Any action that *changes* repo state (checkout, commit, branch, stash,
-  merge, reset, push, pull, ...) must be implemented as a command sent to
-  that repo's terminal session, the same way checkout is.
-- Do not add a backend route that shells out to `git` (or calls a mutating
-  GitPython method) to perform an action on behalf of the UI.
-
-Why: the terminal is the single point where git is actually invoked, so
-there's exactly one code path to reason about for anything that mutates a
-repo, and the user always sees the real command (and its real output/errors)
-run for any git action, instead of a backend silently doing it.
-
-## Testing: use the demo repo, never the user's real repos
-
-`~/Documents/2026/demo-repo` is a disposable local git repo created
-specifically for testing git-juggler — it has multiple branches
-(`main`, `feature/onboarding` merged, `feature/dashboard` unmerged), a merge
-commit, a tag (`v0.1.0`), and a stash, with a clean working tree.
-
-- Always test UI actions that mutate repo state (checkout, fetch, and
-  anything added later) against `demo-repo`, never against the user's real
-  projects (e.g. anything under `~/Documents/2025/projects`, `fanta-bot`,
-  etc.) — those have real uncommitted work and real history that must not be
-  disturbed.
-- It's already inside a configured scan path (`~/Documents/2026`), so it
-  shows up in the app automatically — no config changes needed to use it.
-- It has no remote configured on purpose. The user will connect it to GitHub
-  themselves to test remote-related mechanics (fetch/push/pull against a
-  real remote) — don't add a remote to it.
-- If a test needs a specific extra state (dirty working tree, a particular
-  conflict, more branches, etc.), set that up in `demo-repo` (or a fresh
-  scratch repo elsewhere), not in a real project.
-
-## Don't push without consensus
-
-Never run `git push` (including to a branch, a fork, or opening a PR) until
-the user has explicitly agreed to it in that conversation. Committing
-locally is fine; pushing is not, until they say so.
-
-## todo.txt: notes queue
-
-`todo.txt` (repo root, gitignored — never commit it) is the user's plain-text
-list of things to implement. It is split by a marker line:
-
-```
---------------- IMPLEMENTED ----------------
-```
-
-- Everything **before** the marker is already implemented.
-- Everything **after** the marker is still to do.
-
-When the user asks to implement the todo list (e.g. "implement todo"):
-
-1. Do the whole activity in a dedicated worktree (e.g. `todo`), not in the
-   primary checkout: enter it before touching any code, and commit there.
-   Read `todo.txt` from the primary checkout (it's gitignored, so it isn't
-   present in worktrees) and take all the notes after the marker.
-2. Implement them (following the rest of this file's guidelines).
-3. Move the marker line down so it sits after the notes just implemented
-   (i.e. those notes now live above it), leaving any not-implemented notes
-   below it. Edit only the marker's position; don't rewrite the user's notes. Since `todo.txt` is
-   gitignored, this edit is made on the primary checkout's copy.
-
-If `todo.txt` doesn't exist, create it containing just the marker line.

git_juggler-0.2.16/pyproject.toml

@@ -1,30 +0,0 @@
-[project]
-name = "git-juggler"
-dynamic = ["version"]
-description = "A local Git dashboard for people juggling agents and too many repos."
-readme = "README.md"
-requires-python = ">=3.10"
-license = "MIT"
-dependencies = [
-    "fastapi>=0.110",
-    "uvicorn[standard]>=0.29",
-    "gitpython>=3.1",
-    "pywinpty>=2.0; sys_platform == 'win32'",
-]
-
-[project.scripts]
-git-juggler = "git_juggler.main:cli"
-
-[build-system]
-requires = ["hatchling", "hatch-vcs"]
-build-backend = "hatchling.build"
-
-[tool.hatch.version]
-source = "vcs"
-
-[tool.hatch.build.targets.wheel]
-packages = ["src/backend/git_juggler"]
-artifacts = ["src/backend/git_juggler/frontend_dist/**"]
-
-[tool.hatch.build.targets.sdist]
-artifacts = ["src/backend/git_juggler/frontend_dist/**"]