Javis OS
Javis OS is an Agentic AI that assists entrepreneurs in business tasks, helping them grow their work.
AI translation
Discover, tailor, apply, track, and interview with one connected career workspace.
BusinessTypeScript · PLpgSQLGitHub @Dr-OparaOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Your next move, handled.
Odesseus is a calm AI-assisted career workspace that helps a candidate move through:
Find → Review → Apply → Track → Interview → Follow up
• Marketing landing page
• Supabase email/password authentication
• Protected logged-in routes
• Resume-first onboarding
• Private PDF/DOCX resume storage
• Candidate profile + job preference persistence
• Calm live-data dashboard
• Applications view
• Interview workspace
• Candidate profile editing
• Credit balance read model
The project uses Supabase for authentication, Postgres, RLS, and private resume storage.Read the full README ↗Your next move, handled.
Odesseus is a calm AI-assisted career workspace that helps a candidate move through:
Find → Review → Apply → Track → Interview → Follow up
The foundation now includes:
The project uses Supabase for authentication, Postgres, RLS, and private resume storage.
Public user-data tables:
profilesjob_preferencesresumesjob_opportunitiesapplicationsinterviewscredit_balancesPrivate server-only billing tables live in odesseus_private.
Every exposed user-data table has Row Level Security enabled. Candidate records are scoped to the authenticated user. Credit balances are intentionally read-only from the user-facing client so paid credits cannot be self-issued.
Resume files live in a private resumes bucket and are restricted to the owning user.
Copy .env.example to .env.local and configure:
NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=
NEXT_PUBLIC_SITE_URL=http://localhost:3000
npm run dev refuses to start when the Supabase variables are missing — it
will not silently fall back to the production project. Local development
targets the local Docker stack started with supabase start (kong on
http://127.0.0.1:54321); use the values printed by supabase status for
NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY, and
SUPABASE_SERVICE_ROLE_KEY in .env.local. Real deployed credentials are
configured per environment in the Vercel dashboard.
Do not add Supabase secret/service-role keys to browser environment variables.
Candidate core usage is pay-per-use from a prepaid wallet. No subscription for candidate core usage; employer plans and recruiter seats may be recurring subscriptions.
Odesseus Match:
Odesseus Match adds the first real AI workflow.
job_opportunities.The default candidate threshold remains 85%+.
Resume parsing and match assessment are performed server-side. The OpenAI API key is never exposed to the browser, and model requests are configured with storage disabled.
PDF resumes are passed as file input. DOCX resumes are converted to raw text server-side before structured extraction.
Resume Tailoring adds:
Odesseus never adds unsupported qualifications to improve a match.
The repository includes AGENTS.md with persistent product, security, AI, billing, and UX rules for Codex.
See docs/development/codex.md for the recommended VS Code + Codex workflow.
Billing adds a prepaid candidate wallet, Standard/Smart Apply charges, and interview passes.
Wallet funds are not spent at top-up time. The Apply workflow draws the Standard or Smart rate only after a successful application submission is verified. Failed, unsupported, paused, cancelled, or unconfirmed submissions never deduct wallet funds.
Legacy note: the pre-wallet model charged one "$0.99 application credit" per submission. Existing credit balances are preserved until the legacy-credit reconciliation and conversion (see docs/development/pricing-migration-plan.md).
Stripe Checkout creates one-time payment sessions. A signed Stripe webhook records an idempotent billing event, which atomically updates the user's wallet or pass balance.
The browser can read its own balances/history but cannot create or modify funds.
Odesseus Apply is an assisted, human-in-the-loop application browser.
Odesseus applies across supported job boards and direct employer career sites, including Workday, Indeed, UN Careers / UN job portals, Greenhouse, Lever, Ashby, iCIMS, direct company career websites, corporate ATS portals, and other supported job boards/employer application sites — at the same Standard $0.39 / Smart $0.99 rates regardless of which platform the job is on. This is not a claim of universal technical compatibility with every site; coverage is scoped to supported job boards and employer career sites.
The current provider adapter uses Browserbase with Playwright and keeps the integration isolated under src/lib/apply so a different hosted browser provider can be substituted later.
Odesseus does not enable CAPTCHA solving or bypass MFA/identity controls.
Apply runs use Vercel Workflow so browser work can pause and resume instead of relying on one long request.
Phase 5 adds:
application_answer_vaultapplication_runsapplication_run_eventsapplication_run_questionsUser-facing run/event data is protected by RLS. System-created run records remain server controlled.
Odesseus Track turns submitted applications into a persistent lifecycle.
Applied -> Employer response -> Assessment -> Interview -> Rejected / Withdrawn / Offer -> Accepted
Each application freezes:
The application timeline stores system, user, Email, and Calendar events in one history.
Phase 7 connects read-only Email and Google Calendar context to Odesseus Track.
Odesseus can detect:
Signals are deduplicated and linked to an existing tracked application before Odesseus changes the pipeline.
When an interview is detected, Odesseus creates an interview record connected to:
Ambiguous messages are not allowed to silently move an application.
Phase 7 requests only:
See docs/integrations/google.md for Vercel Connect configuration.
Phase 7 is provider-agnostic.
Email and Calendar are separate connection types. A user can connect Yahoo for email and Google Calendar for interviews, or any other supported combination.
OAuth providers use Vercel Connect. iCloud/custom IMAP secrets are stored in Supabase Vault; normal application tables store only the Vault secret reference.
The normalized downstream signal type is always either email or calendar; provider identity is stored separately.
The Interview Workspace is free and does not consume a Odesseus Live pass.
It combines:
Readiness can generate:
Odesseus does not run mock interviews in this phase.
Phase 9 carries interview context across rounds before Odesseus Live exists.
After a round, the candidate can record:
Odesseus creates a factual handoff that captures:
Later interview readiness automatically includes prior-round memory.
Phase 9 does not grade interview performance or predict hiring outcomes.
When Odesseus Live is introduced in Phase 10, transcript-derived memory can populate this same model automatically. Full post-interview analysis and follow-up remain Phase 11.
Odesseus Live provides private, on-screen interview guidance while the candidate remains the speaker.
gpt-live-transcribe.Opening the Live screen costs nothing.
One interview pass is consumed only after the realtime connection succeeds and the Live session atomically activates.
Reconnecting the same active session does not consume another pass.
Phase 11 closes the interview loop after Odesseus Live.
After a completed Live session, Odesseus can generate:
Odesseus does not:
Transcript-backed facts are merged into the current interview round memory.
Existing user-entered notes/signals are preserved rather than overwritten.
The updated handoff becomes context for future interview readiness.
Odesseus creates an editable follow-up draft from actual interview context.
The candidate must review/approve it before sending.
If an outbound Google connector is configured, Odesseus can send the approved draft through Gmail. Otherwise Odesseus opens the approved draft in the user's normal email app using a mailto handoff.
Read-only Email/Calendar connectors remain separate from optional outbound-send connectors.