feat: add tips from Zed v0.226.4 and v0.227.1

tips/activate-last-pane-keybinding.mdx

@@ -0,0 +1,48 @@
+---
+title: Jump to Last Pane with Keybinding
+subtitle: Add a keyboard shortcut to focus the rightmost pane instantly
+category: navigation
+difficulty: beginner
+tags:
+  - panes
+  - keybindings
+  - navigation
+  - workflow
+prUrl: 'https://github.com/zed-industries/zed/pull/49853'
+publishedAt: '2026-03-16'
+updatedAt: '2026-03-16'
+author: godruoyi
+authorUrl: 'https://github.com/godruoyi'
+---
+
+The new `workspace::ActivateLastPane` action lets you bind a keyboard shortcut that always focuses the rightmost pane, providing a predictable navigation target.
+
+## How to Use
+
+Add this to your keymap.json:
+
+```json
+{
+  "bindings": {
+    "cmd-9": "workspace::ActivateLastPane"
+  }
+}
+```
+
+Now pressing **`Cmd-9`** always jumps to the last (rightmost) pane in your current window.
+
+## Why This Matters
+
+**Predictable navigation**: Unlike numbered pane actions, this never creates new panes.
+
+**Stable target**: Always focuses the rightmost pane regardless of how many panes exist.
+
+**Complements existing shortcuts**: Works well with `Cmd-1` through `Cmd-8` for other panes.
+
+**No side effects**: Pure focus action - never splits or modifies your layout.
+
+## Comparison with ActivatePane
+
+`workspace::ActivatePane` with an index can create/split panes when the index doesn't exist. `ActivateLastPane` is focus-only and never modifies your pane layout.
+
+This is perfect for users who want a reliable "jump to rightmost pane" shortcut similar to terminal or browser tab navigation patterns.

tips/ctrl-enter-newline-search.mdx

@@ -0,0 +1,47 @@
+---
+title: Insert Newlines in Search Bars with Ctrl-Enter
+subtitle: Add line breaks in search queries using keyboard shortcut on macOS
+category: shortcuts
+difficulty: beginner
+tags:
+  - search
+  - keybindings
+  - multiline
+  - macos
+prUrl: 'https://github.com/zed-industries/zed/pull/50420'
+publishedAt: '2026-03-16'
+updatedAt: '2026-03-16'
+author: godruoyi
+authorUrl: 'https://github.com/godruoyi'
+---
+
+On macOS, you can now use **`Ctrl-Enter`** to insert newlines in search bars, making it easier to search for multi-line patterns.
+
+## How to Use
+
+1. Open buffer search (**`Cmd-F`**) or project search (**`Cmd-Shift-F`**)
+2. Type your search query
+3. Press **`Ctrl-Enter`** to insert a newline
+4. Continue typing on the next line
+5. **`Enter`** still executes the search as before
+
+This keybinding is macOS-specific and matches common text editing patterns.
+
+## Why This Matters
+
+**Multi-line searches**: Find patterns that span multiple lines.
+
+**Regex patterns**: Format complex regular expressions for readability.
+
+**Code blocks**: Search for code snippets with proper line breaks.
+
+**Natural workflow**: **`Ctrl-Enter`** for newline, **`Enter`** for action.
+
+## Example Use Cases
+
+- Searching for multi-line function signatures
+- Finding code blocks with specific structure
+- Locating formatted text patterns
+- Building readable regex patterns with line breaks for clarity
+
+Previously, there was no easy way to insert newlines in search bars - pressing **`Enter`** would execute the search. This enhancement brings better multi-line search support to Zed.

tips/customize-vim-yank-highlight.mdx

