What you'll hand it
The everyday jobs Pier is built for. Each one walks through how the agent reads, plans, and ships.
Add an API endpoint
Point Pier at your service and describe the endpoint. It finds the routing, the handlers, and the tests, then writes the change to match.
How it works →Explain a large repository
Drop into an unfamiliar codebase and ask. Pier maps the structure, the key modules, and how a request flows through the system.
How it works →Run a codebase-wide migration
Swap a library, rename an API, or change a pattern everywhere it appears. Pier finds every call site, edits them consistently, and keeps the build green as it goes.
How it works →Track down a failing test
Hand Pier a red test and let it dig: reproduce it, trace the failure to its root cause across files, fix it, and confirm the suite is green again.
How it works →Fix a failing CI build
Paste the red CI log and let Pier work backwards: reproduce the failure locally, find what broke, fix it, and confirm the pipeline goes green.
How it works →Write tests for untested code
Point Pier at a module with no coverage. It reads the behaviour, writes tests that match your existing style, and runs them to prove they pass.
How it works →Upgrade a dependency with breaking changes
Bump a major version and let Pier handle the fallout: read the changelog, find every broken call site, update them, and get the build passing again.
How it works →Keep exploring
Begin here
A gateway between people and intelligence. Join the early-access list and be first to ship with Pier.
1.45k devs and engineers ship with Pier daily