GigAI
GigAI runs AI work on your own computer, under your control. Your settings, your credentials and your work stay on your machine, and every model call can be inspected. It works through the model you already use: Codex, Claude Code, Ollama or OpenRouter.
Scout is its first Gig, for a job search. It keeps a local store of public job postings, ranks them against your resume, assesses the ones you approve, asks you the questions a posting leaves open, remembers your answers and stories, and drafts a tailored resume you download as a PDF. You use it from the browser, or from your own AI agent.
Quickstart
-
Requirements. macOS or Linux with Python 3.11+,
uv, and one model CLI installed and logged in: Codex (codex login) or Claude Code (claude, then/login). -
Install.
uv tool install gigai
-
Run.
gigai scout run # starts Scout and opens the browser
The setup wizard asks for your model, your resume (
.mdor.txt) and your roles. Then Update sources fills the store, the Jobs page lists what matches, Assess these assesses what you approve, and Tailor resume drafts a resume for one job. Update later withuv tool upgrade gigai.
Use it from your AI agent
gigai agent-skill # prints the instructions that teach your agent the loop
gigai agent-permissions # prints a permissions snippet for you to apply; GigAI applies nothing
gigai scout new # what is new since your last check
- You ask your agent "what's new?". It runs
gigai scout newand shows you a grid. - Scout asks before it assesses: you see the count and an estimate, and say yes or no.
- The agent asks you each job's open questions and saves your answers. A longer reply becomes a story, if you agree.
- Jobs you answered are tailored and scored in the background, within daily limits (10 jobs per trigger, 40 model calls a day; more waits for your approval).
- For a PDF the agent gives you an "open in Scout" link. You add your name and contact details there, in your browser. The agent never gets them.
For agents has the full workflow, the setup and an example session.
Privacy
GigAI never stores your name, email, phone, address or links. You type them only when you make a PDF, and GigAI forgets them right after. A resume you add is stored without its name and contact lines; that removal works on patterns and can't catch personal details elsewhere in the text, so keep those out. Earlier versions did store contact lines: a one-time cleanup after you upgrade removes them from the current files, but older copies can remain in GigAI's local history on your computer.
Everything else you give GigAI (your answers, stories, notes and the body of your resume) stays on your computer unless you or your agent send it somewhere. GigAI's own model calls send your resume (without the contact lines) and your answers to the model you picked. With Ollama the resume stays on this machine.
Anything GigAI gives your agent is sent to that agent's model provider. Agents get no contact data from GigAI, but an agent with shell access can read local files.
See Privacy and security for exactly what is stored, what is sent, and to whom.
Links
- Documentation: quickstart, concepts, CLI and API reference, known limitations
- What Scout's numbers and labels mean: rank, verdict, Scout label, Scout ATS score
- Roadmap: what is planned, without dates
- CHANGELOG and Releases
- CONTRIBUTING and issues
GigAI is an alpha; expect rough edges. Apache-2.0, see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for gigai 0.1.10.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gigai-0.1.10.7.tar.gz | 2.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gigai-0.1.10.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.4 MB
Release files / gigai-0.1.10.7.tar.gz
| Download URL | gigai-0.1.10.7.tar.gz |
|---|---|
| Size | 2.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b66aea3bc72369c8c5ac7565b2945af1dc24d363c45ddfec6bd17d3ed1b548b5
|
|
BLAKE2b-256 checksum How to use checksums |
ca349f7b0a0289dc78a1a33027d4caf38afc8f6d8f1c02221c816261d84050cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency logRelease files / gigai-0.1.10.7-py3-none-any.whl
| Download URL | gigai-0.1.10.7-py3-none-any.whl |
|---|---|
| Size | 2.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d43ea6c7416eca7630eb4eb80399e4ffbd8b8d8bf68968b256ba8ee4bf62da3
|
|
BLAKE2b-256 checksum How to use checksums |
a037c3c68046467c973128b1753cefadfac1c5ff789719ab11510b12a53d9252
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency log
