Glean Code Search lets engineers find the right code, commits, ADRs, tickets and PRs in one view—grounded in your company’s repos and tools. Code Writer uses that context to draft small PRs and targeted fixes, so teams can move from “what’s going on here?” to a reviewed change in minutes.

Spend less time searching and more time building: Glean Code Search & Code Writer

Glean has introduced Code Search and Code Writer to help engineering teams stay in flow. Instead of hopping between tabs for repos, tickets, docs and Slack threads, you can pull context into a single workspace, find what matters fast, and turn understanding into a draft pull request.

Why this matters

Engineering work is scattered: code, configs, design docs, incident notes, Jira issues and Slack threads. Context switching adds delay and risk. By unifying search across these sources—and letting an assistant act on that context—teams reduce meantime‑to‑understanding and get to shippable changes sooner.

Code Search: the right context, instantly

• Unified results. Surface relevant files, functions, commits, ADRs, tickets and PRs side‑by‑side.

• Repository‑aware. Results respect repository structure, branches and permissions.

• Everyday workflows. Ideal for debugging, code reviews, ramping onto new services, and tracing regressions across releases.

• Deep links. Jump directly into your IDE, Git provider, ticket or doc to continue work without losing context.

Code Writer: from insight to a draft PR

• Small, safe changes. Generate targeted patches and draft pull requests for well‑scoped fixes (e.g., log messages, config tweaks, minor refactors).

• Grounded by your stack. Suggestions are conditioned on your repos, tickets and docs, improving first‑time correctness.

• Human‑in‑the‑loop. You approve, edit and merge; Writer speeds the draft, you keep control of the final change.

• Triggers & actions. Kick off common tasks from the assistant or agent workflows and route outputs back to the tools you already use.

Example use cases

• Debugging a production issue. Search across code, recent PRs and incident notes; get the likely culprit and a suggested patch, then open a draft PR.

• Review assistance. Pull similar diffs and linked tickets to accelerate review and catch edge cases.

• Ramping onto a service. Ask for the architecture summary, key modules and past incidents; jump straight to the files that matter.

• Targeted refactors. Queue a series of small, reviewable changes with clear diffs and commit messages.

Availability & setup

• Code Search is available now.

• Code Writer can be enabled by admins in the console.

• Works with popular stacks (e.g., GitHub/GitLab, Jira, Confluence, Slack) and honours existing permissions.

• Export capability via MCP lets you connect flows with IDEs and agent tools that support the Model Context Protocol.

Security & governance

• Least‑privilege by design. Access follows your identity and repository permissions.

• Grounded outputs. Answers and suggested changes are tied back to sources—repos, tickets and docs—supporting audit and review.

• Admin control. Enable Code Writer when you’re ready; monitor usage and roll out to selected teams first.

Getting started (quick pilot)

1. Connect your Git provider, issue tracker and knowledge tools.

2. Pick one workflow—e.g., “weekly bug triage” or “reduce PR review time.”

3. Measure baseline (time‑to‑first‑fix, review latency, or context‑gathering time).

4. Enable Code Writer for the pilot group; enforce human review.

5. Compare outcomes and expand incrementally.

FAQs

What is Code Search?
A unified, developer‑focused search across code and context—files, functions, commits, ADRs, tickets and PRs—so you can find and understand faster.

What is Code Writer?
A capability that drafts small, targeted pull requests grounded in your company context; you review and merge.

How do we turn on Code Writer?
Admins can enable it in the console and roll out to selected teams; permissions continue to follow your identity and repo access.

Does it work with our IDEs and agent tools?
Yes—workflows can be exported via MCP, so you can connect to IDEs and agent clients that support the standard.

What are good first projects?
Bug triage, regression fixes, docstring improvements, dependency bumps with guardrails, and small refactors with clear tests.