notes

Using Padgit

The detailed guide. For a first note in two minutes, see Try it.

Look around first

On the sign-in screen, Look around first opens Padgit with a few sample notes, without an account or a GitHub sign-in. Everything works on them: open, edit, tick, link, Preview, Today. They live only in that browser tab: nothing is sent anywhere, and closing or reloading the tab starts them afresh. Renaming and moving are not available there. Sign in in the banner at the top leaves the demo.

Sign in with a token instead

For the most privacy short of running your own copy: on the sign-in screen, open Other ways to sign in and use a GitHub fine-grained personal access token instead of the app. Make it with the link there, choosing Only select repositories (your notes repository), Contents: Read and write and an expiry date, then paste it. It goes only from your browser to GitHub: no app is installed and the sign-in service is never used. Padgit lists the repositories the token can read, which may include public ones it cannot save to; it saves only to the ones you gave it. Padgit cannot tell in advance whether a token may save, so a token without Read and write is found out at the first save, and what you typed is kept. When the token expires or is deleted on GitHub, Padgit signs you out and keeps what you had not saved; make a new token and sign in with it.

New to GitHub?

GitHub is where your notes are stored. You need a free account (make one); you never need to write code. A few words you will meet:

Because your notes are plain files in your own repository, AI tools you connect to GitHub (Claude, ChatGPT, Codex and others) can read them and, if you allow it, add to them. Padgit itself sends your notes nowhere but GitHub.

Finding and saving notes

The editor’s formatting bar inserts or toggles Markdown around selected text or lines: bold, italic, heading, bulleted/numbered/task lists, links, quotes and code. With no selection, inline actions select a placeholder to replace. Ctrl/Cmd+B and I format text; Ctrl/Cmd+Shift+K inserts a link. Ctrl/Cmd+K continues to open the note switcher. Undo works in both editors.

Editor and Preview use a centred reading column on wide screens. Settings → Note text size changes both at once (Smaller, Normal or Larger), remembers the choice in this browser and keeps it after sign-out. Phone text stays at least 16 pixels to avoid focus zoom.

Opening a note updates the address. Bookmark or copy it to return after sign-in; choose the same repository and branch in Settings. Browser Back and Forward (or Alt+← and Alt+→) and phone back gestures move between notes. Leaving still saves edits or keeps their draft. Filenames are in the address fragment (not sent to the static host), and may remain in browser history.

Settings includes About Padgit, with the version, GitHub repository, privacy note, changelog and Report a bug. Links open in a new tab.

Before browsing folders, you can use Find in the header or Ctrl/Cmd+K to open a note by name or path. Recent notes appear first for an empty query; typing ranks exact names and then name prefixes. Use arrow keys and Enter, or tap a result. Escape closes the switcher. This searches the loaded file list without reading note contents; use Search contents for that.

The line below the note keeps its save status visible, including in Preview: Saved, Saving, Unsaved changes, a conflict, or an offline draft. A successful save in this open note shows its time. Word count counts whitespace-separated parts of the Markdown source, including frontmatter and Markdown markers. If browser storage is full or blocked, the line says the local copy is unavailable; save or copy your text before closing the page.

No notes repository yet

Signed in, but Padgit is on no repository? The app shows two steps and nothing else: Create a repository opens GitHub’s form with the name notes and Private already filled in, and Let Padgit use it opens the page where you choose that repository for the app. Both open in a new tab. Come back to the Padgit tab and it notices by itself (or press Check now): with one private repository you go straight in, with several you choose (a private one called notes is offered first). A public repository is never chosen for you, and choosing one says that anyone can read what is saved there.

A brand new, empty repository

A repository with no commits works: the file list says it is empty, and the first note you save creates its main branch. If the repository’s main branch is later renamed, or your first push from elsewhere creates a differently named one, the app follows it and says so.

Writing, saving and organising

