logposa / the forge for the agent era

README  

▲ LOGPOSA

Where your team and its AI agents build software together, and nobody forgets why.

AI agents now write a big part of the code. They are fast, but they forget everything between two tasks. So the team explains the same things again and again, and the reasons behind the code get lost.

Logposa is the home of your code, built for this. It remembers what your team decided, and makes sure every agent follows it.

▲ each arrow is a change, by a person or an agent. Move your mouse: they all find the same course. Click to merge.

## How it works

Logposa is a forge, like GitHub: your code, your changes, your reviews, your tickets. The difference is who it was built for. GitHub was built for people. Logposa is built for people and agents working on the same code.

  1. 1Bring your projects. Logposa stays in sync with GitHub, so nobody has to move on day one.
  2. 2Logposa learns how your team works. What the code is meant to do, who knows each part, which choices you already made.
  3. 3Everyone works with that memory. People review faster, agents follow your rules, and the boring work runs on its own.

One node per team, not a shared server. Each team gets its own Logposa: its own machine, its own data. When another company pushes a thousand agent changes at once, your pages, your reviews and your agents don't feel it.

shared forge                ▲ logposa
[ you | them | them | them ]   [ you ]   [ them ]   [ them ]
 everyone waits in one line     each team runs on its own node

Everything you do on GitHub, you can do here. Pick one to compare:

## Features

    ## Every change remembers why

    People and agents work side by side. Click a change to see the reason behind it.

      ## Decide once

      When your team makes a choice, Logposa notices it and suggests a rule. You keep it, change it or drop it. Try it:

      ## Agents handle the chores

      Something breaks? An agent picks it up, tries until it works, then asks you to approve.

      
        

      · you choose which agents work, and what they may do alone.

      ## Automations that think in numbers

      Write what you want in one sentence. Logposa watches the numbers and acts only when they say yes. Change the words below:

      When , if the tests pass, it changes fewer than lines, and errors stay under for . Otherwise, .

      
        

      Other ideas: lock a release when error rates climb · ask a second reviewer when a change touches payments · close stale issues nobody follows.

      ## Everything on record

      Every change, every approval, every automation: who did it, when, and under which rule. Ready for your SOC 2 or ISO 27001 audit.

        The record can't be edited. Hand it to your auditor as a report, filtered by date, person or rule.

        ## Works with the agent you already use

          Connect it once. It then knows your team's rules, wherever it works.

          ## Get started

            ## Questions

            Do we have to leave GitHub?

            No. Logposa stays in sync with GitHub. Move when you are ready.

            Where is our code kept?

            On your team's own node, a server that only your team uses. Your data is never mixed with another company's, and their traffic never slows you down.

            Can an agent change things on its own?

            Only what you allow. Everything else waits for a person to approve.

            Why "Logposa"?

            A log pose is a compass that always points to the next island. Logposa keeps every change pointed the way your team chose.

            ──── logposa · 2026 · blog · the stories on this page are examples