Skip to content
PersonOS
PersonOS Context

Personal context infrastructure for AI agents面向所有 Agent 的个人 Context 基础设施

Every AI.Grounded in you.让每一个 AI,都从你出发。

PersonOS brings your files, experience, decisions and goals into a Context Bank you own. The AI you choose uses it with your permission, and what you create together comes back to you.PersonOS 把散落在应用与设备里的资料、经历、判断与目标,积累成你持有的 Context Bank。你选择的 AI 按授权使用,新的成果继续回到这里。

Research notes · Yours to own研究笔记 · 由你持有№ 0412

The assumptions behind the growth.增长背后的那些假设。

  1. 1Original原件fy26-q3-report.pdf · p.14
  2. 2Annotations批注3 annotations · 2 revisions3 条批注 · 2 次修订
  3. 3Your judgment你的判断“Watch the durability of subscription revenue. If collections slow, revisit the quality of growth.”“关注订阅收入的持续性。如果回款放缓,就重新审视增长的质量。”
  4. 4Saved back回存Updated thesis review更新后的论点复盘By your research agent · allowed for 1 hr由研究 Agent 写回 · 已允许 1 小时

AI companies can earn your choice.They don’t get to own your history.AI 厂商可以争取你的选择,无权锁住你的长期积累。

Your projects, research, plans and private details belong with you, across AI, apps and devices.项目要求、研究轨迹、生活安排与敏感资料,应当由你长期持有,随你跨越不同的 AI、应用与设备。

We oppose building an AI monopoly out of personal context. You choose the AI that fits each goal, and you decide how your own history is used. That principle binds PersonOS too.我们反对以个人 Context 建立智能垄断。你有权选择适合不同目标的 AI,也有权决定自己的积累如何被使用。这条原则,同样约束 PersonOS。

01 Context BankContext Bank

The time you’ve put inshould stay.你投入过的时间,应该留下来。

You saved a piece of research, and the conclusion, the evidence and the reason you revised it later. Context Bank keeps all of it, so the next AI that uses it can see how far you’ve already come.你保存了一份研究,也留下了结论、依据与后来修正它的原因。Context Bank 把这些一起留下,让下一次使用它的 AI 看见你已经走到哪里。

IDs, payment details, sizes and preferences. Project files, meeting notes, photos, audio and video. All of it can live in one Bank. Originals, sources and timestamps are stored with the content, and corrections keep feeding later tasks.证件、付款资料、尺寸与偏好,项目文件、会议记录、照片和音视频,都可以进入同一个 Bank。原件、来源与时间随内容保存,修正后的信息继续供后续任务使用。

One research record, kept whole.一份研究,完整留存。

The first judgment, the reason it changed, the new original and what an agent saved back stay in one record, in order. The next AI picks up from here.最初的判断、修正的原因、新的原件,以及 Agent 回存的成果,按时间留在同一条记录里。下一次使用它的 AI,从这里接着往下走。

  1. Initial thesis最初的假设
    Subscription growth looks durable.订阅增长看起来是可持续的。
  2. Revised, with the reason修正,并写下原因
    Growth looks durable.增长可持续。The weight moves to renewal rate.判断重心移到续费率。Because Q2 collections slowed.因为 Q2 回款放缓。
  3. New evidence, with the original新的依据,连同原件
    fy26-q3-report.pdfPage 14, imported as it was.第 14 页,按原样导入。
  4. Saved back by an agent you allowed由你允许的 Agent 回存
    Updated thesis review更新后的论点复盘Linked to this record, with source and time.带着来源与时间,关联到这条记录。

02 Across AI跨 AI

It isn’t the agent that knows you.It’s PersonOS.懂你的不是 Agent,是 PersonOS。

Pick the AI that’s best at research. Swap in a different coding agent any time. PersonOS keeps maintaining your context, so every new arrival starts from the experience, judgment and goals you already have.你可以选择更擅长研究的 AI,也可以随时换一个 Coding Agent。PersonOS 持续维护关于你的 Context,让新加入的 AI 从你已有的经历、判断与目标开始。

Agents take context by permission and save new decisions and results back. Different AIs, one growing body of work.Agent 按授权取用 Context,也把新的决定与成果保存回来。不同 AI 的工作,继续落在同一份积累上。

