You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
greptile init enables Greptile for the current repository, while automatic
onboarding now guides interactive users through setup when needed.
greptile skills update installs current Greptile-authored agent skills from
the API. The CLI also detects stale skills and reports available updates.
Interactive and scripted settings now cover the same local and organization
review settings, deployment URLs, members, and invitations.
greptile settings gains "Create a new organization", restoring organization
creation to the interactive CLI after greptile onboard was deprecated.
The Repositories settings flow now starts with a page showing the GitHub
organizations linked to your workspace (workspaces with more than one can
finally manage all of them from the CLI), with an "Install Greptile on
another GitHub organization" action that opens the dashboard's Code
providers page in your browser (printing the link when no browser is
available). The CLI then waits for the install to complete, confirms the
organization it detected, links it to your workspace, and lists it for
repository selection. A repository missing from the list no longer
dead-ends in the CLI.
Changed
greptile onboard now points existing users to greptile init and greptile settings.
Welcome, help, version, and other instant commands no longer initialize or
wait for telemetry.
Skill commands list and update only skills authored by Greptile.
The connection picker names what it lists: "Which GitHub organization should
this Greptile workspace use?" (GitLab: group), with "Refresh GitHub
organizations" / "Refresh GitLab groups" actions, and your personal GitHub
account is marked "(personal account)" so it does not read as an
organization. Naming the provider keeps these rows from being mistaken for
Greptile organizations.
Cancelling organization creation after the organization exists now explains
how to finish setting it up (Repositories in Settings, or the dashboard)
instead of returning to the menu silently.
Removed the expired settings migration from versions before 3.2.
Fixed
AI rules discovered during onboarding are imported only after confirmation,
only from an enabled repository in the current workspace, and only into that
repository's review context.