Build a feature
Turn a product request into code that follows the patterns already established in the repository.
OpenWaya CodeCLI + Desktop · early access
WayaCode
Turn ambition into software.
Build a feature, fix a bug, refactor a service, or review risky code. WayaCode works through the repository, runs the right checks, and returns the diff, decisions, and evidence your team needs to ship.
waya:task:v1:7K2…Working
Fix duplicate checkout requests and prove the regression is covered.
- ExploreRelevant request path mapped
- Plan3 bounded changes accepted
- CodeEditing idempotency boundary
- ProofFocused test waiting
- ReviewCold diff review waiting
3 files+41−12Approval boundary intact
Start here
Install the CLI and give it a real task.
WayaCode is available to approved early-access testers from the source repository. Set up the CLI, open the project you want to change, and start with a clear outcome.
Public packages and signed Desktop downloads will be added here as they clear release verification.Install WayaCode CLIEarly access
curl -fsSL https://openwaya.africa/code/install.sh | shRun your first task
cd /path/to/your-project
waya plan "Fix the checkout bug and add a regression test"
waya run "Fix the checkout bug and add a regression test"ShipBuild features and fixes in the codebase you already have
VerifyBring focused test results back with the diff
ChooseMatch each stage to a live model on OpenWaya
ControlKeep permissions and approvals visible throughout the task
Give it the backlog
Start with the work your team needs finished.
WayaCode takes a bounded engineering task and carries it through the repository. You stay close enough to guide the work without having to drive every edit and command.
Fix a bug
Trace the failure to its source, make the smallest safe change, and add regression coverage.
Refactor or upgrade
Update dependencies, reshape a subsystem, or carry a change across every affected file.
Review a change
Inspect a finished diff with independent context and surface bugs, risk, and missing proof.
How WayaCode works
From a task to a reviewable change.
Describe the result you need. WayaCode finds the relevant code, plans the work, implements it, runs focused checks, and reviews the finished diff. One task record keeps the people, models, tools, and evidence aligned from start to finish.
- 01
Explore
Find the code, instructions, and dependencies that matter to the task.
- 02
Plan
Break the outcome into clear changes and checks before editing.
- 03
Build
Make the change inside the repository and record the work as it happens.
- 04
Verify
Run focused checks and connect their results to the requested outcome.
- 05
Review
Read the finished diff with fresh context and return an explicit delivery state.
OpenWaya models
Match the model to the work.
Choose a model yourself or let routing put speed, context, and deeper reasoning where they add the most value. The task history and evidence stay together as models change.
RoleSelectionWhy
Explore
fast · long contextMap the repository and collect the context the change needs.Implement
frontier codingBring stronger coding and reasoning to the change itself.Review
fresh contextInspect the finished work without inheriting the builder's assumptions.Available in early access
Start in the terminal. See everything in Desktop.
CLI and Desktop run the same task engine and share the same task state. Start work from the command line, then open the visual workspace when you want to follow parallel tasks, inspect a diff, use a terminal, or handle an approval.
CLI
Open a repository, start a task, follow its progress, inspect the evidence, and commit from a scriptable terminal workflow.
Desktop
Manage parallel tasks, diffs, terminals, approvals, evidence, and recovery from one visual workspace.
Coming next
CloudIsolated remote execution for long-running work.
Editor and partner integrationsThe same task engine inside editors and engineering tools.
Built for accountable work
See what happened before you trust the result.
Useful autonomy needs clear boundaries and proof. WayaCode keeps authority, activity, verification, and delivery state attached to the task so your team can review the work on its merits.
Scoped authority
WayaCode works inside the repository access and approval rules you set.
Reviewable evidence
Inspect the activity, diff, checks, approvals, cost, and final task state.
Durable tasks
Resume, retry, or hand off work with one authoritative task history.
Bring the next ticket
Give WayaCode a real task.
Start with the CLI or Desktop, connect a repository, and see how a task moves from request to reviewable code.