All apps

First-party app · Git Repository

git-repo

Index the CONTENT of a git repository you own into your knowledge library. Source code AND docs, from a local clone or a github.com URL; each file becomes a searchable knowledge item, and a re-poll after a new commit ingests only the changed files (commit-cursor), never the whole tree. Remote fetches route through the core network chokepoint; it owns no socket.

Before you install

A first-party app of PersonalClaw v0.3.9

No scan on record before install

PersonalClaw publishes no scan of its own apps before you install one.

PersonalClaw runs its own scan of the actual code of every app it installs: this one is rescanned when you install, and that scan is what can stop an install.

Its row on Compare: install rescan

Compatibility
Works with PersonalClaw v0.3.9

What it gets

Permissions
  • network: true
Its own network permission
On. Its own network permission is a declaration, not a fence.

What it starts

The programs on this machine it starts, as install consent names them.

  • git: git reads the commits and files of the local clone you point the app at, to index them. It runs only commands that read the clone.

    It runs with your own git settings.

What it reaches

Hosts it names
Not declared in this release's manifest

Its own code has no host list at this release: any hosts it names are for the programs, servers and sources it starts or fetches, not everything it can reach. Its own network permission is a declaration, not a fence.

Secrets you would enter

Settings marked secret
  • Access token credential

The app's settings file holds only a reference, the value lives in the credential store, and every route that shows settings masks it. The app's own code receives the value when it runs.

Its own code calls PersonalClaw's gateway with a token scoped to the app, not with your owner token.

What installing it gives and runs

The manifest's own declarations, under the names install consent shows them by and in its order. The Store adds, at install, which of them run as you.

Permissions it is granted
{
  "network": true
}
Programs on this machine it starts
[
  {
    "program": "git",
    "why": "git reads the commits and files of the local clone you point the app at, to index them. It runs only commands that read the clone.",
    "inherits": [
      "settings"
    ]
  }
]
Provider modules the gateway loads
[
  {
    "type": "knowledge",
    "implementation": "provider:create_provider"
  }
]

Not declared in this release's manifest:

  • Scheduled jobs
  • Python packages installed for it
  • Engine packages it can install
  • What it needs that PersonalClaw does not install
  • npm packages installed for it
  • Places outside its folder it writes
  • Pages it adds to the dashboard
  • Components it adds to the dashboard
  • A server process of its own
  • The sandbox tier its server runs in
  • Command run after install
  • Command run after an update
  • Command run when it is switched on
  • Command run when it is switched off
  • Command run before it is removed
  • What it runs for personalclaw setup
  • What it runs for personalclaw doctor
  • Connector sources it parses
  • MCP servers it adds
  • Skills it installs

Where it comes from

Publisher
PersonalClaw
License
MIT
Pinned commit
169cbc4f8fc59cd42a65a6a3546235bc49ab3b22
Signer
Not declared in this release's manifest

From review to enable

  1. Held and scanned. An install stages the app in quarantine, checks its signature, and runs the shared supply-chain scanner over the staged bytes before anything is shown for consent. A registry's recorded verdict is not read at install: the scan that can stop it is this one.Its row on Compare: install rescan
  2. A dangerous verdict ends it. A dangerous verdict returns a refusal before consent is asked, so there is no consent to give and no switch that skips it. A warning verdict asks for your consent instead.Its row on Compare: dangerous verdict
  3. You review and consent. The review records a digest of the staged bytes, and an install committed against different bytes is refused: it needs consent again, because the app changed after it was reviewed. An update that changes what the app gets asks for consent again too.Its row on Compare: consent
  4. Its setup runs, then you switch it on. Nothing it declares runs before your consent; an app already installed is offered as an update instead.

To install it and switch it on

  1. In PersonalClaw, open the Store.
  2. Find git-repo.
  3. Review what it gets and runs, and consent.
  4. Install it, then switch it on.

Evidence

git-repo/app.json at the pinned commit, as written, with the blob hash git lists for it: dbbb7ea2a3766b55455557faee5cfd32eea2c811

Open it at the commit