@@ -0,0 +1,56 @@
+---
+title: Customize Vim Yank Highlight Color
+subtitle: Set a custom background color for vim yank highlighting in your theme
+category: vim
+difficulty: beginner
+tags:
+  - vim
+  - theme
+  - customization
+  - visual
+prUrl: 'https://github.com/zed-industries/zed/pull/49517'
+mediaType: image
+mediaUrl: 'https://cat.zed.tips/2026-03-16/customize-vim-yank-highlight-146fe90f.png'
+publishedAt: '2026-03-16'
+updatedAt: '2026-03-16'
+author: godruoyi
+authorUrl: 'https://github.com/godruoyi'
+---
+
+Vim mode now supports customizing the background color that appears when you yank (copy) text, allowing you to make it more visible or match your theme preferences.
+
+## How to Configure
+
+Add this to your settings.json:
+
+```json
+{
+  "theme_overrides": {
+    "Your Theme Name": {
+      "vim.yank.background": "#FE7F1F"
+    }
+  }
+}
+```
+
+Replace `"Your Theme Name"` with your active theme (e.g., "Gruvbox Material", "One Dark", etc.) and choose your preferred color.
+
+## Why This Matters
+
+**Better visibility**: Make yank highlighting stand out more than the default document highlight color.
+
+**Theme consistency**: Match the yank highlight to your color scheme.
+
+**Accessibility**: Use higher contrast colors if needed for better visibility.
+
+**Personal preference**: Choose colors that work best for your eyes and workflow.
+
+Previously, vim yank highlighting was hardcoded to use `editor.document_highlight.read_background`, making it impossible to distinguish from other highlights. Now you have full control over this visual feedback.
+
+## Example Colors
+
+Try these popular choices:
+- Orange: `#FE7F1F` (high visibility)
+- Yellow: `#FFEB3B` (classic highlight)
+- Blue: `#2196F3` (cool tone)
+- Green: `#4CAF50` (subtle)

tips/diagnostic-count-badges.mdx

@@ -0,0 +1,51 @@
+---
+title: See Error and Warning Counts in Project Panel
+subtitle: Display diagnostic badges next to files showing error and warning counts
+category: productivity
+difficulty: beginner
+tags:
+  - diagnostics
+  - project-panel
+  - errors
+  - ui
+prUrl: 'https://github.com/zed-industries/zed/pull/49802'
+mediaType: image
+mediaUrl: 'https://cat.zed.tips/2026-03-16/diagnostic-count-badges-c9bb5860.png'
+publishedAt: '2026-03-16'
+updatedAt: '2026-03-16'
+author: godruoyi
+authorUrl: 'https://github.com/godruoyi'
+---
+
+The project panel can now show colored badges displaying the number of errors and warnings for each file, making it easy to spot which files need attention at a glance.
+
+## How to Enable
+
+1. Open Settings (**`Cmd-,`** on macOS)
+2. Search for **diagnostic_badges**
+3. Enable the option
+4. Error counts appear in red, warnings in yellow next to file names
+
+Diagnostic counts automatically bubble up to parent directories, showing the total count for all files within.
+
+## Why This Matters
+
+**Visual scanning**: Quickly identify problematic files without opening them.
+
+**Prioritize work**: See which files have the most issues at a glance.
+
+**Track progress**: Watch error counts decrease as you fix issues.
+
+**Directory-level view**: Parent folders show aggregate counts for all contained files.
+
+When enabled, diagnostic severity takes priority over git status for file text color, while git status remains visible through file icon decorations.
+
+## Configuration
+
+The setting is disabled by default. Add to your settings.json:
+
+```json
+{
+  "diagnostic_badges": true
+}
+```

tips/git-panel-diff-stats.mdx

@@ -0,0 +1,53 @@
+---
+title: See Addition and Deletion Counts in Git Panel
+subtitle: View file-level diff statistics showing lines added and removed
+category: git
+difficulty: beginner
+tags:
+  - git
+  - diff
+  - statistics
+  - ui
+prUrl: 'https://github.com/zed-industries/zed/pull/49519'
+mediaType: image
+mediaUrl: 'https://cat.zed.tips/2026-03-16/git-panel-diff-stats-d6ecc2df.png'
+publishedAt: '2026-03-16'
+updatedAt: '2026-03-16'
+author: godruoyi
+authorUrl: 'https://github.com/godruoyi'
+---
+
+The git panel now displays diff statistics for each modified file, showing you exactly how many lines were added and removed without opening the file.
+
+## How to Enable
+
+1. Open Settings (**`Cmd-,`** on macOS)
+2. Search for **git_panel**
+3. Find the **diff_stats** option and enable it
+4. Addition and deletion counts appear next to each file in the git panel
+
+The counts are shown as colored numbers: green for additions, red for deletions.
+
+## Why This Matters
+
+**Quick assessment**: Gauge the scope of changes at a glance.
+
+**Review planning**: Prioritize which files to review based on change size.
+
+**Spot outliers**: Identify unexpectedly large changes that might need extra attention.
+
+**Context awareness**: Understand the impact of commits before viewing detailed diffs.
+
+## Configuration
+
+Add to your settings.json:
+
+```json
+{
+  "git_panel": {
+    "diff_stats": true
+  }
+}
+```
+
+The setting is disabled by default to keep the git panel minimal, but enabling it provides valuable context for code review and commit planning.

