Philo is the IDE for your daily notes.
Build widgets directly inside your notes. Keep daily planning in one timeline. Let unfinished and recurring work come back automatically. Keep everything as plain markdown on disk.
Philo is built for the gap between capture and execution. Instead of writing something down and rebuilding the context later in another tool, you stay inside the note and keep moving.
Most journaling apps are good at capture and weak at execution. Philo is designed to collapse that gap.
The core bet is simple:
- daily notes should help you run what you thought, not just remember it
- unfinished tasks should carry forward until they are done
- recurring work should reappear automatically
- small tools should be cheap to generate right where the note needs them
- Keeps older notes in one continuous timeline instead of hiding them behind separate tabs and files
- Rolls unfinished tasks into today automatically when the date changes
- Brings recurring tasks back on schedule so your planning surface rebuilds itself
- Generates disposable widgets inline for one-off tools, trackers, calculators, and experiments
- Lets you keep the useful widgets in a small reusable library
- Stores notes as plain markdown on disk and works with existing Obsidian vaults
- Supports markdown-native content like images, wiki links, and Excalidraw embeds
- Includes optional AI features for note chat, search, and dry-run edits inside the app
Philo keeps tomorrow, today, and past notes close together so the page already knows what was in flight when you open it.
Many tools only need to exist for a day or a week. Philo makes widgets cheap to create, easy to delete, and reusable only when they earn it.
Your notes stay as files you control. Philo is meant to sit beside your vault, not replace it.
Philo is built to make daily notes lighter, not turn them into another subscription silo.
⌘⇧Bbuild a widget from the current selection⌘Jopen note chat⌘Fsearch notes⌘Popen the widget library⌘,open settings
- Website: philo.so
- Blog: Notes from the team
- Releases: GitHub releases
- Source: GitHub repository
Tauri v2, React 19, TypeScript, TipTap, Tailwind CSS v4, and Rust.
Philo's Settings -> Google Account flow uses Philo's bundled desktop OAuth client. End users only need to click Continue with Google in settings and complete consent in their browser.
If you are maintaining Philo's Google Cloud project, make sure:
- The Gmail API and Google Calendar API are enabled.
- The OAuth consent screen is configured in
Google Auth platform. - The bundled desktop OAuth client remains active on the project.
GOOGLE_OAUTH_CLIENT_SECRETis available in local build envs and GitHub Actions secrets if that client requires a secret during token exchange.
For local desktop development, put GOOGLE_OAUTH_CLIENT_SECRET=... in the repo root .env or export it in your shell before starting pnpm dev. If you want to override the bundled client ID locally, GOOGLE_OAUTH_CLIENT_ID=... is also accepted. The desktop Tauri launcher reads those values and passes them through to Rust and Vite before startup.
Philo currently requests:
openid,email, andprofilehttps://www.googleapis.com/auth/calendar.events.readonlyhttps://www.googleapis.com/auth/gmail.readonly
Philo can connect multiple Google accounts. Account metadata is stored in settings.json, while access and refresh tokens stay in the OS credential store.
If your OAuth consent screen is still in testing and your audience is external, add your Google account as a test user before signing in. Gmail read-only is a restricted scope, so a public rollout may require Google verification.
- Data storage and configuration
- Markdown sync and editor rendering
- File and folder organization
- Widget persistence and lifecycle
Philo is licensed under the GNU General Public License v3.0 or later. See LICENSE.