Private AI on your Mac. Chat, dictation, meeting notes, and a local agent in one open source workspace.
# Add to your Claude Code skills
git clone https://github.com/open-software-network/os-juneos-june is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by open-software-network. Private AI on your Mac. Chat, dictation, meeting notes, and a local agent in one open source workspace. It has 172 GitHub stars.
os-june's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/open-software-network/os-june" and add it to your Claude Code skills directory (see the Installation section above).
os-june is primarily written in TypeScript. It is open-source under open-software-network on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh os-june against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.

Most AI apps ask you to hand over your most sensitive data and trust them with it. Every prompt, file, and meeting reveals something about you, and a cloud agent with that reach is a remote company's window into your work.
June is built the other way around. The app and the agent run on your Mac. Notes, recordings, transcripts, files, sessions, and agent memory stay on your machine by default. When June needs model inference, the request goes through June API, an open source, TEE-attested service that keeps provider keys server-side and routes to private models with zero data retention by default. You do not have to take any of this on faith: the entire product is MIT licensed, and the exact code serving production is cryptographically verifiable.
Local by default. App state, recordings, transcripts, and agent memory live on your machine. The agent runs locally inside a macOS write-jail unless you opt a session out.
Private models. Model calls default to private Venice models with zero data retention: nothing stored, no training. Anonymized third-party models are opt-in, and those providers may retain what they receive under their own policies.
Minimal retention. Open Software's services store account, login, and billing records. Prompts, audio, transcripts, and files are not among them.
Verifiable, not promised. June API runs in an Intel TDX confidential VM on Phala Cloud, and its trust chain has three public anchors:
org.opencontainers.image.revision label.build-june-api.yml
publishes ghcr.io/open-software-network/june-api;
deploys pin immutable per-commit tags recorded as signed deploy/<env>/<sha> git tags.Every deployment serves a self-contained walkthrough at
/verify. The chain proves the
code running in the confidential VM, not what upstream model providers do
with what they receive, which is why zero-retention routing is the default.
June runs on macOS 14 or later, Apple Silicon and Intel. Releases are signed,
notarized, and auto-updating, with stable and rc channels switchable
in-app. It is free to start.
If you use Homebrew, this is the recommended way to install:
brew install --cask open-software-network/tap/june
Windows builds cover the app shell, sign-in, microphone recording, notes, and the bundled agent runtime, but not global dictation paste, system audio capture, or the macOS sandbox. macOS is the primary target.
This repo contains the full product: the desktop app and the service that powers its metered AI calls.
src/ React and TypeScript frontend
src-tauri/ Tauri v2 Rust desktop backend and native helpers
june-api/ June API: models, transcription, generation, and billing
docs/ Architecture notes, ADRs, subsystem guides, and runbooks
spec/ Enforceable coding rules
specs/ Feature specs, plans, and validation notes
The desktop app never holds provider or OS Accounts App API keys; those live only in June API. Start with docs/index.md for the full doc map, CONTEXT.md for the domain glossary, and AGENTS.md for the contributor guide.
You need Node.js with pnpm 9 and a Rust toolchain.
git clone https://github.com/open-software-network/os-june
cd os-june
cp .env.example .env
cp june-api/.env.example june-api/.env
# Edit june-api/.env and set JUNE__UPSTREAMS__VENICE__API_KEY.
pnpm install
pnpm tauri:dev
The example env files default to open source local mode: no OS Accounts login,
no billing, and a local June API authenticated by a shared bearer token.
Provider keys belong only in june-api/.env, never in the root desktop
.env. A Venice API key is enough for transcription, generation, and
dictation cleanup.
See docs/development.md for the day-to-day development guide (ports, onboarding replay, local data, permissions, agent skills, and test commands) and docs/configuration.md for the full configuration reference, including exposing your own models and running against OS Accounts.
June ships near-daily releases and development happens in the open.
pnpm check # lint and format (Biome)
pnpm typecheck
pnpm test # frontend (Vitest)
pnpm test:rust # desktop Rust
pnpm test:june-api # June API
make verify mirrors CI. Start with CONTRIBUTING.md, then
AGENTS.md for the full contributor guide; the enforceable UI
rules live in spec/. Report bugs through GitHub issues, and
report security vulnerabilities privately per SECURITY.md.
June is MIT licensed. See LICENSE. Bundled third-party runtime notices are tracked in THIRD_PARTY_NOTICES.md.