Skip to main content
rafaygenAI

Software & code

Beta

Give your next software project a stronger starting point.

Explain the behaviour you need and work through the implementation in manageable steps, with tests that show what was checked.

In beta In Work, describe a small coding task in a Cloud project. RafayGen writes standard-library Python files, runs their unittest suite, and shows the changed files with a trusted pass result.

Beta: keep tasks small. RafayGen writes standard-library Python with a unittest suite. It cannot install packages, push to a repository or deploy.

Sign-in required. Available on the Free plan. Model choice depends on your plan.

Review the result before you rely on it.

RafayGen example · 18 November 2026

Example

Task, as typed in Work

Create asset_tracker.py: an internal asset tracker with add, search by name, filter by status and a detail view function, plus test_asset_tracker.py with unittest tests for each function, and run the tests.

Work’s reply

Your changes are ready. The checks passed.

Changed files

  • asset_tracker.py
  • test_asset_tracker.py

Test result, from the task’s run record

python -m unittest -v

Ran 18 testsOK

Trusted test runner · 18 passed · 0 failed · exit code 0

asset_tracker.pyLines 62–75

    def search_by_name(self, name: str) -> list[Asset]:        """Search assets by name (case-insensitive partial match).Lines 64–70 left out (the rest of the docstring)        name_lower = name.lower()        return [            asset for asset in self._assets.values()            if name_lower in asset.name.lower()        ]

test_asset_tracker.pyLines 74–79

    def test_search_by_name_case_insensitive(self):        """Test that search is case-insensitive."""        self.tracker.add("A001", "Laptop", AssetStatus.ACTIVE)        results = self.tracker.search_by_name("laptop")        self.assertEqual(len(results), 1)
RafayGen example from a real Work task on a Free account, 18 November 2026: the task as typed, Work’s reply, two short excerpts of the files RafayGen wrote (quoted exactly, with their line numbers) and the test result from the task’s run record. The tests in this task passed; that shows only what those tests check.
Contents

What you can do

  1. Standard-library Python files, written into a Work project with a Cloud environment.

  2. A unittest suite that RafayGen runs, with the result recorded by a trusted test runner.

  3. A list of the changed files, which you can open and read in Work.

How it works

From your brief to a result you can review, in three stages.

  1. Define the behaviour

    In a Work project with a Cloud environment, describe the functions you need and ask for unittest tests that check each one.

  2. Implement the change

    RafayGen writes standard-library Python files in the project and runs their unittest suite.

  3. Inspect the evidence

    Work lists the changed files and says whether the checks passed. Read the code and its tests before you use them.

Example brief

Brief

Create asset_tracker.py: an internal asset tracker with add, search by name, filter by status and a detail view function, plus test_asset_tracker.py with unittest tests for each function, and run the tests.

We ran this brief when we checked this tool on .

Name the files, the functions and the tests you want, and end with “run the tests”. Keep the task small.

Formats

You provide

  • A task description, typed in a Work project with a Cloud environment

You get

  • Standard-library Python files in the project
  • A unittest run, with a pass result from a trusted test runner when the tests pass
  • A list of the changed files

File formats

  • Python (.py)

Questions

What can I ask for in the beta?

A small task in a Work project with a Cloud environment: standard-library Python files with a unittest suite that RafayGen runs. The example brief on this page is the task we checked.

Which plans include it?

You need to sign in. The beta is available on the Free plan, and the models you can choose depend on your plan.

Can RafayGen push, open pull requests or deploy?

No. It writes files in the Work project and runs their tests; it does not push, open pull requests or deploy.

Is the code ready for production?

Not automatically. A pass shows only that the task’s own tests passed. Review the code, its behaviour and its security before you rely on it.

Limits to know before you start

  • This beta is for small tasks: standard-library Python files with a unittest suite. Larger applications are outside it.
  • RafayGen does not push code, open pull requests or deploy.
  • Projects have no network access and cannot install packages.
  • Write tests with Python’s unittest: other test styles, such as pytest, do not count towards the pass result.
  • A command can run for up to 30 seconds and a task for up to four minutes.
  • Work has no way to delete a project yet.
  • Passing tests cover only the cases they check. Review the code before you use it.

Software & code in RafayGen

Beta: keep tasks small. RafayGen writes standard-library Python with a unittest suite. It cannot install packages, push to a repository or deploy.

Sign-in required. Available on the Free plan. Model choice depends on your plan.

Review the result before you rely on it.