OXYGENHUB

README: a section on working with agents 1f53d5b91eb5

Where the delegation model is explained and how it shows who did the
work, with pointers to the design and the guide.
Author
Andy McCall @andymccall <[email protected]>
When
· 2026-10-04 17:59 UTC
Signature
✔ signed by Andy McCall
Hash
1f53d5b91eb5f2d67b7733d87ad53b41c0d6b8ba3c42eca34dc02933f2ba0887
Depends on
648724d8e0de d02e545dc265
Depended on by
37f1914b62a8
In bookmarks
agents-in-readme bare-hashes carried-not-removed carry-identical doctor-trust identical-sides keyless-tags main merge-remote-bookmark only-help-103 paths-for-resolutions-and-amend push-notes show-stat subrepo-pin-state switch-says
In tags
v0.10.0 v0.11.0 v0.4.1 v0.4.2 v0.4.3 v0.4.4 v0.4.5 v0.4.6 v0.5.0 v0.5.1 v0.6.0 v0.7.0 v0.8.0 v0.9.0
Edits
1 atom, 0 tree operations, 1 file

Browse the tree at this change

hide whitespace changes
modified README.md +4 −0
… 
3 unchanged lines
4 4 

    

  
    

      5
      5
       
      
It is self-hosting: this directory is an Oxygen repository, and the project's own history is kept with `oxy`, not with Git.

    

  
    

      6
      6
       
      

    

  
    

      
      7
      +
      
## Working with agents

    

  
    

      
      8
      +
      

    

  
    

      
      9
      +
      
An AI agent works in Oxygen under its own key, delegated by you for a scope and a time (`oxy identity delegate add agent.identity --scope changes --expires 8h`): every change it makes is authored by you and signed by the agent, so `oxy log`, `oxy verify` and the hub show *who did the work* ("Andy McCall · via Claude Code") and a policy can require that a person approved it. See [docs/ai_native_agent_workflows.md](docs/ai_native_agent_workflows.md) for the design and [docs/guide.md](docs/guide.md) §9 for the setup.

    

  
    

      
      10
      +
      

    

  
    

      7
      11
       
      
## What is different

    

  
    

      8
      12
       
      

    

  
    

      9
      13
       
      
- **History is a set of changes, not a chain of snapshots.** A change records what it did to identified lines and tree nodes and which earlier changes it depends on. Changes that do not depend on each other commute, so there are no merge commits and rebasing independent work rewrites nothing.

    

  
    

      
      
      …
      
63 unchanged lines