Skip to content

Engineering: code, with an agent.

Code lives in a team project, with its repository on GitHub. You open it in the browser, in Agents. The agent works on a branch of its own, in the chat the team already uses.

One chat.

Whoever writes the code and whoever reviews it sit in the same conversation as the agent. Corrections are said there, and stay for whoever arrives later.

From the repository to the merge request

An example. Every feature it names has its own page.

  1. Starting

    Connect GitHub.

    Whoever has “Keys” connects the organization’s app. The team’s project lives in its repository.

  2. Asking

    Write in the team chat.

    You tell the agent what to change. Colleagues read and answer there too.

  3. Working

    The agent edits and commits.

    On a working branch, not on the main one. Every step is a commit.

  4. Reviewing

    The merge request.

    When it is done the agent opens it, and the team reads it.

  5. Checking

    The checks on GitHub.

    The agent reads the result of the checks that run on the branch and writes in the chat what is red.

Frequently asked questions

Who pays for the model?

Whoever uses it, with their own key, and a cap per person.

Can I connect other tools?

Yes: the services you already use link to Pan, and the ones that write ask permission.

Can another assistant that writes code work here?

Yes: with a code you give it, an outside assistant works in Fallthere like you, and every action stays in the log.

Let’s see it together.

We show it to you live.

Request a demo