Pines GitHub
Local-first AI for iPhone and Apple Watch

Pines

Run local models, bring in private context, add cloud power only when it earns the trip, and keep conversations close from your wrist.

View source Check availability
iPhone app in development Watch companion included Source available today
Route Local first
Pines

Chats

Pines app icon
Qwen3 4B MLX Vault on
You

Summarize the field notes in my private vault and keep it local.

Pines

I found 4 relevant chunks. Local model route is ready.

Tool

Vault search: 4 matches, no cloud context shared.

Ask Pines...
Connected

Pines

Live chat
Planning Notes Qwen3 4B
Quick reply Summarize
Vault Documents, chunks, OCR, embeddings
iPhone workbenchApple Watch companionMLX on deviceCloud only by choicePrivate vaultTool approval
Why Pines

Your phone can be more than a remote control for cloud chat.

Pines brings local models, optional cloud providers, private context, and tools into one iPhone workspace with an Apple Watch companion for quick access.

Local chat, vision, embeddings

Use capable models on iPhone

Install supported MLX models and use local inference for everyday work, private drafts, and context-heavy questions that should stay close.

OpenAI-compatible, OpenRouter, Anthropic, Gemini

Add cloud power only when you choose it

Bring your own provider keys for harder tasks. Pines keeps cloud routing explicit and never turns a local request into a cloud request silently.

PDF, images, Markdown, JSON, CSV

Keep useful context in a private vault

Import files and notes so Pines can retrieve the right material later instead of asking you to paste the same context again.

Default Boundary

On device until you decide otherwise.

Pines is local-first by default. Chats, model state, vault documents, embeddings, attachments, and normal inference stay on device unless you configure a provider and choose a cloud route.

Local only Prefer local Cloud allowed Cloud required

Visible Consent Points

  • API keys stay in Keychain.
  • Normal inference remains local unless a cloud route is configured and chosen.
  • Private vault and MCP resource context require per-turn approval before cloud use.
  • Tool specs declare permissions, side effects, network policy, and timeout.
  • CloudKit sync is optional and deliberately excludes secrets and model binaries.
MCP Streamable HTTP 
tools/list        enabled per server
resources/read    selected by user
prompts/get       editable arguments
sampling/create   reviewed before return
Tools And MCP

Connect useful systems while keeping actions legible.

MCP servers can bring tools, resources, prompts, subscriptions, and sampling into Pines. Network operations, private context, browser actions, and sampling results remain approval-aware.

Read the MCP notes
App Previews

The iPhone app makes model choice and privacy boundaries visible.

Pines is built around the moments that matter in daily use: local chat, model readiness, private context, cloud approval, and Watch continuity.

Pines Local route active
You

Summarize the project notes in my vault and keep this local.

Pines

I found the relevant local context. No cloud provider is needed for this turn.

Local route

Private Chat

Stays on device
  • Choose an installed model
  • Attach private notes
  • Stream without cloud
MLX ready

Model Library

Know before install
  • Footprint and capability checks
  • Verified local picks
  • Runtime diagnostics
Your material

Vault Context

Searchable when needed
  • Import files and notes
  • OCR and chunking
  • Retrieval for chat
Visible consent

Cloud Approval

You choose the boundary
  • Send with context
  • Send without context
  • Keep it local
Product Tour

One app surface for the AI work that usually gets scattered.

Pines gives the major pieces of modern AI work one coherent iPhone surface: model choice, private context, cloud reach, tool use, MCP, and Watch access.

Daily workspace

Talk to the model that fits the moment.

Start with a local model, bring in files, choose a provider when a task needs outside reach, and keep private context decisions visible.

  • Model picker per thread
  • Attachments with capability checks
  • Cloud context approval
Getting Started

Designed so the first useful step does not require cloud setup.

Pines is meant to feel calm on day one: begin locally, add your own material, then connect cloud providers and tools only when your workflow needs them.

01

Open a local chat

Start with an on-device route so the first experience is useful before any provider keys are involved.

02

Choose a model

Review local model size, capability, and readiness before downloading an MLX model for everyday use.

03

Add your context

Import notes, PDFs, images, Markdown, JSON, CSV, or plain text so Pines can retrieve what matters later.

04

Add cloud reach

Connect BYOK providers for harder tasks while keeping private-context approval visible per turn.

05

Bring it to your wrist

Use the Watch app for quick replies, conversation status, cancellation, and pending request recovery.

What It Is For

A personal AI workspace for people who care where the work runs.

Think privately

Ask ordinary questions, draft notes, and work through personal context without making every prompt a network request.

Research with context

Use vault retrieval, web fetch, search, and MCP resources when a conversation needs more than memory.

Switch routes clearly

Keep local models and BYOK providers in one workflow instead of spreading work across apps and dashboards.

Stay close on Watch

Check conversations, send quick replies, stop active runs, and recover pending requests from Apple Watch.

Availability And Trust

Clear expectations before you build, follow, or install.

Availability

Pines is source-available now. Public App Store or TestFlight availability will be announced only when distribution is ready.

License

PolyForm Noncommercial 1.0.0. Commercial use requires a separate written Schtack license.

Platforms

Built for iPhone with an Apple Watch companion, Live Activity support, and shared Swift packages.

Data boundary

Local-first defaults, Keychain secrets, optional iCloud sync, and explicit cloud context approval.

Models

Local MLX models are treated as a first-class path, with provider routes available when configured.

Source

The code, architecture notes, security model, MCP notes, and current status are available on GitHub.

FAQ

Straight answers about Pines today.

Is Pines a finished App Store app?

No. It is a working production-oriented foundation with final App Store hardening and device acceptance still in progress.

Does Pines require cloud AI?

No. Local execution is a first-class route. Cloud is BYOK-only and explicit.

Can cloud providers see vault context automatically?

No. Private local context requires a visible per-turn approval path before cloud use.

Why source-available instead of open source?

The repository is available for noncommercial inspection, building, and contribution under PolyForm Noncommercial 1.0.0. Commercial use needs a separate license.

What should a new visitor do first?

Read the status page for maturity, then follow GitHub releases or inspect the source.

Open To Inspect

The product story is backed by a source-available Swift codebase.

Pines is not a black-box landing page. The repository includes the SwiftUI app, shared core contracts, persistence, runtime bridges, model lifecycle services, policy-gated tools, and Watch support.

View source Developer README
SwiftUI app shellPinesCore contractsGRDB persistenceMLX runtime bridgeCloud providersMCP clientTool policy gateWatch protocol
Current Status

Transparent about what is ready and what is still being hardened.

Pines already has the iPhone app foundation, Watch companion, local model runtime, BYOK providers, vault ingestion, MCP support, tool approval, audit surfaces, and release validation. Public distribution still depends on real-device acceptance and final App Store polish.

Read status