Skip to main content
The Glean Feed CLI is the recommended starting point for an indie developer who wants product work to live beside the code. It connects one repository to one workspace, gives humans concise terminal commands, and gives agents and CI a stable JSON contract.

Five-minute setup

Install the CLI, connect a workspace, capture feedback, connect an agent, move an accepted request, and draft a changelog entry.

​
What the CLI operates

  • Read and create feedback, then update its stage or moderation status.
  • Promote accepted feedback to the roadmap without losing votes or comments.
  • Send accepted feedback to a configured Linear team.
  • Create, update, schedule, review, and explicitly publish changelog entries.
  • Import GitHub issues as feedback with dry-run, duplicate, and retry controls.
  • Install the Glean Feed MCP endpoint for Codex, Claude Code, Cursor, or VS Code.
  • Return deterministic JSON and exit codes for agents and CI.

​
Install

Node.js 20 or later is required.
Installation succeeded when gleanfeed --version prints a semantic version and gleanfeed --help lists auth, init, feedback, roadmap, changelog, and agent.

​
Human and agent use the same contract

Interactive commands show readable previews and ask before customer-visible or external writes. Agents and CI add --json for one machine-readable object and --yes when an approval prompt cannot be answered. The flag changes output and confirmation behavior; it does not widen scopes or change the selected workspace.
An OAuth token or API key always fixes the workspace on the server. --profile only selects a locally stored credential; no command accepts a workspace ID that can override the authenticated workspace.

​
Continue

Quickstart

Complete and verify the first product loop.

Command reference

Find every command group and approval boundary.

Profiles and repository config

Understand selection, local credentials, and .gleanfeed.json.

Agents and CI

Connect MCP clients and run noninteractive workflows.

Security

Store, scope, rotate, and revoke credentials safely.

Troubleshooting

Diagnose auth, config, network, and MCP failures.
Use the JavaScript SDK instead when trusted server code needs typed, in-process access rather than a subprocess. Use MCP when an agent should operate Glean Feed through its own OAuth connection.