Questions,
answered.

20 answers about the environment, the models, your code, and the beta. Search, or browse by topic.

20 ANSWERS

Cloud Mac

Why does a coding agent need a Mac?

Some important development work only happens on macOS: native Apple apps, Simulator-based testing, desktop Safari, and the tools many teams use every day. JY Code gives your agent a Mac environment in the cloud, so it can build and check work where your project is meant to run.

What architecture does the cloud Mac run on?

Workspaces are designed around Apple Silicon (arm64) macOS, matching modern MacBook Pro developer machines as well as native iOS Simulator and arm64 Homebrew binaries.

What kinds of projects is the cloud Mac designed for?

Apple platform apps, web apps that need Safari and other browsers, and backend or command-line projects from teams that develop on Macs. The Cloud Mac page explains why each one benefits from macOS.

Does the agent run on my own computer?

No. The development work in a session happens on the cloud Mac. You describe the task and review the results, and your own machine stays free for your work.

Which tools will be available in the workspace?

We are designing the workspace around Apple, web, and backend development, with tools such as Xcode, the iOS Simulator, Instruments, Safari, Node.js, Bun, Rust, Go, Python, Homebrew, and a Unix shell. We will publish exact versions with beta access.

Models

Which models can I use?

The directory lists 20 models from 8 labs: Anthropic, OpenAI, Google, DeepSeek, Meta, xAI, Mistral, and Qwen. They cover everyday coding, reasoning, interfaces and large repositories, quick iterations, and open-weight work. Available models may change during the private beta.

How should I choose a model?

Start with an everyday coding model for most tasks. Reach for a reasoning model when a bug is hard to pin down or a design decision has real tradeoffs, and a vision-capable model when the result needs to be checked on screen. The Models page groups each model by the work it fits.

Can I change models during a task?

That is part of how we are designing JY Code: start with one model for planning, hand implementation to a fast daily coder, and bring in a vision model to verify UI output on the same workspace.

Can I bring my own model API keys?

We are exploring options for teams with existing model provider enterprise agreements or API keys. Mention your setup when you request access.

Agent harness

What is the JY Code agent harness?

A model alone only predicts text, and a Mac alone only runs binaries. The harness is the control loop in between: it indexes repository context, exposes atomic edit and macOS GUI tools, compacts noisy compiler logs, and enforces human review gates.

How does the harness prevent long build logs from flooding model context?

Build tools like xcodebuild or Playwright can output tens of thousands of lines. The harness parses compiler and test output into structured file-and-line diagnostics, folding routine build noise by around 90% so reasoning stays sharp over long sessions.

Does the harness follow our repository's AGENTS.md and linter rules?

Yes. Project instruction files (such as AGENTS.md or CLAUDE.md), formatter rules, and typecheck gates are loaded during the Ground stage and verified automatically before a session packages its diff.

What happens if a build fails or a model gets stuck?

The harness tracks git checkpoints and compiler error signatures across turns. If edits oscillate or an external requirement is ambiguous, it rolls back cleanly to the last good checkpoint and surfaces a concise question rather than looping endlessly.

Code & data

How will repositories and secrets be handled?

Your code deserves clear answers before you connect it. Repository access is scoped to what you authorize, environment secrets are injected only for active sessions, and full documentation of workspace controls ships with beta onboarding.

Will my code be used to train models?

Before you connect a repository, we clearly surface data-retention and zero-training policies for each model provider, and allow teams to restrict sessions to approved labs or open-weight models.

Does the agent push directly to my main branch?

Never by default. Sessions work on isolated feature branches and prepare changes for human review—you decide what gets opened as a pull request or merged.

Beta & access

Who can join the private beta?

JY Code is in private beta for individual developers and engineering teams. Request access with your email, and teams can contact us directly about their projects.

How much will JY Code cost?

We have not announced general pricing yet. Cloud Mac compute and model usage details will be shared transparently with beta participants.

Can our team request custom pre-installed dependencies?

Yes. Write to business@jarvisforyou.com with your target Xcode version, SDKs, or internal package registry requirements so we can align your beta workspace.

What happens after I request access?

We invite developers and teams in cohorts as capacity expands, sharing workspace documentation, supported models, and onboarding steps when your slot opens.

Still have a question?

Tell us about your project. We read every message.