Factory Droid combines an interactive development session with a separate run from the command line. Suitable for tasks where the agent needs project context and clear result.

The front page of Factory Droid documentation. Open the source

One-time launch from the terminal

You can use Droid in a conversation or run it as a one-off command to get a result without an ongoing session. The droid exec documentation shows how to pipe in input and choose an output format. This is useful for processing a prepared diff or a draft document. Before automating the task, decide whether the agent only needs to read the input or should also run project commands.

The output has a format, but this does not follow the correctness of the content. If the result is read by another script, provide verification of required fields and the case when the agent returned an incomplete answer.

From diff to release notes

In the training branch, the limit on the length of the product name was changed and a check of old records was added. Pass the diff and ask to write out only noticeable changes for the user. Set the structure with a brief description and a link to the change line. As a result, it should be clear where the interface behavior has changed and in which cases the new limit is applied.

Check the wording with the test and code before using the text. Changing the check while saving may not affect the import of old records. Clarification is essential for the reader and is easily lost in a short draft.

Permits and expenses

Factory documents autonomy settings, execution environments, and model selection. When running in CI, check which secrets and directories the process can access. If a diff is the only input needed, pass it in and restrict access to the rest of the project.

Suitable tasks

Prepare release notes from a set of changes
Run a one-time code analysis from the automation scenario

Features

Strengths

There is an interactive and automatic start
Help describes machine-readable output formats

Things to consider

Limitations

Agent access to tools should be limited to the task
The team checks which models, files and cloud resources are involved in the session

Selection and conditions

Free access: Not confirmed
Trial period: Not confirmed
No sign-up required: Not confirmed
Russian interface: Not confirmed
Local installation: Not confirmed
API: Yes

“Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms.

Input formats: Code, Text
Result: Code, Text

Terms

There are individual plans. Consumption depends on the model and mode, and the conditions for connecting your own key are specified separately. The team checks which models, files and cloud resources are involved in the session

From task to first result

Practical example

Task: Prepare release notes from a set of changes
What to prepare: Diff educational branch and structure of short notes to release.

Task brief or prompt

List the changes that the user sees. Add a link to the diff string to each item. Find out if the new limit affects old records.

Expected result

Draft notes indicating the changes in the code being checked.

How to check the result

Check the statements with tests and diff.
Make sure that no secrets or internal addresses are included.

An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted.

Check details

Official sources

This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use.

Factory Droid.