Skip to content
WeHarness Docs

Quickstart

This guide takes about ten minutes of your own time; WeHarness reads, plans and checks while you wait. You need a WeHarness account and a workspace with credits. See Getting access.

  1. Open your workspace.

    Sign in at app.weharness.io. Your pilot workspace opens. The workspace switcher at the top of the sidebar changes workspace or creates a new one.

    Open Usage & billing in the sidebar to see your credits. A new workspace has none until WeHarness adds them: write to info@weharness.io. See Credits and usage.

  2. Bring your code.

    From GitHub (owners and admins):

    1. In the sidebar, open Integrations and select Add account or organization.
    2. On GitHub, install the WeHarness GitHub App on your personal account or an organization, and choose the repositories WeHarness may use. In an organization, an owner of the organization may have to approve the installation.
    3. Back in WeHarness, the account and its repositories appear in Integrations and in the repository picker of New session.

    See GitHub.

    Without GitHub: start the session in step 3 with No repository — start from an idea. Then open the Context tab in the session’s work panel and select Choose a folder or Upload a zip. Your browser reads the files; check the preflight (what is included and what is left out, such as secrets and node_modules) and confirm. See Project context.

  3. Start a session.

    Select New session. Choose the repository; the branch chip shows its default branch, and you can pick another. Write what you want in your own words, in any language. For example:

    Our support agent should refund only orders under 30 days old, and only after a support lead approves.

    Send it. WeHarness reads the repository, answers and asks what it needs. You can attach up to ten files with the paperclip. See Sessions.

  4. Get a plan.

    Ask WeHarness to build it, or type /plan. The Plan tab shows the requirements, the acceptance tests and two to four options, with the checks each passed. If WeHarness asks questions, answer them in the chat or go with its suggested answers. Ask for changes in the chat; each change is a new version. See Plans and approval.

  5. Approve the plan.

    An owner or admin selects Approve plan in the Plan tab. WeHarness builds the plan in the session’s draft, step by step, while you watch in the chat. Your repository does not change. Open Changes to see every edit.

  6. Approve the environment and check the draft.

    WeHarness proposes in the chat how your repository is set up and tested (for example npm ci and npm test). An owner, admin or member selects Approve environment once for the repository. Before a push, a clean check runs those commands on the exact draft in a fresh sandbox. The Checks tab shows the result. See Cloud work.

  7. Push a pull request.

    When the draft is ready, WeHarness asks to push (or type /push). An owner, admin or member selects Approve and push. WeHarness writes one commit to a weharness/… branch and opens a pull request against your branch. It never merges. The session header shows the pull request and its state, and the PR tab shows its CI checks.

    For an uploaded project, download a Patch from Changes instead.

Next steps

Section titled “Next steps”