Agree on the work.
Let agents build.
Plan code changes together, put agents to work, and review every pull request in one shared workspace.
Open ElwingFrom a shared idea to a reviewed change.
Interactive exampleAdd CSV export
Give people a spreadsheet-ready export, with the same access rules as JSON.
What needs to be true
- Keep JSON exports working
Existing API clients keep their current response.
- Respect workspace permissions
Check access when creating and downloading an export.
- Handle real-world CSV data
Escape commas, quotes, and newlines in cell values.
See the implementation steps
- Add a CSV serializer with tests for escaped values.
- Connect the format option to export jobs and downloads.
The plan stays
with the work.
Decide what the change should do, what it must preserve, and how you’ll check the result.
Elwing keeps those answers in a shared plan, alongside the code that informed it. Your team can review the same version before an agent starts building.
src/exports.tsdocs/permissions.mdResearch cites the files it reads, at the commit you started from.
Use the same permission checks for every export format.
Example requirement, saved with the planYour team keeps
the final say.
Give agents room to work, with clear points for your team to review the result.
- Approve a specific plan.
- The agent runs the version your team approved. Requirements, decisions, and review comments stay on record.
- Review one change at a time.
- Each plan step becomes a draft pull request. Elwing checks GitHub CI before the next step starts.
- Keep the final say.
- Pause a run, answer a question, or send work back. You choose when to merge and deploy.
Start with one
code change.
Open your workspace with GitHub.
Connect a repository and work through a plan.
Elwing is in active development. Model usage is billed to the provider account you connect.