Plugs into the AI you already use.接入你已经在用的 AI。

Through MCP, Skills, plugins and connectors, PersonOS shows up inside the AI you already work with. What you already have comes in, organized; what you make next keeps writing back.通过 MCP、Skill、Plugin 与 Connector,PersonOS 出现在你常用的 AI 里。已有的资料整理进来,新的成果持续写回。

What you already have已有的积累

  • Files & PDFs文件与 PDFOriginals kept, page by page原件与页码一起保存
  • Notes & documents笔记与文档Your annotations and revisions连同你的批注与修订
  • Watched folders持续更新的文件夹New files come in on their own新文件自动进入
  • Photos & recordings照片与录音With time and source带着时间与来源

Organized into context with source and time整理成带来源与时间的 Context

Your Context Bank你的 Context Bank Always growing · yours to own持续生长 · 由你持有

The AI you use你使用的 AI

  • MCPClaude Code and other MCP-capable agentsClaude Code 与其他支持 MCP 的 Agent
  • SkillTells an agent when to ask, and for what让 Agent 知道何时取用、取用什么
  • PluginInstalls into the AI apps you use装进你常用的 AI 应用
  • ConnectorLinks chat assistants and workflows连接聊天助手与工作流

New decisions and results keep writing back新的决定与成果,持续写回 Bank

Switch agents. The reasons stay.换一个 Agent,理由还在。

That check that looks safe to delete exists because a retry once caused duplicate writes. Three agents, joining at different times, all work from the same history.那段看似可以删掉的校验,背后是一次重复写入的事故。三个 Agent 在不同时间加入,依据的是同一份历史。

From your Bank · one history, kept by PersonOS来自你的 Bank · 同一份历史,由 PersonOS 维护

  1. 1Retry caused duplicate writes重试曾导致重复写入
  2. 2Keep the idempotency check on /charge保留 /charge 的幂等校验
  3. 3Small PRs, tests first小步提交,先写测试
  4. 4Check sample size in Table 2核对表 2 的样本量

Coding agentCoding Agent

“The check looks redundant, but your Bank says a retry once caused duplicate writes. I’m keeping it.”“这段校验看起来多余,但你的 Bank 记着:重试曾导致重复写入。我会保留它。”

Based on依据 12

A new coding agent, joined today新的 Coding Agent · 今天加入

“I can see why the check stays. I’ll simplify around it, in a small PR with the test first.”“我明白这段校验为什么留着。我会绕开它来简化,用一个小 PR,先写测试。”

Based on依据 23

Research agent研究 Agent

“Picking up your note from your phone: the sample is 41, which is small. I’ve flagged it for the methods section.”“接着你昨天在手机上的批注:样本量只有 41,偏小。我已把它标进方法部分。”

Based on依据 4

03 Permissions & audit授权与审计

To use your context,accept your rules.使用你的 Context,就必须接受你的规则。

Give each agent only the access its task needs: the right records, the right actions, for a time you choose.只给每个 Agent 当前任务需要的权限:哪些资料、哪些操作、持续多久,都由你决定。

Read, append, update and delete are granted separately. Bound it to a single task, the current session, or a clear stretch of time. Revoke whenever you like; later requests ask again.读取、追加、更新与删除分别授权。一次任务、当前会话,或一段明确的时间,都可以设定边界。你可以随时撤销,后续请求重新取得同意。

What one grant looks like.一次授权,长这样。

A research agent can read selected interviews and append analysis, but it can’t rewrite the originals. Your private calendar wasn’t requested, so it stays sealed.研究 Agent 可以读取选定的访谈、追加分析,但不能改写原始记录。私人日程没有被请求,也就不会开放。

A research agent may…研究 Agent 可以……Read读取Append追加Update更新Delete删除
Selected interviews选定的访谈12 records12 条记录Allowed允许Allowed允许Not allowed不允许Not allowed不允许
Original records原始记录Never rewritten by agentsAgent 无法改写Allowed允许Not allowed不允许Not allowed不允许Not allowed不允许
Private calendar私人日程Not requested, not shared未请求,也未共享Sealed已封存
For how long持续多久Then it asks again.到期后重新询问。Once本次15 min15 分钟1 hour1 小时This session当前会话

