Continuity
Knowledge and decisions should survive a change of session or tool.
About ChaseOS
AI operating system
Keep the context. Keep control of the work.
Keeps project context, agent work and approvals in one place.
01 / Purpose
Why ChaseOS exists
A project is more than the prompt currently on screen. It includes decisions, files, constraints, unfinished work and the reasons behind each change. ChaseOS is built around keeping that context usable when people and agents return to the project.
ChaseOS is a human–AI operating system and governance layer. It brings knowledge, agent activity and approvals into a shared operating picture. Rather than treating every tool call as permission to act, it separates the work an agent can prepare from the actions a person must authorise.
02 / In practice
From the problem to the next step
- 01
Bring project context and constraints into the workspace.
- 02
Let scoped agents prepare work against that context.
- 03
Review the evidence, decisions and changes before authorising consequential actions.
Who it is for
Builders and small teams managing ongoing projects across AI tools.
What it brings together
- Project knowledge and reusable context
- Agent work with review and approval boundaries
- A connected platform, runtime and agent family
03 / Design principles
What guides the product
Bounded execution
Tools and agents operate within explicit permission and approval boundaries.
Visible evidence
A proposed change, a local test and a published result are different states.
04 / The builder
Built by John Idowu · ChaseInTech
ChaseInTech is John’s public builder identity: a place to follow the projects, product decisions and development work behind these brands. Each brand has its own purpose; the shared connection is the person building it.
The brand profile explains the business purpose. The linked project case studies go deeper into the software and implementation.
Meet the founder →05 / Current status
Know what you are looking at
The project catalogue records ChaseOS as live. Individual components have their own release and availability states; the official site and linked case studies carry the detail. This profile does not imply unrestricted execution or that every planned capability is available.
Profile reviewed 24 September 2026. Refer to the official product pages for current availability and terms.
06 / Questions
A little more context
Is ChaseOS the same as ChaseInTech?
No. ChaseInTech is John Idowu’s public builder identity. ChaseOS is a product family with its own site and technical projects.
How do Core and Chaser Agent fit?
Core supplies foundational contracts and runtime work; Chaser Agent is the agent-facing part of the family. Their case studies explain the implementation and boundaries separately.
Does an agent get automatic permission to publish or spend?
No. Keeping consequential actions behind explicit authority is part of the product’s governance model.