When model.maxTokens is 0 (unset/unknown), omit maxTokens from the Bedrock ConverseStream inferenceConfig instead of sending 0. Bedrock's inferenceConfig.maxTokens is optional — when omitted, the model uses its own internal default. This is optimal for Bedrock's token quota management: - At request start, Bedrock reserves input_tokens + max_tokens from your TPM quota - For Claude 3.7+ models, output tokens have a 5x burndown rate - Sending an unnecessarily high maxTokens wastes TPM capacity during the reservation window, reducing concurrent request throughput - Omitting it lets Bedrock use the model default (~4096 for Claude), matching expected output sizes and maximizing quota utilization Also applies the same conditional pattern to temperature — only include it in inferenceConfig when explicitly set. Changes: - simple-options.ts: Use ?? instead of || so explicit 0 is preserved; return undefined when model.maxTokens is 0 (unset) - amazon-bedrock.ts: Spread maxTokens and temperature into inferenceConfig only when defined Fixes #3399
pi.dev domain graciously donated by
![]()
exe.dev
New issues and PRs from new contributors are auto-closed by default. Maintainers review auto-closed issues daily. See CONTRIBUTING.md.
Pi Monorepo
Looking for the pi coding agent? See packages/coding-agent for installation and usage.
Tools for building AI agents and managing LLM deployments.
Share your OSS coding agent sessions
If you use pi or other coding agents for open source work, please share your sessions.
Public OSS session data helps improve coding agents with real-world tasks, tool use, failures, and fixes instead of toy benchmarks.
For the full explanation, see this post on X.
To publish sessions, use badlogic/pi-share-hf. Read its README.md for setup instructions. All you need is a Hugging Face account, the Hugging Face CLI, and pi-share-hf.
You can also watch this video, where I show how I publish my pi-mono sessions.
I regularly publish my own pi-mono work sessions here:
Packages
| Package | Description |
|---|---|
| @mariozechner/pi-ai | Unified multi-provider LLM API (OpenAI, Anthropic, Google, etc.) |
| @mariozechner/pi-agent-core | Agent runtime with tool calling and state management |
| @mariozechner/pi-coding-agent | Interactive coding agent CLI |
| @mariozechner/pi-mom | Slack bot that delegates messages to the pi coding agent |
| @mariozechner/pi-tui | Terminal UI library with differential rendering |
| @mariozechner/pi-web-ui | Web components for AI chat interfaces |
| @mariozechner/pi-pods | CLI for managing vLLM deployments on GPU pods |
Contributing
See CONTRIBUTING.md for contribution guidelines and AGENTS.md for project-specific rules (for both humans and agents).
Development
npm install # Install all dependencies
npm run build # Build all packages
npm run check # Lint, format, and type check
./test.sh # Run tests (skips LLM-dependent tests without API keys)
./pi-test.sh # Run pi from sources (can be run from any directory)
Note:
npm run checkrequiresnpm run buildto be run first. The web-ui package usestscwhich needs compiled.d.tsfiles from dependencies.
License
MIT