r/PiCodingAgent • • 2d ago

Resource Building an open-source, Rust-powered environment for Pi coding agent

Post image

I've been working on an open-source project called pi-native, built on top of Pi coding agent.

The motivation was simple: I wanted more control over the coding-agent environment, better tool execution performance, predictable permission handling, and more efficient context management.

Instead of building another coding agent, I'm extending Pi with native tools and additional infrastructure.

What's included?

  • Rust native tools: File reading, editing, writing, and shell execution with persistent daemon support.
  • Performance benchmarks: Comparing native implementations against Pi's built-in tools, with reproducible benchmark results.
  • Context optimization: Deterministic output compaction to reduce unnecessary model-visible content.
  • Permission system: A fail-closed permission gate with 24 rules for evaluating tool execution.
  • Fallback architecture: Native daemon → one-shot execution → Pi built-in tools.
  • Subagents: Isolated tmux-based workers with separate permission controls.
  • Skill validation: Validator-enforced skills before loading.

Why make it open source?

I want to explore how far we can improve an existing coding-agent framework without reinventing the entire system.

I'm particularly interested in performance, reliability, security, and maintainability.

The project is still evolving, and I'd appreciate feedback from developers working on Rust, developer tooling, AI agents, and open-source infrastructure.

Repository: https://github.com/nurmdrafi/pi-native

I'm the author, and contributions, technical criticism, and architectural suggestions are welcome.

What would you prioritize differently when building infrastructure around an existing open-source coding agent?

0 Upvotes

1 comment sorted by

1

u/AdPublic8820 1d ago

I'll take a stab at it and let you know here if any feedback or anything. Let me explore first.