floatboat
Open navigation menu

Earendil Works: Pi and Agent Tooling

Explore Earendil Works through Pi, an extensible agent harness and toolkit. Understand the current upstream, reusable runtime libraries, package-based customization, and the responsibilities that remain with the host environment.

About Earendil Works

Earendil Works is the current organization hosting the Pi project. Its public repository brings together a coding agent and the libraries that support it. The useful perspective is the relationship between a finished interactive tool and the smaller runtime components developers can study or reuse.

Pi’s approach emphasizes a small extensible core and workflow-specific customization. Extensions, Skills, templates, and themes can be assembled into packages. This makes the publisher relevant to both people configuring their own coding environment and developers investigating agent infrastructure.

Earlier references use badlogic/pi-mono; the current upstream is earendil-works/pi. The new address is an upstream migration of the same project. Evaluate each runtime library and extension by its own responsibilities, especially where the host environment must supply execution restrictions.

Earendil Works Projects

Explore the project as a reference for designing your own agent workflows, with attention to task structure, extensions, and execution boundaries.

Related Agent Publishers

Explore other teams developing agent runtimes, coding tools, and reusable working environments.

Earendil Works FAQ

Why is Pi attributed to Earendil Works?
The current repository is earendil-works/pi. Older badlogic/pi-mono links redirect there; use the current upstream to check maintainers, releases, and documentation.
Is the old Pi repository a different product?
The repository move itself does not establish a separate product. Use the current project documentation and avoid counting the old and new addresses as two independent tools.
Who benefits from the reusable libraries?
Developers who need model-provider interfaces, an agent core, conversation runtime, or terminal UI can inspect the relevant component instead of adopting every part of the CLI.
Are all workflow features part of Pi’s core?
No. Pi adds capabilities through extensions and packages. Community packages have their own maintainers and support scope, separate from the official core.
Does an open runtime imply built-in isolation?
No. Pi explicitly documents that access restrictions are not a built-in permission system. Check how the chosen host environment provides the boundaries required by the work.
What does MIT mean for third-party extensions?
Pi’s MIT source license does not establish the license or trustworthiness of every extension. Check the source, maintainer, and authorization of each package separately.

Study Pi Workflow Design

Read the project guide to identify useful mechanisms and plan a small workflow experiment.

View Pi