tips/jump-to-file-from-agent-diff.mdx

@@ -0,0 +1,48 @@
+---
+title: Jump to Files from Agent Diffs
+subtitle: Open files directly from agent-shown diffs with Option-Enter
+category: ai
+difficulty: beginner
+tags:
+  - agent
+  - navigation
+  - diff
+  - workflow
+prUrl: 'https://github.com/zed-industries/zed/pull/50292'
+mediaType: video
+mediaUrl: 'https://cat.zed.tips/2026-03-16/jump-to-file-from-agent-diff-1a16202b.mov'
+publishedAt: '2026-03-16'
+updatedAt: '2026-03-16'
+author: godruoyi
+authorUrl: 'https://github.com/godruoyi'
+---
+
+When reviewing diffs in the agent conversation, you can now jump directly to the actual file by placing your cursor in the diff and pressing **`Option-Enter`**.
+
+## How to Use
+
+1. Review agent changes in the Agent Panel
+2. Click anywhere in a diff block to place your cursor
+3. Press **`Option-Enter`** to open the file at that location
+4. Use **`Shift-Option-Enter`** to open in a split pane
+
+This uses the standard `editor: Open excerpts` and `editor: Open excerpts split` actions.
+
+## Why This Matters
+
+**Quick navigation**: Jump from conversation to code instantly.
+
+**Context switching**: Move seamlessly between review and editing.
+
+**Efficient workflow**: No need to manually search for files mentioned in diffs.
+
+**Split view support**: Open side-by-side for simultaneous comparison.
+
+## Example Use Cases
+
+- Jump to a file to review agent changes in full context
+- Navigate to related code after understanding agent's modifications
+- Open files in split view to compare before/after states
+- Quickly investigate why the agent made certain changes
+
+This makes the agent conversation feel more integrated with your editing workflow, reducing friction when moving between discussion and implementation.

tips/manage-built-in-agents.mdx

@@ -0,0 +1,53 @@
+---
+title: Remove and Manage Built-in Agents
+subtitle: All built-in agents are now removable via the ACP Registry
+category: ai
+difficulty: beginner
+tags:
+  - agent
+  - acp
+  - registry
+  - customization
+prUrl: 'https://github.com/zed-industries/zed/pull/50094'
+publishedAt: '2026-03-16'
+updatedAt: '2026-03-16'
+author: godruoyi
+authorUrl: 'https://github.com/godruoyi'
+---
+
+All of Zed's built-in agents (Claude, Codex, Gemini, etc.) have been migrated to the ACP Registry, which means you can now remove agents you don't use and manage them like any other extension.
+
+## What Changed
+
+Previously, built-in agents were hardcoded and always available. Now they're:
+- Listed in the ACP Registry alongside community agents
+- Removable if you don't need them
+- Reinstallable from the registry at any time
+- Managed through the same interface as third-party agents
+
+## How to Manage Agents
+
+1. Open the Agent Panel
+2. Click on agent settings or the registry icon
+3. View all installed agents (including built-in ones)
+4. Remove unwanted agents with the uninstall button
+5. Reinstall from the registry if needed later
+
+## Why This Matters
+
+**Cleaner workspace**: Remove agents you never use from the interface.
+
+**Reduced clutter**: Agent picker only shows relevant options.
+
+**User control**: Treat built-in agents like any other extension.
+
+**Consistent management**: One interface for all agents regardless of source.
+
+## Example Use Cases
+
+- Remove Gemini if you only use Claude
+- Uninstall Codex if you prefer other models
+- Simplify the agent picker to just your preferred agents
+- Reinstall agents when your workflow changes
+
+This change gives you complete control over your agent setup, letting you tailor Zed's AI features to your specific needs and preferences.