Island · on your desktopIsland · 桌面上的授权

See who’s asking, why, and for what.看清谁在请求、为什么、要什么。

In Island on your desktop, in the browser or in the PersonOS app, review the request, then allow, partly allow or deny. Every request, and what was actually delivered, leaves a record you can review.在桌面 Island、浏览器或 PersonOS App 中,看清请求者、用途和范围,再决定允许、部分允许或拒绝。每次请求及实际交付的内容,都留下可回看的记录。

✻ Claude Code
❯

Draft my Monday weekly update in my preferred tone. Lead with concrete progress from this week, then cover current blockers and any pending follow-ups. Use only context PersonOS explicitly releases for this request; if a field is withheld, leave it out rather than infer it.

Thought for 7s (ctrl+o to expand)

I should build this from task-scoped context, not from the full person model.

I’ll request preferred tone, recent progress, current blockers, and pending follow-ups for this update.

If PersonOS withholds a field, I’ll omit that section rather than fill the gap.

Calling personos…(ctrl+o to expand)

⎿  personos_read(purpose: "weekly work update", fields: 4, duration: "15m")

Reaching for context…(0s · ↓ 84 tokens · esc to interrupt)

Called personos (ctrl+o to expand)

⎿ Context delivery CP-8F31 · 2 released · 2 withheld · ctrl+o to expand

releasedvoice.tone, work.recent_progress

withheldwork.blockers, relationships.pending_followups

Here’s a draft:

This week, I completed a working end-to-end PersonOS demo. Claude Code now declares a concrete purpose and requests only the personal context needed for that task.I connected that request to an owner-controlled approval flow, compiled the released fields into a scoped Context delivery, and used only that context without exposing the rest of the person model.The same run now writes a signed audit receipt, so the request, authorization, released and withheld fields, output, and evidence trail can be reviewed together.

Current blockers and pending follow-ups weren’t released, so this draft only covers verified progress.
❯

personos-demomainPersonOS MCP · connected

PersonOSPrototype · simulated data and signatures
Broker connected

Access

Who can read which part of your context.

2active grants 0reading now 1approved, never used
Apps and callersStanding and one-time grants live together
Current projectThursday availabilityPreferred writing tone

Revocation blocks future reads. Context already delivered to an agent cannot be recalled.

Duration
  1. AskClaude Code declares its purpose
  2. ChooseYou narrow the requested fields
  3. UseOnly approved context shapes the answer

Access and receipts

Access settings and the latest request record.

04 The right context恰好够用的 Context

Your world is big.This time, the AI needs this part.你的世界很大。这一次,AI 需要懂的是这一部分。

Reading a new earnings report, AI can check it against the judgment you left last time: which assumptions hold, and which deserve another look.读一份新财报时,AI 可以对照你上次留下的判断,指出哪些假设得到支持,哪些值得重新检查。

PersonOS organizes around what you’re doing. The AI asks for the relevant material, judgment and preferences: original files and excerpts when facts need checking, your decisions and limits when it needs to understand a choice.PersonOS 围绕正在做的事,让 AI 请求相关资料、判断与偏好。需要核对事实,就提供原始文件与片段;需要理解选择,就带上你的决定与限制。

Let AI understand this task,
without opening your whole life.
让 AI 理解这件事,
不必向它开放你的全部生活。

Three tasks, three different sets of background. What a task doesn’t need stays in your Bank.三件事,三份不同的相关背景。这件事用不上的部分,留在你的 Bank 里。

Investment research投资研究

A new earnings report arrives.一份新的财报送到手里。

  • Your thesis · Jun 4你的论点 · 6 月 4 日
  • Your annotations · 3你的批注 · 3 条
  • Original excerpt · p.14财报原文 · 第 14 页
  • Renewal and collection history历史续费与回款记录
  • Family travel plans家庭出行计划
  • Medical records体检记录

Collections slowed for two quarters. Revisit the quality-of-growth assumption.回款已连续两个季度放缓,值得重看「增长质量」这条判断。

PhD application博士申请

A research statement is due in December.十二月前要交一份研究陈述。

  • Your CV · latest你的简历 · 最新版
  • Annotations on 3 papers3 篇论文的批注
  • Advisor shortlist notes导师候选名单笔记
  • Personal calendar个人日程
  • Payment details付款资料

