Skip to main content
This path starts with browser sign-in and ends with a reviewable changelog draft. Nothing publishes automatically.

​
Prerequisites

You need:
  • Node.js 20 or later and an existing Git repository.
  • A browser. You can sign in to an existing Glean Feed account or create an account and workspace during CLI login.
  • A feedback board that accepts submissions. Sending a request to Linear also requires a configured Linear connection.
  • A profile name. The examples use indie; choose a stable local name.
Review authentication and the scope table instead of granting broader access than this path needs.

​
1. Install and authenticate

The CLI opens Glean Feed in your browser. Sign in or create an account, choose a workspace, review the requested scopes, and approve access. If the browser does not open, copy the printed URL into a browser.
Authentication succeeded when the status output names profile indie, the expected workspace ID, your role, and the granted scopes.

​
2. Connect the repository

Run from anywhere inside the Git repository:
init writes .gleanfeed.json at the Git root. It contains only a schema version, profile selector, workspace ID, and optional non-secret defaults. Review it before deciding whether to commit it.
config validate reports a valid version 1 file, and whoami reports the same workspace as the authenticated profile. The file must not contain an API key, token, API endpoint, or machine path.

​
3. Capture and find feedback

Use a board slug from the dashboard. If the repository config already has defaultBoard, omit --board.
Copy the returned request ID, then verify the stored request:
Both reads show the same request ID, title, board, and current stage. The request also appears in the workspace dashboard.

​
4. Connect a coding agent

Preview the owned MCP configuration before changing it:
Complete OAuth in each client reported by the command. For example, run codex mcp login glean-feed for Codex; other client-specific steps are listed in Agents and CI. Verify with a read-only prompt:
The agent names the expected workspace and includes the request created in the previous step.

​
5. Move the accepted request

Choose one reviewed destination.
Promotion preserves the original request, votes, and comments. Linear delivery uses the workspace’s configured destination unless you pass documented overrides. Safe retries return the existing linked item or issue.
feedback get REQUEST_ID includes the linked roadmap item or active Linear issue, and the target appears in the dashboard.

​
6. Draft the customer update

Copy the entry ID and inspect the server copy:
The entry has state: "draft", contains the reviewed customer-facing text, and links the original feedback. It is not visible on the public Updates page until separately published.

​
Cleanup and revocation

If this was a disposable test, delete the draft and remove only the MCP entries owned by Glean Feed:
Delete .gleanfeed.json if the repository should no longer select this workspace. Logout attempts to revoke the browser grant, then always removes the local credential.
changelog publish, roadmap moves, feedback stage/status changes, and Linear delivery can affect customers or external systems. Review the preview and use --yes only after the intended write is clear.