Today in Files opens your daily note using your device’s local date. Without Obsidian settings it uses Daily/YYYY-MM-DD.md. If your vault has .obsidian/daily-notes.json, Padgit reads its folder, format and template without changing that file. An empty folder means the repository root. Common Moment year, month, day and time tokens and [literal text] work; unsupported filename formats fall back to YYYY-MM-DD with a notice. Templates support ,, and explicit formats such as; template scripts are not executed. To start every new daily note from a template, write the template as an ordinary note (headings, prompts, `` and the other placeholders above), save it, then choose ⋯ → Use for new daily notes in that note. Today now starts each new day’s note from it; ⋯ → Stop using for new daily notes goes back to blank notes. Padgit records the choice as the template line of Obsidian’s .obsidian/daily-notes.json (making that file if needed, with daily notes in Daily/, or at the top level if daily notes are already there), so it works on every device and in Obsidian. Nothing else in that file changes. If the template note is later renamed or deleted, Today says so: choose the template again from the note you want. A new daily note is created only when saved (or after editing triggers autosave). Existing notes and drafts are preserved. Missing templates or invalid settings show an explanation and leave the current note alone.

Each save is one commit. Notes save themselves two seconds after you stop typing, and straight away when you switch to another app or tab. Beside the note’s name, a green dot with Saved means GitHub has it; with unsaved changes it turns into a Save button (on a phone, the dot alone), and Ctrl/Cmd+S works any time. A file you have only opened, or a restored draft you have not typed into yet, is never saved on its own. Switching to another file never asks anything: what you typed is committed on the way out, or, if that cannot happen yet (offline, a conflict), kept as a draft for when you come back.

A write carries the version it was based on, so if the file changed underneath you GitHub rejects it: you are told, your text stays in the editor, and that file stops saving itself until you resolve it. Nothing is silently overwritten.

Unsaved changes are kept in the browser as you type, one draft per file, so a reload, a closed tab or a phone closing the app in the background loses nothing. Open the file again and the draft is back, marked unsaved draft; saving commits it and removes it, Discard throws it away and loads the version on GitHub. A draft remembers which version it started from, so if the file changed on GitHub in the meantime, saving never overwrites it: it is merged when the changes are on different lines, or reported as a conflict (a draft restored after a reload is never merged, only kept both ways). Signing out deletes every draft in that browser.

Markdown notes open in Preview; new or empty notes, notes with a restored draft, and other text files open in Edit. Use the Edit / Preview switch at the top to read the current note, including unsaved edits, as rendered Markdown. Edit returns to the unchanged source. Headings use your device’s book face. Obsidian callouts (> [!tip] Title, > [!warning], and foldable > [!note]- or > [!note]+) appear as coloured boxes with an icon; other editors see an ordinary quote. Simple properties (frontmatter) appear as chips above the note, such as Pinned and its tags; anything more complex appears as its text; checklists are editable and wikilinks open notes. Repository PNG, JPEG, GIF and WebP images appear in Markdown image references and Obsidian ![[image.png]] embeds. Relative paths resolve from the note’s folder; / starts at the repository root. Up to 20 images, each no larger than 10 MB, load with four requests at a time (images over 1 MB are read as Git blobs, as GitHub only hands smaller files over with their contents). External images, SVGs, hidden paths and known symlinks show a notice instead. Missing or undecodable images also show an explanation. Images never become editable notes. If the preview libraries cannot load, Padgit explains this and keeps the editor available.

Save or resolve source changes before editing a checklist. Read-only repositories keep every checklist control read-only. Unusual or ambiguous Markdown stays read-only in Preview with a notice; use Edit for its source. Sub-tasks indented with tabs (as Obsidian writes them) or spaces, and tasks inside a quote or a callout (such as > [!todo]), work like any other; a quote with a line that carries on without its > is one of the unusual cases. Failed task text edits are kept as drafts and return when the note is reopened. Clear done removes checked lines only, leaving unchecked children (a ticked task stays when its unchecked sub-tasks are indented a tab or four spaces, which would otherwise read as code); × removes the whole task and its children. Both offer Undo.

