🔗 pi-umans-provider

Coding-optimized models through UMANS

A pi provider extension with reasoning, vision, and live plan status.

Features

• OpenAI-compatible API - Uses UMANS's /v1/chat/completions endpoint
• Reasoning models - reasoning_effort-controlled thinking, surfaced as reasoning_content
• Vision models - Image input on all models
• Tool use - Function calling support across all models
• Streaming - Real-time token streaming
• Subscription-based - All models included in your plan, no per-token cost
• Usage status bar — Displays your plan, concurrent sessions, and remaining requests in the pi footer

Available Models

| Model | Base | Context | Vision | Reasoning | Max Output | |-------|------|---------|--------|-----------|------------| | Coder | Kimi K2.7-Code | 262K | ✅ | ✅ | 33K | | DeepSeek V4 Flash (experimental) | DeepSeek-V4-Flash | 1.0M | ❌ | ✅ | 393K | | Flash | Qwen3.6-35B-A3B | 262K | ✅ | ✅ | 33K | | GLM 5.2 | GLM-5.2 | 406K | ❌ | ✅ | 131K | | Kimi K2.7 Code | Kimi K2.7-Code | 262K | ✅ | ✅ | 33K | | Kimi K3 | Kimi K3 | 1.0M | ✅ | ✅ | 131K | | Qwen3.6 35B A3B | Qwen3.6-35B-A3B | 262K | ✅ | ✅ | 33K |

Note: umans-flash-beta is deprecated (sunset 2026-06-07). Use umans-flash instead. umans-qwen3.6-35b-a3b is a technical alias for umans-flash.

Installation

Option 1: Using pi install (Recommended)

Install directly from GitHub:

pi install https://github.com/monotykamary/pi-umans-provider

Then set your API key and run pi:

# Recommended: add to auth.json
# See Authentication section below

# Or set as environment variable
export UMANS_API_KEY=your-api-key-here

pi

Get your API key from code.umans.ai.

Option 2: Manual Clone

1. Clone this repository:

   git clone https://github.com/monotykamary/pi-umans-provider.git
   cd pi-umans-provider

2. Set your UMANS API key:

   # Recommended: add to auth.json
   # See Authentication section below
   
   # Or set as environment variable
   export UMANS_API_KEY=your-api-key-here

3. Run pi with the extension:

   pi -e /path/to/pi-umans-provider

Authentication

The UMANS API key can be configured in multiple ways (resolved in this order):

1. auth.json (recommended) — Add to ~/.pi/agent/auth.json:

   { "umans": { "type": "api_key", "key": "your-api-key" } }

   The key field supports literal values, env var names, and shell commands (prefix with !). See pi's auth file docs for details.
2. Runtime override — Use the --api-key CLI flag
3. Environment variable — Set UMANS_API_KEY

Get your API key from code.umans.ai.

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | UMANS_API_KEY | No | Your UMANS API key (fallback if not in auth.json) |

Configuration

Add to your pi configuration for automatic loading:

{
  "extensions": [
    "/path/to/pi-umans-provider"
  ]
}

Usage

Once loaded, select a model with:

/model umans umans-coder

Or use /models to browse all available UMANS models.

Recommended Models

• umans-coder — Best for complex, coding-heavy workloads. Optimized for coding agents.
• umans-flash — Fastest model for low-latency iteration with tools.
• umans-kimi-k2.7 — Moonshot's Kimi K2.7-Code for the hardest, multi-step coding tasks. Reasoning is always on.

Reasoning Effort

For reasoning models, control thinking depth:

/reasoning high

Levels: off, minimal, low, medium, high (default: medium). off disables reasoning (maps to reasoning_effort: none); minimal is mapped to the nearest UMANS level.

Usage Status Bar

Once authenticated, the pi footer shows your UMANS account status:

Code Max (Founding Seat) | ⟠ 1/4

• Plan name — Your current subscription plan
• ⟠ N/M — Active concurrent sessions / max concurrent sessions
• ⇄ N — Remaining requests in the current window (shown when limited)

The concurrent-session count is tracked locally: it's optimistically incremented the moment an agent run starts (no API call needed — the server has a brief registration lag anyway), reconciled with UMANS's /v1/usage endpoint after each agent run ends, and lightly polled while idle so the baseline stays fresh. The plan name and request budget are fetched on session start and model selection.

API Compatibility

The UMANS API follows OpenAI conventions with these differences (handled via patch.json and before_provider_request hook):

| Aspect | OpenAI Native | UMANS | |--------|-------------|-------| | Reasoning control | reasoning_effort | reasoning_effort (none/low/medium/high; default medium) | | Developer role | Varies | ❌ Not supported (use system role) | | Reasoning content | reasoning_content | reasoning_content (DeepSeek-style field) | | requiresReasoningContentOnAssistantMessages | — | ✅ Required — preserves thinking in history | | Pricing | Per-token | Subscription-based ($0/M) |

The extension also sanitizes orphaned tool_calls in conversation history. Context compaction can drop tool result messages while keeping the assistant message that made the tool call, causing a 400 error from the API. The before_provider_request hook detects this and inserts synthetic tool results.

Updating Models

To refresh the model list from the UMANS API:

npm run update-models

This fetches from /v1/models/info, updates models.json, and regenerates the README model table. Idempotent — safe to run repeatedly.

API Documentation

• UMANS: https://code.umans.ai
• OpenAI-compatible endpoint: https://api.code.umans.ai/v1
• Models endpoint: https://api.code.umans.ai/v1/models
• Models info: https://api.code.umans.ai/v1/models/info
• Usage endpoint: https://api.code.umans.ai/v1/usage

License

MIT