{
  "name": "git-repo",
  "version": "0.1.3",
  "displayName": "Git Repository",
  "description": "Index the CONTENT of a git repository you own into your knowledge library. Source code AND docs, from a local clone or a github.com URL; each file becomes a searchable knowledge item, and a re-poll after a new commit ingests only the changed files (commit-cursor), never the whole tree. Remote fetches route through the core network chokepoint; it owns no socket.",
  "icon": "GitBranch",
  "author": "PersonalClaw",
  "license": "MIT",
  "tags": [
    "knowledge",
    "git",
    "source",
    "code",
    "docs"
  ],
  "provider": {
    "id": "knowledge",
    "label": "Index a git repository into your library",
    "type": "knowledge",
    "implementation": "provider:create_provider",
    "capabilities": [
      "source"
    ],
    "settingsSchema": {
      "type": "object",
      "properties": {
        "repo": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "Repository",
            "help": "Default repository for new sources: an absolute path to a local working clone on this machine, or an https://github.com/<owner>/<repo> URL. Each source can override it with {\"repo\": \"...\"} in its own spec, so one install can watch several repositories. Leave empty to configure every source individually."
          }
        },
        "ref": {
          "type": "string",
          "default": "HEAD",
          "x-meta": {
            "label": "Ref",
            "help": "Default branch, tag, or commit to index, overridable per source. Defaults to HEAD (the repository's current head)."
          }
        },
        "include": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "Include globs",
            "help": "Comma-separated filename globs to index (e.g. *.py, *.md). Empty means the built-in default, which covers common source-code AND doc extensions."
          }
        },
        "exclude": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "Exclude globs",
            "help": "Comma-separated globs to skip, matched on the path or basename (e.g. *.min.js, tests/*). VCS/dependency/build directories are always skipped."
          }
        },
        "max_files": {
          "type": "integer",
          "default": 5000,
          "x-meta": {
            "label": "Max files",
            "help": "Hard ceiling on files ingested per poll (1–5000). A huge tree degrades to a bounded ingest rather than a long walk."
          }
        },
        "token_credential": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "Access token credential",
            "help": "For a PRIVATE github.com repository: the name of a credential (in Settings > Credentials) holding a personal access token. Sent in an Authorization header, never in a URL. Leave empty for a public repo or a local clone.",
            "sensitive": true
          }
        }
      }
    }
  },
  "permissions": {
    "network": true
  },
  "launches": [
    {
      "program": "git",
      "why": "git reads the commits and files of the local clone you point the app at, to index them. It runs only commands that read the clone.",
      "inherits": [
        "settings"
      ]
    }
  ],
  "quality": {
    "tested": true
  }
}
Scan verdict
No scan on record before install
Scan time
No scan is published before install
Blocking findings
No scan is published before install
Scanner version
No scan is published before install

PersonalClaw publishes no scan of its own apps before you install one.

  • Every app is scanned again when you install it, whatever its listing says.

    An install stages the app in quarantine, checks its signature, and runs the shared supply-chain scanner over the staged bytes before anything is shown for consent. A registry's recorded verdict is not read at install: the scan that can stop it is this one.

    apps/app_manager.py at v0.3.9
  • A dangerous scan verdict stops the install, and nothing overrides it.

    A dangerous verdict returns a refusal before consent is asked, so there is no consent to give and no switch that skips it. A warning verdict asks for your consent instead.

    apps/app_manager.py at v0.3.9
  • Consent covers exactly what you reviewed, and an app that changed asks again.

    The review records a digest of the staged bytes, and an install committed against different bytes is refused: it needs consent again, because the app changed after it was reviewed. An update that changes what the app gets asks for consent again too.

    apps/app_manager.py at v0.3.9
  • A setting an app marks secret is kept in the credential store and never shown back.

    The app's settings file holds only a reference, the value lives in the credential store, and every route that shows settings masks it. The app's own code receives the value when it runs.

    apps/secret_fields.py at v0.3.9

PersonalClaw/PersonalClawApps @ 169cbc4f8fc5 · git-repo/app.json