In Files, typing filters filenames instantly. Press Enter or Search contents to search note text as well, including local drafts. Opening a result keeps the list available. Search reads up to 300 text files, four at a time; files over 1 MB and hidden folders are excluded. It reports unreadable files, scan limits and partial file lists rather than claiming a complete search. Press Search contents again to update results after edits, or refresh Files to pick up remote changes. Search creates no index or extra repository files.

If a request fails

If GitHub or the connection fails, the message stays visible until another action. Retry the same button: Save for a note, the file-list refresh button for the list, or the file name to open it again. A request that does not answer times out after 30 seconds. A temporary sign-in service outage keeps your sign-in; a rejected refresh token still asks you to sign in again. For a rate limit, wait for the time shown before retrying. Padgit also holds requests during that wait. Repository rules may require the repository owner’s help before a write can succeed.

An interrupted save keeps your draft. If you reload or change repositories before its outcome is known, retrying may report a conflict with your own earlier save: Save as copy keeps your text as a new note beside it. Padgit does not silently replace a version it cannot verify.

If a note changed on GitHub while you were editing it (another device, a colleague), saving merges the two when you changed different lines, and says so. Where you both changed the same lines nothing is guessed: the note is marked as a conflict, and Save as copy saves your version as “name (my copy).md” beside it while the note shows theirs, or Discard loads theirs and drops yours. No conflict markers are written into notes.

If a checklist save fails, the list goes back to what GitHub has; a task text edit that could not be saved is kept as a draft of the note, and returns when you reopen it. Changing repositories while a checklist is saving keeps its pending text as a draft in the original repository. Return there and open the note to recover it; copy the text before discarding if it reports a conflict. If browser storage is full, changing between remembered and session-only mode stops and explains why, keeping the drafts in their original storage.

Repositories you cannot change

An archived repository, or one your GitHub account can only read, opens read-only: a red read-only badge says why, the editor is locked and there is nothing to save, so nothing is ever sent. If a repository is deleted, renamed or the app is removed from it, the file list says so and points you to settings.

Using it on several computers

It is a web page, so any browser works: home, work, phone. Sign in once per browser. On a phone, open the URL and choose Add to Home Screen. The home-screen shortcut is named Padgit, uses the paper icon and opens the app in its own window. It still needs a connection to GitHub to load and commit notes. On iPhone or iPad, sign in again in the home-screen app. Save any browser drafts first; they stay in the browser. When GitHub opens in a browser to choose repositories, return to the Padgit home-screen app afterwards. On a phone, the editor follows the space above the keyboard, keeping the caret and header controls visible. Pinch zoom remains available.

On a work or shared computer, tick Forget me when I close the browser before signing in. The sign-in and drafts are kept for this browser session only, not in its lasting storage, and go when the tabs are closed. Drafts of unsaved changes still survive a reload in this mode, so save before you leave, and press Sign out: a browser set to reopen its tabs on start brings the session back with them (see the privacy note). A session badge in the header shows which mode you are in.

Sign-ins last six months per browser; the app renews the short-lived token every eight hours without asking. Several tabs open at once share one sign-in and take turns renewing it, so they never sign each other out. They share settings too: choose another repository or pinned files in one tab and the others follow, after saving what was open in them to the repository it came from. Signing out, or choosing Forget me, in one tab signs the others out.

Using it with an existing Obsidian vault

It reads the vault as it is. Nothing is converted, and nothing is written that Obsidian would not understand, so both can work on the same repository.

Open notes

Choose Outline in the note’s ⋯ menu to see its headings, including underlined headings and headings inside lists or quotes. Select one to jump there in the editor or Preview. The outline uses the current unsaved text without fetching anything; it does not modify the note. Long outlines have Previous/More controls. Escape closes the outline. If the note changes while it is open, reopen it to get current positions. If the Markdown library is unavailable, a notice explains why the outline cannot load; editing still works.

