Task in.Issue in.Review in. Build out.Plan out.Fix out.
The forward deployed engineer's toolchain for GitHub. Write the task in plain words, in any repository you carry. AISWEC answers with a plan; you approve it; it builds behind that repository's own CI gates and answers your review with commits.
Open source · read every line that runs in your repository
- REFINE
- APPROVE
- BUILD
- REVISE
- MERGE
- TASK IN → BUILD OUT
- THE FORWARD DEPLOYED ENGINEER'S TOOLCHAIN
- EVERY REPO, ONE INBOX
- FULL DEVELOPER AUTOMATION
- NOTHING NEW TO LEARN, IT IS GITHUB
- PUT YOUR CLAUDE SUBSCRIPTION TO WORK
- YOUR SECRETS NEVER LEAVE GITHUB
Two products. One engineer.
The agent is the engineer: it works inside your repository, on your own GitHub Actions. Suite is where you run it from. The agent works on its own; Suite drives it for every repository you carry.
-
OPEN SOURCE ·
GITHUB APP
AISWEC Agent
The GitHub App and the three workflows that do the work: refine posts a plan for an issue, build opens a pull request behind your own checks, revise answers your review with commits. Install the App, or host it yourself with your own key.
- refine · build · revise
- your Actions, your key
- FSL-1.1-ALv2
aiswec.com/agent · /agent/docs -
WEB APP ·
INSTALLS ON YOUR PHONE
AISWEC Suite
Where you drive the agent from: one inbox across every repository, plans to approve, changes to review, every run and what it spent. Set up and Remove are one button each, and your first project is free.
- one inbox
- approve from your phone
- first project free
aiswec.com/suite · /suite/docs
One task, start to finish.
You ask in plain words and approve the plan; AISWEC builds it on your own GitHub Actions and hands it back as a pull request for you to accept. Under a minute, best with the sound on.
Every customer's repository. One inbox.
A forward deployed engineer lives in other people's code: a client's API in the morning, their field app after lunch, the next client's data pipeline by evening. Install AISWEC on each repository and every one of them gets the same engineer, working by that repository's own rules, on its own Actions, behind its own gates. You run all of it from one place.
- #41Usage-based invoicesplan ready
- #38Retry failed webhookschanges ready
- #12Offline job list2 questions
- #7Backfill March orderschanges ready
- #88Sign in with Oktabuilding
-
Each repository keeps its own rules
Before it plans, AISWEC reads that repository's CLAUDE.md and README, and your own CODE.md, the rules you carry from client to client. It runs on the customer's Actions, and their secrets never leave GitHub.
-
One inbox across all of them
Suite gathers what waits on you from every project, grouped by project, freshest first: plans to approve, changes to review, questions to answer. Activity shows every run on every repository, and the model that ran it.
-
Work that crosses repositories
When the API's plan needs a change in the app, that step becomes a task in the app's repository in two clicks, linked back to the plan, and the plan goes on without waiting for it.
-
A new repository in one click
Set up writes the stages, the labels and the secrets in one commit; Remove takes them out again. A fix to AISWEC reaches every repository you run without a push to any of them.
You write product. It writes software.
Four steps on one repository, in two lanes: the white lane is you, the blue lane runs unattended on your own GitHub Actions. Your only verbs are write, approve, review and merge. Every hand-off is a GitHub resource you can read, a comment, a label, a pull request; never a hidden state.
-
Write the task
A title is enough. Label the issue aiswec, or file it as a task from Suite.
you · one line -
Refine
Reads the repository with read-only tools and posts the plan on the thread: scope, files, tests. Nothing is built yet.
sonnet · 40 turns · aiswec:refined -
Approve the plan
The first line of a comment: approve, lgtm, ship it. Anything else is feedback, and re-refines.
you · one comment · zero tokens -
Build
A branch, commits and a pull request on aiswec/issue-N, behind your own CI gates, three tries. Red gates leave a draft WIP PR flagged for you, never a quiet failure.
opus · 120 turns · aiswec:pr-open -
Review
Review it like anyone's: inline comments, review bodies, plain replies. All of it counts.
you · as many rounds as you like -
Revise
Every thread answered with replies and commits on the same pull request, until you merge.
opus · 120 turns · until you merge -
Merge
Yours, always. Nothing merges itself; your own Actions build and ship it.
you · merge · shipped
Scroll the diagram sideways to follow both lanes.
- Refine
- sonnet, 40 turns, 15 minutes. Read-only tools; the plan is posted on the issue, where you can read it.
- Build and revise
- opus, 120 turns, 40 minutes each, behind your own CI gates with three tries. Red gates leave a draft WIP PR for you.
- You
- Write, approve, review, merge. One comment approves, and approval costs zero tokens.
- The brakes
- aiswec:hold stops an issue in any state, even an approved one. aiswec:needs-human asks for you; any maintainer comment revives the stage.
Full automation. Nothing new to learn.
The engineering runs end to end on its own; what is left for you is GitHub as you already use it. Every step of both is an issue, a comment, a label or a pull request, written as aiswec[bot] and on the record.
-
Reads before it writes
The repository, with read-only tools, and the vendor's own docs at the version your lockfile pins. The plan says what the docs say and what changes because of it.
refine · read-only · docs at your version -
Asks when it matters
When an answer would change what you get, it asks, each question with options and the one it recommends. Pick, send, and it plans. Anything smaller it decides and says so.
options · one recommended -
Any stack, its own checks
A web app, a phone app, a command line or a service: it builds with what the repository already uses and proves it with the repository's own commands before the pull request opens.
build · your gates · three tries -
Answers every review
Inline comments, review bodies, plain replies: each is answered with a reply and commits on the same pull request, round after round, until you merge.
revise · until you merge
-
Approve with one comment
approve, lgtm or ship it as the first line, or one button in Suite. Approval costs zero tokens, and nothing merges itself.
you · one comment -
Your part, as a checklist
What only you can do, a token to make, a secret to add, a store setting, comes as a list of manual todos that says where. Suite holds Approve until it is ticked.
you · manual todos -
From your phone
Suite installs as an app and tells you when a plan or changes are ready. Approve on the way to the client, review at your desk.
you · installable · notifications -
Leave any time
Everything AISWEC does is a GitHub resource. Remove it from a repository and the code, the branches and the pull requests stay exactly where they are.
github is the database
File an issue tonight. Review a pull request with coffee.
Suite is the web app on top of the pipeline: one inbox across every project, approvals, reviews, runs. Sign in with GitHub and install on as many repositories as you carry. Set up is one button that writes the stages, labels and secrets. Remove is one button too.