The statement connects your retrieval project with two papers you annotated, and relates them to the prospective advisor’s research.以你的检索项目为主线,结合两篇已批注论文,说明与意向导师研究方向的联系。

Training plan训练安排

Next week’s runs, before a race.比赛前一周,怎么跑。

  • Last 4 weeks of runs过去 4 周的跑步记录
  • Right knee: avoid downhill右膝:避免下坡
  • Race date · Nov 16比赛日期 · 11 月 16 日
  • Work calendar工作日程
  • Private messages私人消息

The draft considers recent training and the race date, and keeps your “avoid downhill” constraint.计划结合近期训练记录与比赛日期,并保留你提出的「避免下坡」要求。

05 Security & openness安全与开放

Encrypted by design.
The keys are yours.
加密保管,
由你持钥。

We’re building Context’s security around keys you control, verifiable access and confidential computing—across storage, delivery and processing.我们正在构建覆盖保存、交付与计算的安全架构:密钥由你掌握,每次访问可核验,云端处理有隔离。

AES-256-GCMIndependent keys · authenticated encryption独立密钥 · 认证加密

A key for each record. Protected on your device.逐份加密,设备端持钥。

Layered key wrapping and integrity checks. Keychain stores keys; Secure Enclave protects device private-key operations.分层封装密钥,读取时核验完整性。Keychain 保管密钥,Secure Enclave 保护设备私钥操作。

End-to-end sync. Only ciphertext in the cloud.端到端同步,云端只存密文。

New devices are verified by you, then receive an HPKE-encrypted key package. The sync service has no decryption keys.新设备经你核验,再接收 HPKE 加密密钥封套。同步服务不持有解密密钥。

Recovery and rotation, under your control.恢复与轮换,由你掌握。

Keep your recovery secret offline. Remove a device and rotate keys to protect future content.离线保管恢复秘密。移除设备后轮换密钥,保护后续内容。

Precisely permitted.
Cryptographically recorded.
权限精确到这次任务,
交付留下签名凭证。

Each agent has its own identity. Permissions are enforced outside the model; every delivery binds the recipient, approved scope and record versions.每个 Agent 都有独立身份。模型之外的权限机制,把每次交付绑定到接收方、授权范围与资料版本。

Verify each request每次请求,重新核验

Agent identity, request and record version are checked together. Replay attempts are rejected.核验 Agent 身份、请求与资料版本,拒绝重放。

Deliver only what is allowed只交付获准的内容

HTTPS protects delivery. Scope and duration are enforced; expiry or revocation blocks future access.通过 HTTPS 交付,限定内容、操作与时限;到期或撤销后停止访问。

Verify the signed record凭证可以独立核验

Device signatures bind the manifest and content digest. Saved checkpoints make the event chain verifiable.设备签名绑定清单与内容摘要,独立检查点用于核验事件链。

Cloud computing.
Verify before you share.
云端计算,
先验证,再交付。

For Context’s confidential cloud processing, your device verifies the approved code and isolated environment, then encrypts approved content directly to it.使用 Context 的机密云端处理时,设备先核验获准代码与隔离环境,再将本次获准内容加密直达该环境。

Confidential computing机密计算Hardware-isolated compute & memory硬件隔离的计算与内存
  1. 01

    Verifiable releases可验证发布

    Public source, reproducible builds and transparency logs tie each release to a verifiable code measurement.公开源码、可复现构建与透明日志,让发布版本对应到可核验的代码度量。

  2. 02

    Remote attestation远程证明

    Your device verifies the attestation signature and its binding to approved code, a fresh challenge and the channel’s public key.设备核验证明签名,以及获准代码、本次挑战与通道公钥在证明中的绑定。

  3. 03

    An encrypted channel into the enclave加密直达隔离计算区

    Only approved content enters the attested environment. The host cannot directly read its isolated memory.只处理本次获准内容,云主机无法直接读取隔离区内存。

Open by design开放,是设计出来的

We don’t keep youby locking in your data.我们不靠锁住你的数据,留住你。

