v0.6.3: repo clone + workspace + workspace-clean#9
Merged
Conversation
Agents driven from non-interactive bridges (Discord/Telegram) had no structured path to clone a repo for edit work. They were falling back to `shell-exec git clone ...` which is auto-denied by merlin's Tier 1.5 safety gate under --yes mode (PR CorvidLabs/merlin#469). The agent then gave up with "I don't have local access" or escalated via owner-notify even when the user just wanted them to grab a repo and start working. Three new actions on `repo`: - `clone <OWNER/NAME> [DIR] [--depth N]` — thin wrapper over `gh repo clone`. Explicit destination, current cwd, inherits `gh auth` for private repos. - `workspace <OWNER/NAME> [-r REF] [--depth N]` — the high-level "give me a sandbox" path. Creates a fresh /tmp/fledge-gh-<owner>-<name>-XXXXXX/<name> dir via mktemp -d, clones the repo there, and prints the absolute path on stdout. -r REF is wired through git's --branch so shallow + ref work together (a post-clone checkout fails on shallow because the partial fetch only contains the default branch tip). - `workspace-clean <DIR>` — rm -rf with a safety check that refuses any path not under /tmp/fledge-gh-. If DIR is the inner clone path, walks up to the fledge-gh-* parent so we don't leave an empty shell behind. Plugin / arg description in plugin.toml updated to surface workspace as the preferred path for agents, with examples.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
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
1 participant
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
Closes the cross-repo-sandbox gap users hit in Discord: `shell-exec git clone ...` is auto-denied by merlin's Tier 1.5 safety gate in `--yes` mode (CorvidLabs/merlin#469), and there was no structured plugin command to clone instead. Adds three actions on `repo`:
Plugin and arg descriptions in `plugin.toml` surface `workspace` as the preferred path with examples.
Test plan