Best Neurosity Crown Settings for Deep Work
You Bought a Formula 1 Car. Stop Driving It to the Grocery Store.
You own a $1,499 brain computer. Eight EEG channels. 256 samples per second. An onboard neural processing chip. brain-responsive audio that literally rewires its output based on your brainwaves. SDK access in JavaScript and Python. Real-time AI integration through MCP.
And you're using it with the default settings.
That's like buying a Formula 1 car and driving it to the grocery store in second gear. The machine is capable of extraordinary things, but only if you configure it to match what you're actually trying to do. For deep work, the difference between a default Crown session and a properly optimized one isn't subtle. It's the difference between vaguely knowing you were "kind of focused" and having a precise, repeatable system that tells you exactly when your brain is locked in, exactly when it's drifting, and exactly what to do about it.
This guide covers every setting, every configuration, and every technique that separates casual Crown users from the ones who've turned deep work into a science. We'll go from hardware basics (how you physically wear the thing matters more than you think) to software configuration to advanced SDK and AI integrations that most people don't even know exist.
Let's start with what your Crown is actually measuring when you sit down to work.
What Your Brain Actually Does During Deep Work
Before we touch a single setting, you need to understand what's happening under those 8 electrodes when you're genuinely locked into deep work. This isn't academic. Every optimization in this guide targets specific neural patterns, and knowing what they are turns you from someone following instructions into someone who understands why each setting matters.
The Crown's 8 sensors sit at positions CP3, C3, F5, PO3, PO4, F6, C4, and CP4. That's not random. Those positions cover your frontal cortex (where executive control lives), your central regions (motor planning and sensorimotor integration), and your parietal-occipital areas (spatial processing and visual attention). Together, they give you a full picture of the brain networks that power deep work.
Here's what those networks produce when you're genuinely focused:
Frontal beta (13-30 Hz): This is your concentration signal. When your prefrontal cortex is actively engaged in a task, maintaining working memory, suppressing distractions, executing decisions, beta power increases in the frontal channels (F5, F6). Higher frontal beta generally means more active, directed thinking.
Theta suppression (4-8 Hz): During unfocused mind-wandering, frontal theta tends to rise. During deep work, it drops. This suppression is your brain saying, "I'm not daydreaming right now. I'm here." The ratio between theta and beta in your frontal channels is one of the strongest markers of attentional engagement.
SMR, sensorimotor rhythm (12-15 Hz): This is the one most people have never heard of, and it might be the most important. SMR is a specific band of activity in the central channels (C3, C4) associated with calm, alert stillness. It's the brain state of a person who is physically relaxed but mentally sharp. Neurofeedback researchers have been training SMR for decades because it's the sweet spot between agitation and drowsiness.
Alpha patterns (8-12 Hz): Alpha is complex. In parietal-occipital regions (PO3, PO4), suppressed alpha means your visual attention system is engaged. In regions not relevant to your task, increased alpha means your brain is efficiently shutting down unnecessary processing. The pattern you want: low alpha where you're working, higher alpha where you're not.
Every setting we'll configure is designed to either improve the Crown's ability to detect these patterns or to create conditions that make these patterns more likely to emerge. That's the framework. Now let's build on it.
Setting 1: Electrode Contact (The Foundation Everything Else Depends On)
This is the single most impactful thing you can do, and it has nothing to do with software. If your electrodes aren't making good contact with your scalp, every other optimization in this guide is building on sand.
The Crown uses flexible rubber electrodes that need to touch your skin directly. Hair is an insulator. A single strand of hair between an electrode and your scalp can degrade signal quality by 40-60%. Multiply that across several channels and you're working with noisy, unreliable data that makes your focus scores meaningless.
Here's the protocol that works:
Before putting on the Crown, part your hair at the approximate sensor locations. You don't need to be surgical about it. The Crown sits in a headband-like position, with sensors along the sides and back of your head. Run your fingers through your hair to create natural parts where the sensors will land. For people with thick or curly hair, a wide-tooth comb can help create clearer paths.
When placing the Crown, position it so the front edge sits about two finger-widths above your eyebrows. Then press gently and rock the device slightly forward and backward. This lets the flexible electrodes settle into the gaps in your hair rather than sitting on top of it.
Check signal quality immediately. The Neurosity app shows a real-time signal quality indicator for each channel. You want all 8 channels green. If any channel shows yellow or red, don't just live with it. Remove the Crown, rework the hair at that position, and try again. A 30-second adjustment here saves you an entire session of bad data.
If a channel shows poor signal quality, try shifting the Crown just 2-3mm in the direction of that sensor. Tiny adjustments make enormous differences in electrode contact. Some users mark their ideal position with a small dot of washable marker on their forehead until the placement becomes muscle memory. It typically takes about a week of daily use to nail your positioning consistently.
For the best results, check signal quality again 5 minutes into your session. Body heat and natural moisture from your scalp actually improve electrode contact over time, so channels that were borderline at the start often improve. If they don't improve after 5 minutes, readjust.
Setting 2: Session Length and Structure
How long should a deep work session be? The answer is rooted in neuroscience, not productivity folklore.
Your brain operates on ultradian rhythms, roughly 90-minute cycles of higher and lower alertness that repeat throughout the day. During a cycle's peak, your capacity for sustained attention is at its maximum. During the trough, your brain is essentially requesting a reset. Fighting this rhythm doesn't make you more productive. It just makes you tired and unfocused while still sitting at your desk.
The optimal Crown deep work session is 90 minutes, structured like this:
| Phase | Duration | What's Happening | Crown Setting |
|---|---|---|---|
| Calibration | 5 minutes | Sit quietly, eyes open. Crown establishes your baseline brain state. | Run calibration in the app before starting work |
| Warm-up | 10-15 minutes | Begin your task. Focus score will be moderate. Your brain is transitioning. | brain-responsive audio on, Focus mode, volume 30% |
| Peak focus | 40-60 minutes | Focus score climbs. Frontal beta is high, theta is suppressed. This is where deep work happens. | Volume can increase to 40-50% if helpful. Don't check scores. |
| Decline | 10-20 minutes | Focus score starts dropping. This is natural, not failure. | Note the timing. This is your personal focus ceiling for this session. |
| Cooldown | 5 minutes | Wrap up current thought. Don't start anything new. | Switch to Calm mode. Review session data. |
The calibration phase deserves special attention. The Crown's focus and calm scores are relative to your baseline. If you skip calibration and jump straight into work, the algorithm doesn't know what "normal" looks like for you today. Maybe you slept poorly. Maybe you had three coffees. Your baseline shifts daily, and giving the Crown 5 minutes to learn today's baseline makes every score that follows more accurate.
Here's the "I had no idea" moment for most Crown users: your peak focus window isn't when you think it is. Most people assume they're most focused right when they sit down, energized and motivated. But the data usually tells a different story. Peak focus scores typically show up 20-45 minutes into a session, after the brain has fully transitioned out of its default mode network and into task-positive network activation. Those first 15 minutes feel productive because you're doing things. But the brain-level engagement that defines true deep work usually comes later.
Track this across a week. You'll start to see your personal pattern, and you can structure your hardest tasks to land in that peak window.
Setting 3: brain-responsive audio Configuration
brain-responsive audio built with the Crown's SDK is one of its most powerful features, and also the one most people configure incorrectly.
Here's how it works: the Crown reads your real-time brainwave state and modulates the audio it produces to nudge your brain toward the target state. In Focus mode, when it detects your attention drifting (rising theta, falling beta), it subtly shifts the audio characteristics to promote re-engagement. In Calm mode, it does the opposite, guiding you toward relaxed alpha states.
This isn't a playlist. It's a closed-loop neurofeedback system disguised as background music.
The settings that matter:
Mode selection. Use Focus mode for analytical deep work: coding, writing, data analysis, anything that requires sustained directed attention. Use Calm mode for creative deep work: brainstorming, design, free writing, anything that benefits from loose associative thinking and a quiet inner critic. This isn't a preference. It's a neurological match. Analytical work relies on frontal beta and active prefrontal control. Creative work often benefits from the alpha-theta border state that Calm mode promotes.
Volume. This is where most people go wrong. They crank it up because louder feels more immersive. But the neuroadaptive system works best when the audio is just barely in your conscious awareness. Think 30-50% volume. The audio should feel like a texture in the room, not a concert in your head. If you're actively listening to it, it's too loud. The point is to let it work on the edges of your awareness, where it can influence brain state without becoming a distraction itself.
When to switch modes mid-session. Some advanced users start a deep work session with 10 minutes of Calm mode before switching to Focus mode. The logic is sound: Calm mode helps deactivate the default mode network and reduce the mental chatter that clutters the transition into deep work. Once you're settled, switching to Focus mode provides the beta-promoting stimulus that sustains directed attention. Try it for a week and watch your time-to-peak-focus in the data. For many users, it drops by 5-10 minutes.
brain-responsive audio built with the Crown's SDK works best in a quiet environment. If you're in a noisy space, use noise-canceling headphones underneath the Crown (earbuds work better for fit). The brain-responsive audio plays through the Crown's own speakers, so you can layer it on top of noise cancellation. But avoid playing your own music simultaneously. Two competing audio streams create cognitive interference that fights the very focus you're trying to build.
Setting 4: Focus Score Calibration and Interpretation
Your focus score is a number between 0 and 1 that represents your brain's current level of directed attention. It's computed from the raw EEG data across all 8 channels, weighting the patterns we discussed earlier: frontal beta, theta suppression, SMR activity, and alpha distribution.
But here's what most users get wrong: they treat the focus score like a grade. A 0.8 is an A. A 0.4 is an F. That's not how it works.
The focus score is a real-time biofeedback signal, not a performance evaluation. A score of 0.4 during creative brainstorming might be exactly right. A score of 0.9 sustained for 60 minutes might indicate ADHD and flow state that's going to leave you exhausted. The number is useful only in context.
Here's how to calibrate your relationship with the score:
Spend your first week just observing. Don't try to "improve" your score. Just work normally and note what scores you see during different activities. You're building a personal baseline map. What's your average during email? During coding? During deep writing? During meetings? After a week, you'll know what your brain considers "normal" for each activity.
Identify your personal deep work range. For most people, genuine deep work happens in a focus score range of 0.6-0.85. Below 0.6, you're likely in shallow work territory. Above 0.85, you might be in a hyperfocus state that's hard to sustain. Your specific range may differ. The data will tell you.
Watch for patterns in score drops. When your focus score drops mid-session, check what happened. Did you glance at your phone? Did a notification pop up? Did you hit a confusing part of the task? Focus drops have causes, and the Crown makes those causes visible. Over time, you'll build a catalog of your personal focus killers, specific and actionable, not vague advice about "minimizing distractions."
Setting 5: Notification Management and Environment
This one's simple but most people skip it. Every notification that reaches you during deep work costs you 23 minutes of recovery time. That's not an exaggeration. It's from a study by Gloria Mark at UC Irvine. Twenty-three minutes to return to the same depth of focus after a single interruption.
The Crown can tell you exactly how expensive each interruption is. But the smarter move is to prevent them.
On your Crown: Make sure device notifications are disabled during deep work sessions. The Crown should be a sensor during deep work, not a notification device. Go to Settings in the Neurosity app and disable all alerts for your session.
On your computer: Use Do Not Disturb mode. On macOS, schedule Focus modes that automatically activate during your deep work blocks. On Windows, use Focus Assist. Close Slack. Close email. Close everything that isn't your work and your Crown dashboard.
On your phone: Put it in another room. Not face-down on your desk. Not in your pocket on silent. In another room. Research from the University of Texas at Austin found that the mere presence of a smartphone, even when turned off, reduces available cognitive capacity. Your brain spends resources monitoring it even when you think you're ignoring it.
Physical environment. Temperature between 68-72F (20-22C). Adequate hydration within arm's reach so you don't need to get up. Consistent lighting, avoid glare that causes squinting, which shows up as muscle artifact in your EEG. If you wear glasses, make sure they don't interfere with the Crown's sensor positions near F5 and F6.
Setting 6: Focus Mode vs. Calm Mode, A Decision Framework
We touched on this in the audio section, but it deserves its own treatment because choosing the wrong mode for your task type is one of the most common mistakes.
| Work Type | Recommended Mode | Why | Expected Focus Score Range |
|---|---|---|---|
| Coding / debugging | Focus | Requires sustained directed attention and working memory | 0.65-0.85 |
| Technical writing | Focus | Sequential logical construction needs active prefrontal engagement | 0.60-0.80 |
| Creative brainstorming | Calm | Loose associative thinking thrives in alpha-theta states | 0.35-0.55 |
| Design and visual work | Calm | Spatial reasoning and aesthetic judgment benefit from relaxed attention | 0.40-0.60 |
| Email and admin | Neither | Save your Crown battery for sessions that matter | N/A |
| Reading and research | Calm then Focus | Start Calm for absorption, switch to Focus for synthesis | 0.45-0.70 |
| Problem solving (stuck) | Calm | The prefrontal cortex often blocks insight. Calm mode helps it step aside. | 0.30-0.50 |
The last row contains a principle worth highlighting. When you're stuck on a hard problem and you've been grinding on it for 30 minutes with no progress, your instinct says push harder. But the neuroscience says the opposite. Insight, that sudden "aha" moment when the solution appears, is associated with a burst of gamma activity preceded by increased alpha. Your brain needs to relax its grip before it can see the answer. Switching to Calm mode when you're stuck isn't giving up. It's giving your brain permission to solve the problem the way it actually wants to.
Setting 7: Custom Dashboards with the SDK
This is where the Crown goes from a consumer device to a scientific instrument. The Neurosity JavaScript and Python SDKs give you direct access to raw brainwave data at 256Hz, power spectral density, frequency band decomposition, focus scores, calm scores, and signal quality metrics.
For deep work optimization, here's what you can build:
A personal focus tracker. Log your focus score every second during work sessions. After a month, you'll have a dataset that shows your focus patterns across time of day, day of week, task type, sleep quality, caffeine intake, and anything else you choose to correlate. Most Crown users who build this discover something they didn't expect. Maybe their best focus day is Wednesday, not Monday. Maybe their afternoon sessions are better than morning ones despite what they always believed.
A distraction detector. Write a script that monitors your focus score and triggers an alert (a subtle sound, a screen flash, a Slack message to yourself) when your score drops below a threshold for more than 30 seconds. This catches mind-wandering before it becomes a 15-minute detour. The SDK makes this about 20 lines of JavaScript.
A session quality scorer. After each deep work session, automatically compute metrics like time-to-peak-focus, duration of peak focus, number of focus drops, and average score. Compare across sessions. This turns subjective feelings about "good days" and "bad days" into objective measurements.
Using the Neurosity JavaScript SDK, you can subscribe to real-time focus scores with just a few lines of code. The focus() observable gives you a stream of scores between 0 and 1. Combine that with the signalQuality() observable to validate that your electrode contact is solid before trusting the data. The SDK's brainwaves("powerByBand") observable gives you theta, alpha, beta, and gamma power for each channel, which you can use to build custom metrics that go deeper than the default focus score. All of this runs in Node.js, so you can pipe it into any logging system, database, or visualization tool you prefer.
The SDK documentation at neurosity.co/developers covers the full API. If you've never worked with observable streams, the learning curve is about an afternoon.
Setting 8: MCP Integration for AI-Assisted Deep Work
This is the setting most Crown owners don't know exists, and it's the one that might matter the most.
The Neurosity MCP (Model Context Protocol) server lets AI tools like Claude access your real-time brain state data. Think about what that means for a second. Your AI assistant doesn't just know what you asked it. It knows how your brain is performing right now.
Here's how that changes deep work:
Context-aware AI responses. When your focus score is high, Claude can give you dense, detailed responses because your brain can handle them. When your focus score is dropping, it can give you shorter, clearer answers that don't overwhelm a brain that's already losing steam. This isn't theoretical. It's what the MCP integration enables today.
Automated session management. You can build a system where Claude monitors your brain state and suggests breaks when your focus score has been declining for 10+ minutes. Not based on a timer. Based on what your brain is actually doing. A Pomodoro timer tells you to take a break every 25 minutes regardless of your state. An MCP-connected system tells you to take a break when your brain says it's time.
Work prioritization by brain state. Imagine starting your workday by telling Claude, "Here's my task list," and Claude responds with, "Based on your current brain state, your focus score is trending high, so start with the hard coding task. Save email for after lunch when your data shows you typically have lower focus." That's not a hypothetical. With MCP and a few weeks of historical data, that's buildable today.
The MCP server connects through the same SDK ecosystem, so if you've already built custom dashboards, adding AI integration is an incremental step, not a rearchitecture.
Putting It All Together: The Complete Deep Work Protocol
Here's the full protocol, assembled from everything above, for a single optimized Crown deep work session:
5 minutes before: Put phone in another room. Close all non-essential apps. Enable Do Not Disturb. Set water within reach. Part hair at sensor sites.
Minute 0: Put on the Crown. Check all 8 channels for green signal quality. Adjust if needed.
Minutes 0-5: Calibration. Sit with eyes open, breathing normally. Don't start working yet. Let the Crown establish today's baseline.
Minutes 5-15: Start with Calm mode audio at 30% volume. Begin your task slowly. Don't rush. Let the transition happen naturally.
Minute 15: Switch to Focus mode. Increase volume to 40% if it feels right. Your brain should now be shifting out of default mode network and into task-positive activation.
Minutes 15-75: Deep work. Don't check your focus score. Don't touch your phone. Don't open email. Work. The Crown is monitoring everything. You'll review it later.
Minutes 75-85: You'll feel the decline. Your focus score is dropping. This is your brain requesting a state change. Start wrapping up your current thought or subtask. Don't start anything new.
Minutes 85-90: Switch to Calm mode. Review your session data. Note your peak focus period, your average score, and any sharp drops that might correspond to specific interruptions.
After the session: Take a genuine 15-20 minute break. Walk. Look at something far away. Let your brain reset. Then, if your schedule allows, run a second session. Most people can do 2-3 high-quality Crown sessions per day. Beyond that, cognitive fatigue makes the returns drop sharply.
The Question Nobody Asks (But Should)
Here's the thing about deep work settings that goes beyond any individual configuration tip.
Every time you run an optimized Crown session, you're generating data about the most complex object in the known universe: your brain. Not someone else's brain. Not an average across 200 research subjects. Your brain, on this day, doing this work, in this state.
Over weeks and months, that data accumulates into something nobody in human history has had before: a detailed, objective, longitudinal record of their own cognitive performance. You can see which days you were sharp and which days you were struggling. Which tasks engage your brain and which ones bore it. Which times of day your prefrontal cortex is firing on all cylinders and which times it's running on fumes.
Most people spend their entire careers guessing about this stuff. Guessing which morning routine works. Guessing whether meditation helps their focus. Guessing whether they're actually more creative at night or just telling themselves that.
You don't have to guess.
The Crown turns your brain from a black box into something you can observe, measure, and systematically optimize. The settings in this guide are the starting point. But the real power is in what happens after you've been running optimized sessions for a month and you look at the data and see something about your own mind that nobody could have told you, because nobody else has ever had access to this information.
That's not a feature of a gadget. That's the beginning of a fundamentally different relationship with your own brain.
And you get there by starting with something as simple as parting your hair.