Skip to content

Pan works in your code.

A code project is a space’s folder, with its repository on GitHub. Pan on code works there on a branch of its own, asks permission before leaving the folder or running a command, and also tests the site it builds: it opens it, looks at it, clicks in it.

It asks, as a colleague would.

In the project’s folder it writes. Outside the folder, and for every command, it asks: “May I run “npm test”?”. Answer Yes, this time, Yes, for this conversation or No. If you do not answer for ten minutes, it is a no.

  • A branch of its own for each session, never the main one.
  • One push, never forced.
  • A draft merge request that waits for a person.

It tests the site it builds.

With the browser on, it opens the site on localhost, reads it and takes pictures, clicks and types in it, watches the console, tries it at 375 pixels and reloads it. The Browser tab opens next to it and says when it is using it: Stop it, I take over.

In detail

  • A branch of its own.

    Before writing it opens an “agente/” branch with the date and the task. At the end of the turn it makes a commit, signed “Co-authored-by: Pan on code”, and pushes without forcing.

  • A check before the push.

    It comes before the push: secrets in the code, GitHub’s workflows, the diary and the tasks.

  • A team, if needed.

    A coordinator and agents, each with its own model: one that reasons at length, a fast one, one that can look at screens. How it works.

  • One working copy per person.

    On the server, next to the space. Each project has a short AGENTS.md written with your three answers, and a folder with the state, the diary, the tasks and the decisions.

  • It reads the space’s pages.

    Read-only, only of that space, and only where you have “Use Pan”. With Ask Pan about this file, Pan sees the file you have open, sixty lines above and below the cursor.

  • GitHub, two ways.

    With the organization’s app, connected by whoever has “Keys”: the new repository is created by Fallthere, empty and private. Or with your own GitHub code, in My GitHub: the vault seals it, and Pan on code never sees it.

  • An existing repository too.

    With your personal code. The first commit, the structure, is made by the person on an empty repository; on one already full it arrives as a change request.

  • Who signs the commits.

    The commit carries “Co-authored-by: Pan on code”. With the organization’s app and without your personal GitHub, they carry the name and mail of the Fallthere account.

How to use it

Six moves, from GitHub to the draft.

  1. Turn on Coding.

    The + at the bottom of the bar, Add or remove apps: Coding is off by default. It also turns on by opening a code project.

  2. Connect GitHub.

    Whoever has “Keys” connects the organization’s app (Settings, Administration, GitHub). Anyone can say yes in their own name or paste a code, in My GitHub. The guide A code project says how.

  3. Create a project.

    From the “+”, Code project; or right-click on a folder, Make it a code project…; or New code project. A new private repository, or one you already have.

  4. Ask Pan on code.

    In the right-hand column, the Pan on code tab: What should I do in the code? and Ask. Closing the tab stops the work.

  5. Answer the permissions.

    Yes, this time, Yes, for this conversation or No.

  6. Look at the changes.

    Changes shows the files changed on the branch. At the end of the turn you find a commit and, once per session, the draft merge request.

Examples

Made-up people and data.

  1. Luca, Mirto Labs

    A new feature.

    Luca opens the project and asks Pan on code to add a field. Pan works on a branch of its own and at the end of the turn makes a commit. The draft merge request waits for Luca.

  2. Luca, Mirto Labs

    A permission.

    Pan wants to run “npm install” and asks. Luca chooses Yes, this time: next time it will ask again.

  3. Luca, Mirto Labs

    Testing the site.

    Pan on code opens the site it builds, tries it at 375 pixels and says what does not add up. Luca watches in the Browser tab, and can stop it with Stop it.

Coming soon

No dates: it arrives when it’s ready.

  • Group coding: several people in the same conversation with the agent, one turn at a time

Frequently asked questions

Can the agent change the main branch?

No. It works on a branch of its own and prepares a draft merge request, which waits for a person. Where GitHub allows it, the main branch is protected: no deletion and no forced push. On a private repository of a free GitHub plan the protection is not there, and the draft is a request with “Draft:” in the title.

Where does Pan on code run?

On the server, next to your space: each person has their own working copy of the project.

Which models does it work with?

With the ones you choose, with your key: the coordinator and each agent of the team can have a different one. The team uses OpenRouter models.

What does the browser see?

Your site in development, on localhost, on development ports. You see it too, in the Browser tab, and can stop it.

What language does it answer in?

Always Italian: the steps and the answers.

What happens if I close the tab?

The work stops. The conversation stays only in memory.

Let’s see it together.

We show it to you live.

Book a demo

Your mail app opens with a message already written. Or write to info@firmamentotechnologies.com.