Expand Linked from under a Markdown note to see notes that link to it. Wikilinks use the same resolution as opening a link; Markdown paths resolve relative to their source note. Reference-style links work too. Code, comments, image embeds and external links do not count. Drafts take precedence over saved text. Choose a result to open its source. On a small screen, Linked from collapses when the keyboard needs the space.

The scan reads up to 300 loaded Markdown notes and reports skipped or unavailable files. Refresh Files to pick up repository changes, then reopen Linked from. If the Markdown library fails to load, the section explains why it is unavailable; editing remains available.

Expand Tags in Files to find Markdown notes by tag. Counts include nested tags (project includes project/notes) and ignore case. Opening the section scans up to 300 loaded Markdown notes using the shared reader; skipped or unavailable notes are reported. Close and reopen it to refresh.

Tags in the note’s ⋯ menu shows its tags above the editor and Preview. Add tag writes the tags property; the × removes a frontmatter tag. These edits preserve other properties and unsaved text and support Undo. Inline #tags remain in the text: select their chip to find related notes, or edit the source to remove them. Tag discovery skips fenced/indented code, inline code, links and comments. Simple YAML tag lists and scalar tags are supported. Complex or ambiguous frontmatter must be edited in the source; the tag controls explain this without rewriting it. No tag index is written into your repository or browser storage.

Expand Recent in Files for recently opened notes and repository changes, with the first heading, a short preview and a time. Local drafts take precedence. The list reads history only when expanded: up to 10 commits, the first 100 files in each commit and 20 notes. It is a bounded view, not a complete activity log. Close and reopen it to refresh. Missing history or previews are labelled.

Open notes have tabs above the editor and Preview. Reopening a note selects its tab. Use × to close a tab; unsaved text stays in its draft. The last 12 open tabs are remembered for this browser’s current repository and branch. On phones, expand Open notes to choose or close one. Closing the last tab leaves the editor empty; it does not delete a file.

Adding images

Use Image above the editor, paste an image, or drop one into the text. PNG, JPEG, GIF and WebP files are supported, one at a time. A photo or screenshot over 1 MB is made smaller in your browser before upload (a PNG stays a PNG if it fits, otherwise it becomes a JPEG) and the status says so; GIFs over 1 MB are refused, since shrinking would stop them moving. Padgit reads the vault’s .obsidian/app.json attachment folder setting; without one it puts the image beside the note. Each upload creates a unique attachment and inserts an ordinary Markdown link after GitHub confirms it. Undo removes the link, leaving the attachment in the repository. If you switch notes during upload, the status names the saved attachment so you can link it from the original note. Failed uploads leave your note text unchanged.

Using Padgit with agents

Agents such as Claude Code or Codex can work on the same repository as Padgit: they read and change the same files, and their changes show in Padgit like anyone else’s. To keep your notes working in Padgit and Obsidian, you can give them standing instructions: copy the text below into a file named AGENTS.md at the top of your notes repository (Claude Code also reads CLAUDE.md; a file with just @AGENTS.md in it points there). Padgit never writes this file for you.

# Notes repository

These are my personal notes, edited in Padgit and Obsidian.

- Leave daily notes and my own writing alone unless I ask you to change them.
- Keep frontmatter, [[wikilinks]] and the .obsidian folder intact.
- If there is an Inbox.md, file what is in it where it belongs, then clear it.
- Say who you are in every commit: name yourself in a
  "Co-authored-by: <your name> <email>" line, or commit as your own account.

That last line is what lets Recent and History show Claude or Codex instead of you: an agent working on your computer usually commits under your name. Anything in the repository, daily notes included, can be read by any agent you give it to, so keep it private.

What it deliberately does not do

No offline queue, no graph view, no plugins, no real-time collaboration and no line-by-line merge tool: a conflict is merged when the changes are on different lines, and otherwise kept both ways (see above). Each of those is a common reason a notes app becomes unmaintainable.

Accessibility

Automated accessibility checks use axe against the main views and plain-editor fallback, failing on serious or critical violations. They supplement manual keyboard and screen-reader testing; they do not certify full accessibility.

Known limits