# Regenerate Grpc Stubs

Regenerate Python + TypeScript gRPC stubs after editing proto files.

- Repository: https://github.com/GetBindu/Bindu (10015 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-09-06
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add GetBindu/Bindu --skill regenerate-grpc-stubs -g -a claude-code -y`
Codex: `npx skills add GetBindu/Bindu --skill regenerate-grpc-stubs -g -a codex -y`
Cursor: `npx skills add GetBindu/Bindu --skill regenerate-grpc-stubs -g -a cursor -y`
Gemini CLI: `npx skills add GetBindu/Bindu --skill regenerate-grpc-stubs -g -a gemini-cli -y`

## Description

Regenerate Python + TypeScript gRPC stubs after editing proto files. Use when proto/*.proto changes, imports from bindu.grpc.generated fail, CI reports generated-code drift, or HandleMessages calls fail with proto mismatch.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Regenerate gRPC Stubs

## Overview

Bindu's cross-language agents share one proto file: [proto/agent_handler.proto](../../../proto/agent_handler.proto). Two generated stub trees must stay in sync with it:

- `bindu/grpc/generated/`, Python stubs for the core
- `sdks/typescript/src/generated/`, TypeScript stubs for the SDK

Both languages must be regenerated **together** and committed in the same PR as the proto change. A proto change without matching stubs leaves main broken for anyone who pulls.

## Inputs

- `<proto_file>`: usually `proto/agent_handler.proto`, or whatever file was modified under `proto/`.

## Safety

- Do not edit files under `bindu/grpc/generated/` or `sdks/typescript/src/generated/`. Changes will be overwritten by the next regeneration.
- Do not split the proto change and the stub regeneration across PRs. They must land atomically.
- If the proto change is breaking (removed fields, renamed RPCs, changed message types), flag it in the PR description, existing clients will break.

## Execution Contract

1. Confirm the proto change is intentional and minimal.
2. Regenerate both Python and TypeScript stubs via the project's script.
3. Verify both stub trees compile.
4. Run the gRPC integration tests.
5. Commit proto + both generated trees together.

## Steps

### 1. Review the proto diff

```bash
git diff proto/agent_handler.proto
```

For each change, classify:
- **Additive** (new RPC, new field with a new tag), safe, backward-compatible.
- **Breaking** (removed field, renumbered tag, renamed RPC), needs a coordination note and a version bump plan.

### 2. Regenerate all stubs

```bash
bash scripts/generate_protos.sh all
```

The script handles both languages and fixes Python import paths. It is the single source of truth, do not run `grpc_tools.protoc` or `grpc_tools_node_protoc` by hand.

### 3. Verify Python stubs

The rest: https://github.com/GetBindu/Bindu/blob/HEAD/.agents/skills/regenerate-grpc-stubs/SKILL.md