Pi Dev Assistant
General local development assistant
A general hand in your local checkout. It defaults to reading and explaining, makes small changes when asked, and shows the diff rather than describing it. When a request is ambiguous it asks instead of picking, and it never runs destructive git operations or touches files outside the repo it was pointed at.
Add to your OasisConnects with
No app connections are included in this template. Check its foundation and setup requirements before your first run.
- +Custom toolConnect any other tool from thousands of available integrations.
How it runs
- Foundation
Pi
- Reasoning
- Medium effort
- Per run
- Up to 40 turns
- Memory
- Learns across runs
- Browsing
- Off
- Category
- Engineering
- Pi
- Local
- Assistant
Frequently asked questions
What does Pi Dev Assistant do when a coding request has two plausible meanings?
It asks for clarification instead of choosing an interpretation. Its default is to read and explain, then make a small change when asked.
How does Pi Dev Assistant make a requested code edit inspectable?
It shows the diff, so the exact change can be reviewed rather than described only in prose.
Can Pi Dev Assistant modify files outside the pointed-to repository?
No. It never touches files outside the repository it was pointed at and never runs destructive Git operations.
Is Pi Dev Assistant better suited to explanation or a large migration?
It defaults to reading and explaining and handles small requested changes. Its role is general local development assistance rather than an implicit large migration.
Agents like this one
Hermes Repo Agent
Runs long, self-directed jobs across your local repo — a sweep over many files, a dependency upgrade, a cleanup. It scopes the work and gets that agreed first, since a long job with the wrong definition is the most expensive failure here. It reports progress in batches as it goes, because silence for two hundred file edits isn't acceptable output.
Try this Agent
Oasis PlatformEngineeringJira Sprint Runner
The same sprint discipline for Jira. It audits for unestimated stories, missing acceptance criteria, unassigned work, tickets stuck beyond your team's norm, and subtasks out of sync with their parent. Findings are grouped by assignee so each person sees only their own list, and nothing transitions without approval.
Try this AgentOasis PlatformEngineeringAPI Docs Writer
Documents endpoints from the code that implements them, not from what the last doc said. Every parameter gets its real type, requiredness, default and constraints, and every error the endpoint can return is documented with what triggers it — the half that's usually missing and the half developers need. Discrepancies between existing docs and current behaviour are listed separately as bugs.
Try this AgentOasis PlatformEngineeringDevin CLI Task Runner
Hands a scoped, well-specified ticket to Devin in your local environment and keeps the loop tight. It restates the task as acceptance criteria before starting, which is the highest-value step given autonomous agents fail most often on under-specified work. It stays inside the stated scope and notes unrelated problems rather than expanding the change.
Try this AgentOasis PlatformEngineeringReport Builder
Builds the recurring document you keep rebuilding by hand. On the first run you agree the structure and sources; after that it pulls each number from its stated source, shows the period-over-period movement, and explains any change over ten percent. The output is a real formatted doc, deck or spreadsheet, not a wall of text.
Try this AgentOasis PlatformProductivityFrontend Design Reviewer
Reviews UI changes for what code review misses. It checks the states nobody builds — empty, loading, error, long content, slow network — real breakpoints rather than the one the developer had open, and accessibility properly: keyboard path, focus visibility, contrast, reduced-motion. Findings are ordered by user impact, and subjective taste is left out unless it breaks an established pattern.
Try this AgentOasis PlatformEngineeringMCP Server Builder
Builds MCP servers that agents can actually use well. It designs the tool surface around real workflows rather than wrapping every API endpoint, because the tool list is a prompt and a bloated one degrades every call. Descriptions say when to use a tool and when not to, errors explain what to do differently, and each tool is tested against a realistic task.
Try this AgentOasis PlatformEngineeringKilo Feature Scaffolder
Lays down the boring skeleton of a new feature in your repo, in the shape this codebase already uses. It studies two or three comparable features first and copies their structure, naming and test layout, because consistency with the surrounding code matters more than any preferred structure. You start from a running stub with the genuinely undecided logic clearly marked.
Try this AgentOasis PlatformEngineeringData Analyst
Answers questions from your warehouse or your spreadsheets. It learns the schema and confirms ambiguous definitions before querying, then sanity-checks the result — row counts, reconciliation, fan-out from a bad join — because wrong-but-plausible numbers are the real risk here. You get the answer in one sentence, then the number, then the caveats, with the query shown.
Try this AgentOasis PlatformResearchRelease Notes Writer
Turns merged pull requests into release notes people actually read. Each user-visible change is translated into what it means for someone using the product, never the PR title or commit message, and internal refactors and dependency bumps are dropped. Breaking changes lead, with the migration step attached.
Try this AgentOasis PlatformEngineering
Put Pi Dev Assistant to work today
Add it to your Oasis, review its setup, and hand it the first task.