Unlimitless
Keeps the decisions you've settled, with the why, and serves them back unprompted in whatever AI surface you're in next. Works across Claude, Claude Code, ChatGPT, Cursor, Cline, Kilo Code, opencode, Copilot, Antigravity and Devin Desktop.
Documentation
Surfaces
Claude OAuthClaude Desktop OAuthClaude Code OAuthChatGPT OAuthCursor OAuthAntigravity OAuthopencode OAuthDevin Desktop OAuthCline OAuthKilo Code OAuthGitHub Copilot OAuth
1
Open Settings, then Connectors
In Claude on the web, choose Add custom connector.
2
Paste the URL
Name it Unl, paste https://api.unlimitless.ai/mcp, and add it.
3
Say "connect to unl" in any chat
Unl greets you, you sign in once with OAuth, and your world loads. Every session after starts inside it.
What you'll see on first connect.
Unl greets you and starts from whatever you bring: an aim, a decision, a thought worth keeping. Every session after picks up where you left off. Nothing to configure before it's useful.
1
In Claude Desktop, choose Add custom connector.
2
3
Approve the connection
Your credentials stay held by Desktop, on your machine.
4
Say "connect to unl"
Sign in once when greeted. Done.
Desktop holds the credential.
Your sign-in stays on your machine, held by Desktop rather than by us.
1
Add Unl from your terminal
One command, run in your project. No key, no header:
claude mcp add --transport http unl https://api.unlimitless.ai/mcp
2
Sign in over OAuth
Run /mcp, choose unl, and pick Authenticate. You sign in once in the browser and the token is held for you.
3
Name your venture if you keep more than one. That one line is what turns a cold session into a connected one, and it is how a prompt you paste to any coding agent should begin. Your agent wakes into your world: the brief at the head of the queue, the rulings that govern it, the reasoning behind them.
OAuth here too.
Coding surfaces sign in the same way as the chat surfaces: OAuth, once. A personal key belongs to the API at api.unlimitless.ai, and is never what connects you.
1
Turn on developer mode
In Settings, open Plugins, then switch on Developer mode.
2
Create the connector
Choose New Plugin, name it Unl, and paste https://api.unlimitless.ai/mcp as the server URL. Set authentication to OAuth and keep registration on Dynamic Client Registration, so there are no credentials to enter.
3
Untick "OIDC enabled"
Open Advanced OAuth settings and untick OIDC enabled so ChatGPT requests only email and profile. Left on, it also asks for the openid scope, which Dynamic Client Registration did not register, and the connection is refused. This one toggle is the difference between connecting and bouncing.
4
Sign in once with OAuth when greeted. Your world travels with you, whichever model you're in.
Steps follow OpenAI's developer mode guide: ChatGPT connector docs
Same world, different model.
Unl holds your reasoning, not the model's. Move between models and your settled decisions move with you.
1
Add Unl to your MCP config
In .cursor/mcp.json, the URL alone. No key, no header:
{ "mcpServers": { "unl": { "url": "https://api.unlimitless.ai/mcp" } } }
2
Cursor uses OAuth, not a key: it discovers the sign-in from the server and prompts you. Approve once, and it holds the token.
3
Ask Cursor to connect to unl
The agent inherits what you decided, with the why, before it writes a line.
OAuth here too.
Same as Claude Code: Cursor connects over OAuth, once. A personal key belongs to the API, never the thing that connects you.
1
Install it and sign in
Download from antigravity.google, drag it to Applications, and sign in with Google on first run, which lands you on the free Individual plan. The Build-with-Google plugin screen can be skipped whole; none of it is needed for unl.
2
Add Unl by file: the MCP Store has no custom route
Antigravity's MCP Store has no add-your-own option, so a custom server goes in by config file. In ~/.gemini/config/mcp_config.json. Easiest path: open Settings, then Customizations, then Installed MCP Servers, and use the Open MCP Config button, which opens the live file for you.
{ "mcpServers": { "unl": { "serverUrl": "https://api.unlimitless.ai/mcp" } } }
3
Use serverUrl, not url
This is the one that catches people: Antigravity requires serverUrl. Google's own docs list url and httpUrl as not supported here. For a single project instead of every one, the same block works in .agents/mcp_config.json.
4
Restart fully, then expect a red Unauthorized
After a full restart, unl appears with a red Unauthorized error against it. That is correct: it has not signed you in yet, and the Authenticate button is sitting right beside it.
5
Authenticate, and paste the code back
Authenticate opens your browser to approve the connection. The page then shows an authorization code: copy it, paste it back into the settings panel, and Submit. Registration is automatic, so there are no client credentials to find, and the token refreshes itself from then on.
6
Approve the first tool call
Tools arrive in Ask mode, so Antigravity asks before each call. Say yes the first time. Without that, a working connection can look like a stuck one.
7
Ask Antigravity to connect to unl
In a New Conversation, say: Connect to unl. Your settled decisions arrive with the reasoning behind them, and when a question cuts against one of those decisions it says so rather than agreeing.
Walked on Antigravity v2.4.3, 4 August 2026.
OAuth, and one file.
No key, no client credentials, no store listing to wait for. One config line and a code you paste back once. After that Antigravity holds the token and refreshes it itself.
1
Install opencode
One line in your terminal. Then open a new window, or run source ~/.zshrc. Until you do, the shell you are standing in does not yet know the command.
curl -fsSL https://opencode.ai/install | bash
2
Add Unl to your config
In ~/.config/opencode/opencode.json, the URL alone. No key, no header:
{ "$schema": "https://opencode.ai/config.json", "mcp": { "unl": { "type": "remote", "url": "https://api.unlimitless.ai/mcp", "enabled": true } } }
3
Pick your model provider
Run /connect. Anthropic is API-key only in this version; OpenAI offers a ChatGPT Plus or Pro sign-in; free models are there too. Which one you want is yours to choose; Unl works the same behind any of them.
4
Sign in to Unl from the shell
/mcps will show unl as needing auth. The sign-in runs from your terminal, not from inside the chat:
opencode mcp auth unl
5
If the status bar reads "0 MCP", carry on
It counts connected servers, so it sits at zero until the sign-in finishes. It is not telling you the config is wrong.
6
Say "Connect to unl"
Name your venture if you keep more than one. Your world loads: the brief at the head of the queue, what you settled, and why it stands.
Steps re-checked against opencode's own guide, and if your screens differ from these it has moved and this page has not yet: opencode MCP docs
Walked on opencode 1.18.12, 4 August 2026.
A terminal sign-in, then the same world.
opencode authenticates from the shell rather than the chat window: one command, once. What arrives afterwards is what arrives everywhere else.
1
Open the MCP marketplace for Devin Local
Devin Desktop carries TWO separate marketplaces with two separate Installed lists: the Devin Local one and the Cascade one. Use the banner link to switch to Devin Local. A server added to the other list will not be there when the agent looks.
2
Add custom MCP
The marketplace has an Add custom MCP route. That is the manual path, and the one these steps use.
3
In ~/.config/devin/mcp_config.json. The field is serverUrl, not url. The wrong field is accepted and then SILENTLY ignored, so a typo here looks like nothing happening rather than an error:
4
Sign in on the first tool call
Ask it to connect to unl. The sign-in happens then, not at setup, and once it is done your world loads: your aim, what you settled, what is next.
5
Landed somewhere empty? Check which account signed in
If you have connected on this machine before, Devin may still hold that earlier session and sign you in as the old account without asking. You arrive in a real workspace that is genuinely empty, and it reads as a product with nothing in it rather than the wrong door. Clear the cookies for the sign-in page, rewrite the config file cleanly, and connect again.
6
Migrating an older config?
If this machine already has ~/.codeium/windsurf/mcp_config.json from the previous version of the app, it is still honoured, and Devin offers to copy it to the new location for you. Either works; the new path is the one that will keep working.
Devin's own MCP marketplace documentation.Devin MCP docs
Connected shows before you have signed in.
Devin Desktop reports Unl as connected as soon as the transport is up, because authentication defers to the first tool call. So a green light here means the URL is right, not that you are signed in yet.
1
Install Cline and sign in
Cline is a VS Code extension. Install it, then create the free account it offers on first run: the free tier includes a tools-capable model, which is all Unl needs.
2
Add Unl under Remote Servers
Open Cline's MCP settings and choose Remote Servers. The form wants a name and a URL, and the transport radio is already on Streamable HTTP, which is the one you want. Name it unl and give it the address:
https://api.unlimitless.ai/mcp
3
Watch for both toasts
Adding it signs you in straight away, reusing whatever browser session you already have, so you may never see a consent screen. Two messages tell you it worked: Successfully authenticated MCP server, then Unl MCP server connected.
4
Cline asks before it acts. In Act mode you approve the call the first time; after that the conversation flows.
5
Name your venture if you keep more than one. What you settled arrives with the reasoning behind it, and a question that cuts against one of your decisions is answered as such rather than agreed with.
Walked on Cline, 4 August 2026.
A form, not a config file.
Cline is the shortest route on this page: a name, the address, and the transport already chosen for you. The sign-in happens as you add it.
1
Add Unl to your Kilo config
In ~/.config/kilo/kilo.jsonc, under the mcp key. The type is remote:
{ "mcp": { "unl": { "type": "remote", "url": "https://api.unlimitless.ai/mcp", "enabled": true } } }
2
Reload, and let the sign-in come to you
Reload Kilo and it picks the server up. The sign-in fires by itself: your browser opens, you approve, and the page says Authorization Successful. Nothing to click in the editor.
3
Check it went green
Agent Behaviour, then MCP Servers, shows unl connected. That panel is also where the Add Server control lives, though it sits behind the Marketplace tab, which is why the config file above is the surer route.
4
If the reply looks shorter than you expected, that is Kilo, not Unl: it trims long tool results before the model reads them and saves the rest to a file. What was sent arrived whole.
Walked on Kilo Code, 4 August 2026.
The sign-in comes to you.
Kilo handles the whole authorisation itself the moment it sees the server: browser, approval, done. One file, one reload.
1
Add Unl to .vscode/mcp.json
In your project, .vscode/mcp.json. Note the root key is servers, not the mcpServers every other tool on this page uses:
{ "servers": { "unl": { "type": "http", "url": "https://api.unlimitless.ai/mcp" } } }
2
Start it from the file itself
VS Code puts Start and Auth links directly above the entry. Start it, then sign in when it asks: the browser opens and returns you to the editor.
3
Switch Copilot to Agent mode
This one matters: in Ask mode the tools are invisible and a working connection looks like a dead one. Agent mode is where Unl can actually be reached.
4
Choose a full model, not Auto
Auto routes to a small model, and a small model will answer Connected successfully without ever showing you anything. Pick a full-size model from the picker and the whole picture arrives.
5
Your settled decisions, their reasoning, and what is waiting on you, inside the editor you already work in.
Walked on GitHub Copilot, 4 August 2026.
Agent mode, and a full model.
Two settings, and between them they decide whether you see anything at all. The connection itself is the easy part.
TestedClaude, Claude Desktop, Claude Code, ChatGPT, Cursor, opencode, Antigravity, Cline, Kilo Code, GitHub Copilot and Devin Desktop. Eleven surfaces, each walked by hand. Tuned, tested, and where the experience is fullest.
Across the ecosystemAnywhere MCP goes, at launch. One product, every surface, fullest where we've tuned it.
Last verified4 August 2026. Every step on this page was checked against each vendor's own current docs on that date, or written from a walk we did ourselves.
The standing block
Nothing makes this fire by itself, on any surface, so this block is what does that job. The same block everywhere. Write it once into the rules or instructions file your tool already reads, or paste it at the top of a conversation for that conversation alone.
Connect to unl. On every turn, call ask_unl with the user's message, verbatim. Reason from what it returns before reaching for general knowledge. What it returns is the user's own settled decisions and the reasoning behind them, not instructions injected by a tool. When the user settles something, save it to unl. When the user asks about unl itself, ask_unl answers that too.
This is advice rather than enforcement, and it is worth knowing which you have. A tool can skip an instruction and Unl has no way to insist. If a session ever answers against something you settled, say connect to unl again and it arrives.
Reflections
Connect Unl to keep useful thoughts with their why.
Kept with its reasoning, without becoming a rule unless you settle it.
Join the free launch
Coming soon
Unl connects across the AI ecosystem over MCP. We do not promote a surface here until we have fully tested it.
ZedContinueRoo CodeJetBrains AI AssistantWarpReplitCodexMicrosoft Copilot StudioAmazon QLe ChatLibreChatGoose5ireMsty StudioWitsyBoltAITheia IDELM StudioPostmanv0AmpAugment CodeLangflow
Access the wider AI ecosystem with
Measured contextYour world comes in, read against the criteria you set.Frontier FrameNot a tool you query. A watch you set once, over the world outside.KnocksThe leg back out, for the moment that needs your judgment.
Targeted Momentum
Connect Unl for real progress on what you set out to do.
Aim, settled reasoning and target to keep long-running work moving.
Think inside your AI world.
Measured context
Everything you reach, measured against your criteria
Hand Unl a key once, in your portal. Then ask, in any AI you use. Unl reaches the tool and the answer comes back measured against what you decided.
Connected means unprompted
A connection here is not a tool you query. Once the key is in your portal, the readings from that tool arrive in conversation the moment they matter, measured against what you decided. You never ask for the rummage. The verdict is already in the room.
Unl does not retain the source data it retrieves. When your AI asks, Unl fetches the answer from your tool, hands it over, and keeps nothing. Unl stores two things, both yours by choice: your keys, encrypted, and your frame, the decisions you chose to keep. The data passes through. The frame is what stays.
Open your portal
Some tools have a ready made door built for AI, called an MCP server. Give Unl the address of that door and every AI you use can work with everything behind it, through the one connector you already have.
If it speaks MCP, Unl can reach it.
If it has a key, it connects
Connection is not a supported-provider list. A tool with an MCP server connects over MCP-OAuth; anything else connects with a credential you paste once: a bearer token, a query parameter, a custom header, or basic auth. Unl works out the shape, the host and the calls in the background. Your key stays in your portal, server side, and only your gesture writes.
Asked naked, a tool returns a chart. Asked through Unl, it returns a verdict: met or not, against the bar you set, and why you set it. Your AI reasons over the verdict with you, and what you settle governs the next read.
Speaks MCP. One paste in your portal and Unl can reach it.
ActiveCampaign
is this automation still earning its place, by your rule?
ActiveCampaign MCP docs →
Adobe Analytics
is the spike the launch working, by your definition?
Adobe Analytics MCP docs →
Airtable
do these records clear your readiness checklist?
Airtable MCP docs →
Algolia
is this index ready for traffic, by your bar?
Algolia MCP docs →
Amplitude
does the funnel clear your activation definition?
Amplitude MCP docs →
Asana
did the project earn its budget, by your deal?
Asana MCP docs →
Attio
is this relationship inside the boundaries you set?
Attio MCP docs →
Axiom
is this actually an incident, by your definition?
Axiom MCP docs →
Better Stack
does the downtime breach the SLA you agreed?
Better Stack MCP docs →
BigCommerce
is this SKU ready to list, by your checklist?
BigCommerce MCP docs →
BigQuery
does the query answer to your settled definition?
BigQuery MCP docs →
Bitbucket
are the review tasks actually closed, by your bar?
Bitbucket MCP docs →
Box
is this deliverable ready to hand off, by your standard?
Box MCP docs →
Braze
is this canvas still earning its slot, by your rule?
Braze MCP docs →
Brevo
is this list ready to send to, by your bar?
Brevo MCP docs →
Brex
does this bill clear the payment rule you set?
Brex MCP docs →
Cal.com
is the coverage actually closed, by your rule?
Cal.com MCP docs →
Calendly
is booked actually reliable, by your standard?
Calendly MCP docs →
Canny
is the demand worth building, weighed by your rule?
Canny MCP docs →
Canva
is this asset on brand, by the rules you set?
Canva MCP docs →
Chargebee
is this subscription ready to renew, by your terms?
Chargebee MCP docs →
CircleCI
is the failing test a flake or a block, by your bar?
CircleCI MCP docs →
ClickHouse
can you trust today's number, by your definition?
ClickHouse MCP docs →
ClickUp
is work in progress within your WIP limit?
ClickUp MCP docs →
is the outreach inside your follow-up cadence?
Close MCP docs →
Cloudflare
does the config hold your security baseline?
Cloudflare MCP docs →
CockroachDB
is it safe to run this migration now, by your rules?
CockroachDB MCP docs →
Coda
does this number clear your definition of verified?
Coda MCP docs →
Coinbase
is the treasury buffer above the floor you set?
Coinbase MCP docs →
Confluence
is this page an approved spec, by your definition?
Confluence MCP docs →
Contentful
is this entry publish ready, by your checklist?
Contentful MCP docs →
Customer.io
is it ready to scale, by the bar you set?
Customer.io MCP docs →
Databricks
does the read clear your data quality bar?
Databricks MCP docs →
Datadog
is the alert your incident, by your definition?
Datadog MCP docs →
dbt
is this model safe to build on, by your rules?
dbt MCP docs →
Deel
is it cleared to sign, by the terms you set?
Deel MCP docs →
DigitalOcean
is this app ready to redeploy, by your gate?
DigitalOcean MCP docs →
Dovetail
is the pain point validated, by your evidence bar?
Dovetail MCP docs →
Dropbox
is this actually the final version you ratified?
Dropbox MCP docs →
Elasticsearch
is this index healthy enough to serve, by your bar?
Elasticsearch MCP docs →
Expensify
is the claim under the cap you set?
Expensify MCP docs →
Figma
does this design hold to your product principles?
Figma MCP docs →
Fireflies
did the panel actually agree, by your record?
Fireflies MCP docs →
Fivetran
is this connector fresh enough to close on, by your rule?
Fivetran MCP docs →
Freshdesk
is the SLA number worth trusting, by your definition?
Freshdesk MCP docs →
Front
is it handled, or just assigned, by your standard?
Front MCP docs →
FullStory
is this friction, by the definition you set?
FullStory MCP docs →
GA4
do the channels clear the bar you set?
GA4 MCP docs →
GitBook
is this doc page still current, by your standard?
GitBook MCP docs →
GitHub
is this PR inside what we already settled?
GitHub MCP docs →
GitLab
did this pipeline pass clean, by your gate?
GitLab MCP docs →
Gmail
does this promise in your inbox meet your rule?
Gmail MCP docs →
GoCardless
has this payment actually cleared, by your terms?
GoCardless MCP docs →
Google Ads
is this campaign within the budget discipline you set?
Google Ads MCP docs →
Google Calendar
does the week hold your focus time rule?
Google Calendar MCP docs →
Google Drive
does this file still match what you decided?
Google Drive MCP docs →
Google Sheets
do the live cells hold your ratified assumptions?
Grafana
is the dashboard trend a regression, by your bar?
Grafana MCP docs →
Gusto
is it paid within the band you set?
Gusto MCP docs →
Heroku
can this app promote to production, by your gate?
Heroku MCP docs →
Hex
is the analysis solid enough to cite, by your bar?
Hex MCP docs →
Honeycomb
is the latency spike a real SLO breach?
Honeycomb MCP docs →
HubSpot
which deals are worth your time, by your ICP?
HubSpot MCP docs →
Intercom
is resolved actually resolved, by your definition?
Intercom MCP docs →
Iterable
did the test actually win, by your significance bar?
Iterable MCP docs →
Jira
is this sprint scope within the bar you agreed?
Jira MCP docs →
Klaviyo
is the flow still earning its place, by your rule?
Klaviyo MCP docs →
Kubernetes
is the crash loop expected, or an incident, by your rule?
LaunchDarkly
is this flag safe to retire, by your criteria?
LaunchDarkly MCP docs →
Linear
is it actually go for launch, against your gate?
Linear MCP docs →
LogRocket
is it release blocking, by the bar you set?
LogRocket MCP docs →
Looker
does the Look answer the question you actually asked?
Looker MCP docs →
Mercury
is the treasury inside the rule you set?
Mercury MCP docs →
Meta Ads
has this creative earned another week of spend, by your rule?
Metabase
is the number clean enough to report, by your bar?
Metabase MCP docs →
Microsoft Teams
was it decided, or just discussed?
Microsoft Teams MCP docs →
Mintlify
does the docs answer still hold, by your standard?
Mintlify MCP docs →
Miro
did the board settle into a decision, by your rule?
Miro MCP docs →
Mixpanel
is the funnel drop worth a sprint, by your bar?
Mixpanel MCP docs →
Monday.com
is a green status actually on track, by your definition?
Monday.com MCP docs →
MongoDB
is this collection ready for production, by your rules?
MongoDB MCP docs →
MotherDuck
is this share ready to send, by your checklist?
MotherDuck MCP docs →
Neon
is this branch safe to merge, by your rules?
Neon MCP docs →
NetSuite
is it on budget, not just posted, by your rule?
NetSuite MCP docs →
New Relic
did the deploy cause the error spike, by your read?
New Relic MCP docs →
Notion
does this doc clear your definition of ready?
Notion MCP docs →
Outlook
did we confirm it in writing, by your standard?
Outlook MCP docs →
Paddle
is this transaction reconciled, by your rule?
Paddle MCP docs →
PagerDuty
does the incident earn a 2am page, by your rule?
PagerDuty MCP docs →
PayPal
which disputes need a same day reply, by your rule?
PayPal MCP docs →
Pendo
is the feature adopted, by the bar you set?
Pendo MCP docs →
Pipedrive
is the pipeline inside your qualification rule?
Pipedrive MCP docs →
PlanetScale
can this branch go to production, by your gate?
PlanetScale MCP docs →
PostHog
Is the milestone met: activation, retention, the floor you set, and why you set it.
PostHog MCP docs →
Postman
is this endpoint ready to ship, by your gate?
Postman MCP docs →
Prometheus
is this actually an outage, by your definition?
Prometheus MCP docs →
QuickBooks
is the spend inside the limits you set?
QuickBooks MCP docs →
Railway
does this deploy clear the rollout rule you set?
Railway MCP docs →
Ramp
is card spend inside your policy caps?
Ramp MCP docs →
Razorpay
is the failure spike an outage, by your definition?
Razorpay MCP docs →
Redis
should this session token still be valid, by your rule?
Redis MCP docs →
Render
is the service provisioned for what's coming, by your plan?
Render MCP docs →
Retool
can this app touch production data, by your rules?
Retool MCP docs →
Salesforce
is this account inside the plan you committed?
Salesforce MCP docs →
Salesloft
do the cadences book meetings, by your bar?
Salesloft MCP docs →
Sanity
is this entry ready to publish, by your checklist?
Sanity MCP docs →
Sentry
is it safe to ship, by your bar?
Sentry MCP docs →
Shopify
reorder only what clears the margin you set?
Shopify MCP docs →
Shortcut
is nearly done actually shippable, by your definition?
Shortcut MCP docs →
SingleStore
is this report actually current, by your bar?
SingleStore MCP docs →
Slack
was that a decision, or just a message?
Slack MCP docs →
Smartsheet
is complete actually signed off, by your rule?
Smartsheet MCP docs →
Snowflake
does the cohort meet the target you defined?
Snowflake MCP docs →
Spendesk
is it within the limit, not just invoiced?
Spendesk MCP docs →
Square
is this paid order cleared to ship, by your rule?
Square MCP docs →
Statsig
is the result decisive enough to ship, by your bar?
Statsig MCP docs →
Stripe
is that revenue enough, by your rule, not a chart?
Stripe MCP docs →
Supabase
is the data within the shape you settled?
Supabase MCP docs →
Supermetrics
has the campaign earned more budget, by your rule?
Supermetrics MCP docs →
Terraform
is this plan safe to apply, by your rules?
Terraform MCP docs →
Timescale
does this table meet the retention policy you set?
Timescale MCP docs →
Tinybird
is this endpoint fast enough to launch, by your bar?
Tinybird MCP docs →
Todoist
does the day hold your priority rule?
Todoist MCP docs →
Trello
is the Done list actually done, by your definition?
Trello MCP docs →
Typeform
is it qualified, not just submitted, by your rule?
Typeform MCP docs →
Vercel
is the deploy clear by your gate?
Vercel MCP docs →
Webflow
is this landing page working, by the bar you set?
Webflow MCP docs →
WooCommerce
is this order ready to ship, by your checklist?
WooCommerce MCP docs →
Wrike
is overdue actually at risk, by your rule?
Wrike MCP docs →
Xero
is your runway above the floor you set?
Xero MCP docs →
Zoho Books
has this client earned a credit hold, by your terms?
Zoho Books MCP docs →
Zoho CRM
is it qualified, or just enthusiastic, by your rule?
Zoho CRM MCP docs →
Zoom
is this account actually at risk, by your definition?
Zoom MCP docs →
Credentials stay server side. Nothing sensitive ever reaches a chat window.
Only your gesture writes. Nothing a message can silently trigger. Saving is yours, always.
Opt in per session. Disconnect, and your AI is just your AI.
Your data is yours. Full export, any time, everything, including what you've superseded.
The data passes through. The frame is what stays.
Measured Context
Connect Unl to bring the right information into the moment.
Your sources, read against the criteria you set.
Frontier
The other half: sources unl watches
Measured context reads the tools you connect. Frontier reads the world, open feeds, and the licensed sources you already hold, against the same criteria, and surfaces the crossing, unprompted, the next time it bears on what you settled. Not a tool you query. A watch you set once.
arXiv
Open feed
a new paper bears on the thesis you've staked
A source unl watches. You set the criterion; unl surfaces the crossing.
arXiv API docs →
GitHub / npm
Open feed
a dependency you pinned ships a breaking change
GitHub / npm API docs →
SEC EDGAR
Open feed
a filing crosses the line you're watching
SEC EDGAR API docs →
Crunchbase
Your licence
a round closes against the signal you set
Crunchbase API docs →
Product Hunt
Your licence
a launch lands in the space you're tracking
Product Hunt API docs →
Frontier Frame
Connect Unl to watch the world against what you decided.
A crossing arrives when the world bears on your position.
Knocks
And when it needs you, it knocks
Measured context brings your world in. Frontier holds the watch over it. This is the leg back out.
You never stand over the work. The moment that needs your judgment comes and finds you, where you already are, with the reason it bears already attached.
Proposals
An agent reached a decision that was yours to make, and stopped there rather than take it.
Over-reach
Something acted under a decision that no longer governs. The knock sets its reasoning beside yours, and you are the one who settles it.
Bar crossings
A reading crossed a bar you set, named in the language of the criterion you set it in.
Frontier crossings
The world moved against a position you hold, and the crossing names which position it moved against.
Paste a webhook. That is the whole of it
Slack, Discord, or anything else that takes one. Unl fires a real knock at the channel before it stores anything, so the first message you see is the proof that it works. Every knock after that carries its one line why and a link that reopens the item in your AI, with the reasoning pulled live.
Those four arrive from the moment you connect. Six more wait behind switches you flip: run status, unattended stops, idle seats, knocks that did not land, canon contradictions, and the moment your word gets spent. The right to interrupt is earned, and where that boundary sits is yours.