greptile 3.3.1 → 3.4.1

package/CHANGELOG.md

@@ -4,6 +4,66 @@ All notable changes to the Greptile CLI.
 
 ## Unreleased
 
+## 3.4.1 - 2026-08-17
+
+### Changed
+
+- Agent skills documentation now reflects that Greptile fetches compatible
+  skills from the API and can update installed copies independently of CLI
+  releases.
+- Normalized `T-Rex` branding to `TREX` in terminal output.
+
+### Fixed
+
+- Repository lookup strips credentials embedded in HTTP(S) Git remotes before
+  sending the remote to Greptile.
+
+## 3.4.0 - 2026-08-10
+
+### Added
+
+- `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.
+
 ## 3.3.1 - 2026-07-29
 
 ### Fixed

package/README.md

@@ -36,9 +36,9 @@ On macOS, run `greptile fix install` after installing the CLI to set up Greptile
 ## Quick start
 
 ```sh
-greptile login        # opens your browser to sign in
-greptile onboard      # creates your Greptile organization
+greptile              # signs you in and walks you through setup on first run
 cd path/to/your/repo
+greptile init         # enables Greptile on this repository
 greptile review       # reviews HEAD against the default branch
 ```
 
@@ -51,8 +51,8 @@ Comments appear in the terminal as they come in.
 | `greptile review`           | Review the current branch against its base.                          |
 | `greptile review show [ID]` | Reopen a previous review. Omit the ID to pick from a list.           |
 | `greptile review status`    | Report the most recent review status for a commit (HEAD by default). |
+| `greptile init`             | Enable Greptile on the current repository.                           |
 | `greptile login`            | Sign in through your browser, or with `--api-key`.                   |
-| `greptile onboard`          | Onboard to Greptile by creating an organization interactively.       |
 | `greptile logout`           | Remove stored credentials.                                           |
 | `greptile whoami`           | Show who you are signed in as and your organizations.                |
 | `greptile settings`         | Manage CLI preferences, repositories, review settings, and team.     |
@@ -189,7 +189,14 @@ greptile review --include .env --include config/db.pem
 
 Run bare `greptile settings` in an interactive terminal to edit local CLI
 preferences. Organization admins can also manage repositories, review behavior,
-and team members from the same hub.
+and team members from the same hub, and **Create a new organization** sets up
+another Greptile organization (a separate workspace) without needing to
+administer an existing one.
+
+> ℹ️ **Note:** If you cancel organization creation after the organization has
+> been created, it stays around half set up (there is no way to delete it from
+> the CLI). Use **Repositories** in the same hub to connect a provider and
+> enable repositories, or finish the remaining setup from your dashboard.
 
 Save local defaults non-interactively instead of repeating flags:
 
@@ -214,32 +221,34 @@ Settings live in `~/.config/greptile/settings.json` (or `$XDG_CONFIG_HOME/grepti
 
 ## Agent skills
 
-Skills are instructions AI coding agents read. The CLI bundles two:
+Skills are instructions AI coding agents read. Greptile provides two for the CLI:
 
 | Skill          | What it covers                                                                          |
 | -------------- | --------------------------------------------------------------------------------------- |
 | `greptile-cli` | How to run the CLI: commands, JSON output shapes, exit codes.                           |
 | `greploop`     | Reviewing a branch, fixing the findings, and reviewing again until it comes back clean. |
 
-`greptile onboard` offers to install them. You can also do it anytime:
+The setup wizard offers to install them. You can also do it anytime:
 
 ```sh
-greptile skills list                  # what ships with this CLI
+greptile skills list                  # what is installed on this machine
 greptile skills install               # asks where, if you're at a terminal
 greptile skills install --global      # all your projects, no prompt
 greptile skills install greploop      # just one
 greptile skills install --force       # replace installed copies
+greptile skills update                # update installed copies
 ```
 
 Skills are written to `.agents/skills/<name>/`, which Codex, Cursor, Gemini CLI, Copilot and other
 tools following the [Agent Skills](https://agentskills.io) standard read, plus `.claude/skills/`
 and `.codex/skills/` when those agents are set up in the same place.
 
-An installed skill is left alone unless you pass `--force`, so local edits are kept. A skill left
-incomplete by a failed write is repaired on the next run.
+Skills are fetched from Greptile, so installation delivers the latest version compatible with your
+CLI. The CLI checks installed Greptile-authored skills in the background and tells you when updates
+are available. Run `greptile skills update` to apply them.
 
-They are compiled into the CLI, so they describe the version you have installed. Upgrade the CLI
-and re-run with `--force` to update them.
+An installed skill is left alone unless you pass `--force`, so local edits are kept. A skill left
+incomplete by a failed write is repaired on the next install. Updates replace stale installed files.
 
 ## Diagrams
 
@@ -288,7 +297,7 @@ greptile review [-b BRANCH] [--layout comments|diff | --diff] [--resume] [--incl
 greptile review show [ID]   # same output flags as review
 greptile review status [--commit REF] [--json | --text | --agent]
 greptile settings list | get KEY | set KEY VALUE | unset KEY | path
-greptile skills list [--json] | install [NAME...] [-g] [-f] [--json]
+greptile skills list [--json] | install [NAME...] [-g] [-f] [--json] | update [--json]
 greptile fix install | status [--json] | uninstall [--remove-mappings]
 greptile update
 ```