chore: move Delta Command to its own repository#10
Draft
nfaggian wants to merge 1 commit into
Draft
Conversation
The Delta Command engineering operations dashboard (previously under
apps/delta-command/) has been extracted into its own home:
https://github.com/nfaggian/delta-tools
Full delta-command commit history is preserved on the export branch
'cursor/delta-tools-export-535c' — that branch's tree is the delta-command
subtree hoisted to root, with paths and history rewritten by
'git subtree split --prefix=apps/delta-command'.
This commit removes the tracked delta-command tree from agent-experiments
(52 files, ~10k lines) and adds a one-line pointer at the top of the
root README so future readers can find the new repo.
Co-authored-by: Nathan Faggian <nathan.faggian@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Delta Command (the engineering ops dashboard under
apps/delta-command/) has outgrown its home in agent-experiments and is being moved to its own repository,nfaggian/delta-tools.This PR performs the "remove from source" half of the move:
apps/delta-command/— 52 files, ~10,100 linesThe other half — pushing to
nfaggian/delta-toolsSince Cloud Agents can't create new GitHub repositories, the export half has been done as a companion branch you can push to a brand-new repo once you create it.
Branch:
cursor/delta-tools-export-535cgit subtree split --prefix=apps/delta-command HEADfrom the tip ofcursor/llm-briefing-535c(which contains the latest Google branding, simplification, LLM briefing, and minimal UI work).apps/delta-command/foonow lives atfooat the repo root.apps/delta-command/exactly.One-time handoff
Create the
delta-toolsrepository on GitHub (empty, no README/license/gitignore), then push the export branch to it:nfaggian/delta-toolswill land with:backend/,src/,package.json,tailwind.config.ts, both READMEs, etc.).uv run pytestandnpm run buildout of the box (they only depend on paths inside the subtree, verified during earlier work).After the export lands
#8simplify,#9LLM briefing + minimal UI) — their contents are already part of the export branch and will be committed todelta-tools.cursor/delta-tools-export-535cbranch fromagent-experimentsonce it has been pushed todelta-tools(it's only meant as a shipping vehicle).Verification
apps/delta-command/is fully self-contained: no imports from repo root, no references in the rootMakefile,pyproject.toml,README.md, or.gitignore. Confirmed byrg "delta[-_]command|apps/delta"returning matches only insideapps/delta-command/.apps/delta-command/tree (diff -qongit ls-tree -r --name-onlyoutput returned no differences).apps/becomes empty after this removal — git will not track the empty parent, soapps/simply disappears from the repo.