session active
Background
📖 User guide
0 words · 0 chars
Projects
↺ Reset

⚙ AI Settings

AI Keys & Providers
Keys live in ~/.hap-proxy/config.json — never in the browser.
Add a provider: stop hap-proxy, run python hap-proxy.py --setup — shows a labeled field for each provider. Paste whichever keys you have. On next connect they appear in the chat dropdown.
New version? Download above, replace the file, restart.
Add an AI Key
Keys are stored in ~/.hap-proxy/config.json — never in the browser.
To add or update a key, open a terminal and run:
python hap-proxy.py --ai-setup
Shows a labeled field for each provider — Claude, GPT, Gemini, and others. Paste whichever keys you have. On next connect they appear in the chat dropdown.
AuthorAware · Quick Reference

Three things that might look unfamiliar

🔑
API Key

An API key is a private password that unlocks access to an AI service — Claude, GPT, Gemini, and others. When you ask the AI a question in AuthorAware, a small program running on your computer (the proxy) uses your key to contact the AI on your behalf. The key never travels through your browser; it stays on your machine. You get one by signing up at the AI provider's website. They charge a small amount based on how much you use — typically a few cents per conversation.

🐙
GitHub

GitHub is a website that stores files and keeps a permanent, timestamped record of every change ever made to them. Programmers have used it for thirty years to collaborate on code — but it works just as well for any writing. When you back up a checkpoint to GitHub, it creates an immutable record of your draft at that exact moment. If you ever need to prove your work existed on a specific date, or recover an earlier version, it's all there. Repositories can be set to private so only you can see them. It's free.

With AI tools now everywhere, GitHub has become the single most reliable way for anyone — writer, researcher, student — to maintain a verifiable history of their own work. If you can save a file, you can use GitHub.

🎫
Access Token

An access token is a limited key that lets AuthorAware write to your GitHub repository without your actual account password. Think of it like a valet key — it opens only the specific door you choose, and you can cancel it at any time from your GitHub settings without changing your password. GitHub generates it for you in a few clicks; you paste it into AuthorAware once, and it's stored locally on your machine.

AuthorAware · Storage

📁 Where your projects are saved

☁ GitHub Backup (optional — free)

Your checkpoints commit to a private GitHub repo — permanent, version-controlled, yours.

Step 1 — GitHub account
  1. Go to github.com/signup
  2. Enter email, password, username
  3. Verify your email
Already have one? Log in
Step 2 — Create a repository
A repository is a folder that keeps every version of your files.
  1. Go to github.com/new
  2. Name it my-writing-backups (example)
  3. Set visibility to Private
  4. Click Create repository
Step 3 — Create an access token
This lets AuthorAware write to your repo without your password.
  1. Click your profile photo (top-right on any GitHub page)
  2. Click Settings
  3. Scroll the left sidebar to the very bottom
  4. Click Developer settings
  5. Click Personal access tokens → Fine-grained tokens → Generate new token
  6. Give the token a name — e.g. AuthorAware
  7. Set Expiration to No expiration — the token only touches your backup repo
  8. Under Repository accessOnly select repositories → pick your backup repo
  9. Under Repository permissionsContentsRead and write
  10. Click Generate token — copy it now, you won't see it again
Step 4 — Enter your details
⚠ This token is saved in browser storage only. If you clear your browser cache, you'll need to re-enter it — but it's easy to get a new one: go to github.com → Settings → Developer settings → Fine-grained tokens, find your token, and click Regenerate.
To store it permanently on your machine so it never needs re-entry, run python hap-proxy.py --github-setup. See the Setup Guide →
⟡ AI Collaborator
AI exchanges are sealed into the provenance record alongside your writing.
0 exchanges sealed