Requested outcome
agentuity deploy, run from a git directory with a GitHub remote, should offer to link the project to that repository when no repository link exists yet. Today the link is only created through the GitHub integration or agentuity git link, so CLI-first projects end up with no repository association and platform features that depend on the linked repo can't use them.
What the source shows today
- Deploy already reads the git remote: non-Agentuity builds call
getGitInfo() (packages/cli/src/utils/git.ts) and record deployment-level git metadata, but the project-level repository link is never written.
- Deploy contains an interactive GitHub-setup block (
packages/cli/src/cmd/cloud/deploy.ts, the getProjectGithubStatus prompt) that is unreachable in the normal parent-child flow: the block requires !useExistingDeployment && hasTTY, while the forked child runs with useExistingDeployment = true and non-TTY output.
agentuity git link (packages/cli/src/cmd/git/link.ts) already implements remote detection and the link API call.
Implementation options
- Re-site the existing dormant prompt into the parent flow, after project resolution and before the preflight/fork, where a TTY exists. Reuses existing behavior; no new policy decisions.
- In non-TTY runs (CI), print a hint to run
agentuity git link instead of prompting.
Open questions
- Defaults for
branch, monorepo directory, auto-deploy, and preview-environment settings if linking becomes non-interactive later.
- Project responses in
@agentuity/server schemas don't expose the repository association; SDK consumers may want it surfaced.
Internal evidence for the motivating flow is available separately.
Requested outcome
agentuity deploy, run from a git directory with a GitHub remote, should offer to link the project to that repository when no repository link exists yet. Today the link is only created through the GitHub integration oragentuity git link, so CLI-first projects end up with no repository association and platform features that depend on the linked repo can't use them.What the source shows today
getGitInfo()(packages/cli/src/utils/git.ts) and record deployment-level git metadata, but the project-level repository link is never written.packages/cli/src/cmd/cloud/deploy.ts, thegetProjectGithubStatusprompt) that is unreachable in the normal parent-child flow: the block requires!useExistingDeployment && hasTTY, while the forked child runs withuseExistingDeployment = trueand non-TTY output.agentuity git link(packages/cli/src/cmd/git/link.ts) already implements remote detection and the link API call.Implementation options
agentuity git linkinstead of prompting.Open questions
branch, monorepodirectory, auto-deploy, and preview-environment settings if linking becomes non-interactive later.@agentuity/serverschemas don't expose the repository association; SDK consumers may want it surfaced.Internal evidence for the motivating flow is available separately.