Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature: add Pi coding-agent harness support

Open
#230 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

Start with the bl mcp connect --help entry point and compare how the existing agent targets are exposed. Verify the supported Pi MCP configuration contract, then use the acceptance criteria to check dry-run output, idempotency, secret redaction, compatibility errors, and preservation of existing targets.

Written by the indexing model from the issue text.

Description

Please add first-class Pi coding-agent harness support to Bailian CLI integrations. In CLI 2.0.1, bl mcp connect --help exposes fixed targets (Codex, Claude Code, Cursor, Qoder, QwenWork, Qwen Code, Gemini, OpenCode, OpenClaw, DeepSeek Harness, ZCode, WorkBuddy, and all) but no Pi target. Pi has its own provider registry and MCP configuration, so users must configure Alibaba Pi support separately. Proposed: add a pi target when Pi has a supported MCP configuration contract, or add a safe bl pi adapter/export command that emits provider IDs, endpoint/model metadata, and setup instructions without printing or persisting secrets. Support Coding Plan and DashScope Cloud selection, China/international endpoints, dry-run/idempotent updates, secret redaction, and explicit process/session contract boundaries for b00t-managed Pi interactions (terminate on timeout/violation; renew only explicitly). Acceptance: bl mcp connect --agent pi configures a supported Pi MCP file or returns a documented compatibility error; dry-run shows non-secret changes; existing targets remain compatible; tests cover idempotency and secret redaction. No credentials are included in this request.

Dominant language
TypeScript
Stars
333
Forks
28
Avg merge
1d 5h
Merged PRs (30d)
37

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelstudioai/cli

All issues in modelstudioai/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.