Revisit last year’s research your own way. Run your notes through a script you wrote, fix a judgment in the editor you like, then let the AI you pick carry on. You don’t have to wait for PersonOS to build every use you can think of.用自己的方法,重新审视过去一年的研究。把资料交给自己写的脚本分析,在熟悉的编辑器里修正判断,再让你选择的 AI 继续。你不必等 PersonOS 为每一种用法开发功能。

Edit, correct, reorganize or delete any context at any time. Content, originals, sources, timestamps and relationships all export in open formats, readable and usable without PersonOS.你的 Context 随时可以编辑、纠正、重新组织或删除。资料、原件、来源、时间与关联关系,都能以开放格式导出,在 PersonOS 之外继续使用。

The export is the research itself导出的,就是这份研究本身

thesis.md
# The assumptions behind the growth
source:  fy26-q3-report.pdf, p.14
revised: 2026-06-04
reason:  Q2 collections slowed

Watch the durability of subscription
revenue. If collections slow, revisit
the quality of growth.

> Your note: check renewal rate against
> collections, not bookings.
context.json
{
  "id": "ctx_research_0412",
  "source": {
    "file": "originals/fy26-q3-report.pdf",
    "page": 14
  },
  "revisions": [
    { "at": "2026-03-12" },
    { "at": "2026-06-04",
      "reason": "Q2 collections slowed" }
  ],
  "links": ["ctx_review_0188"]
}

Your editor你的编辑器Your script你的脚本The AI you choose你选择的 AI

06 Beyond the screen超越屏幕

Your context shouldn’tend at the screen.你的 Context,不应该止于屏幕。

A line in a meeting that changed the direction. A demo at a trade show worth following up. Either could become the background your next task needs.会议里一句改变方向的话,展会上一个值得继续研究的演示,都可能成为下一次任务的重要背景。

PersonOS is built for phones, recorders, watches, smart glasses and more, turning the sound, images and notes you choose to keep into context you can keep using.PersonOS 面向手机、录音设备、手表、智能眼镜与更多采集入口,把你选择留下的声音、画面和记录,整理成可继续使用的 Context。

  • Phone手机
  • Recorder录音设备
  • Watch手表
  • Smart glasses智能眼镜
  • And more更多

One line from the room, linked to the next proposal.一句现场的原话,连到下一份方案。

A requirement in your next proposal stays connected to what was said in the room. When you keep a moment, you may not know which project it will help later. So the source stays, corrections are allowed, and it can take part in problems that haven’t shown up yet.下一份方案里出现的要求,依然连接着现场的原话。当时留下这段经历,你未必知道它以后会帮助哪个项目;保留来源、允许修正,让它能够参与尚未出现的问题。

“…let’s make export open by default, no exceptions.”“……导出这件事,默认就该是开放的,没有例外。”
Team sync · Oct 9 · 12:41 · captured on a Watch团队同步会 · 10 月 9 日 · 12:41 · 由手表采集

Proposal v3 · Requirement 4.2方案 v3 · 需求 4.2

Export must be open by default.导出必须默认开放。

From the meeting, 12:41来自会议 · 12:41

We’re building everyone’sown AI ecosystem.我们正在构建,每个人自己的 AI 生态。

One day you’ll have Personal Agents with different strengths, researching, creating, arranging your life, and pushing goals that span years.未来,你可以拥有不同能力的 Personal Agent,一起研究、创造、安排生活,推进跨越很长时间的目标。

They start from the experience, judgment and choices you keep accumulating, take part within what you allow, and hand new results back to you.它们从你持续积累的经历、判断与选择出发,在你允许的范围内参与,把新的成果交还给你。

Intelligence can come from anywhere.Context stays yours.智能可以来自任何地方。Context,始终属于你。

Research研究Why the thesis changed.论点为什么改了。
Identity身份IDs, sizes, preferences.证件、尺寸、偏好。
Code代码Why the check stays.这段校验为什么留着。
Meetings会议The line that changed direction.那句改变方向的话。
AgentsAgentMany agents. One history.许多 Agent,同一份历史。
Open开放Export it. Edit it. Take it.导出它,改写它,带走它。
Scenes场景This part, for this task.这件事,只用这一部分。
Access授权Your rules. Every time.你的规则,每一次。
Goals目标A plan that spans years.一个跨越数年的计划。
Delivery交付Only what you allowed.只交出你允许的部分。