T50-Systems builds focused software products, AI-oriented developer tooling, and operational automation. Visit t50.systems for the canonical public website.
| Project | Purpose | Topics | Intended users | Status |
|---|---|---|---|---|
pi-anchor-edit-core |
Shared TypeScript anchor-editing core for Pi hashline read/edit and smart-edit packages. | developer-tools, editing, hashline, library, pi, typescript |
Editing-tool maintainers | Active |
pi-compaction-improvement |
Pi extension for proactive autocompaction, richer summaries, validation contracts, and safe fallback. | automation, compaction, context-management, pi, pi-extension, typescript |
Long-running Pi sessions | Active |
pi-fff-plus |
Safer FFF-powered file and content search tools for Pi across Windows and multi-root workspaces. | developer-tools, fff, pi, pi-extension, search, typescript |
Pi users on Windows and multi-repo workspaces | Active |
pi-github-admin |
Pi-native GitHub admin tools for repositories, branch protection, issues, releases, PRs, and verification. | automation, devops, github, pi, pi-extension, typescript |
Maintainers automating repository operations | Active |
pi-hashline-edit-plus |
Cross-platform Pi read/edit override using hashline anchors to make file edits safer and recoverable. | developer-tools, editing, hashline, pi, pi-extension, typescript |
Pi agents and extension authors | Active |
pi-smart-edit |
Smart Pi editing helpers for stale-anchor recovery, semantic replacements, and retryable hashline edits. | developer-tools, editing, pi, pi-extension, stale-anchors, typescript |
Pi extension and automation authors | Active |
pi-thread-goal |
Pi-native Claude-style /goal extension with branch-aware state, guarded tools, and automatic continuation. | agent, goal, pi, pi-extension, typescript, workflow |
Pi users running multi-turn tasks | Active |
pi-work-guard |
Memory-safe Pi workflow guard for bounded shell output, checkpoints, phases, and file-size budgets. | developer-tools, pi, pi-extension, safety, typescript, workflow |
Pi users operating in large repositories | Active |
Private product and research repositories are intentionally omitted from the public directory.
- Read the target repository README and contribution guidance before starting.
- Use its issue forms for bugs, features, and maintenance requests.
- Follow the organization Code of Conduct.
- Ask support questions through the repository's documented channel.
Report vulnerabilities privately through the affected repository's Security tab. If that is unavailable, use organization-default private vulnerability reporting. Never disclose exploit details, credentials, customer data, or private session files in public issues.
The community policy maintainer reviews the approved manifest and generated directory quarterly and after public repository launches, archives, or renames. Repository descriptions and topics are refreshed from public GitHub metadata through a review-only pull request.