ChaseOS Studio

Local-first AI workspace where agents run under approval.

1 follower

Local-first AI workspace where agents run under approval.

1 follower

ChaseOS Studio is a local-first AI workspace for Windows. Project context compounds in a private typed graph instead of resetting every session. Agents run on your machine inside declared runtime profiles and stop at approval gates before consequential actions. Every run records what it read, produced, and was refused. Community is a free tier; ChaseOS Core is MIT, while Studio is commercial.

Free Options

Launch tags:Productivity•Developer Tools•Artificial Intelligence

Launch Team

Maker

📌

Windows-only first: ChaseOS Studio currently supports Windows 10 (1809+) and Windows 11, x64. It is not a hosted agent service. I built ChaseOS because project context kept resetting between AI sessions, while tools that could act often asked for too much trust. Studio keeps sources, decisions, approvals, runs, and outputs in a private typed graph on your machine. Agents work from scoped context inside declared runtime profiles, and sending, publishing, or spending stops at an approval gate. The Community tier is the complete local product, not a trial. ChaseOS Core is MIT; Studio itself is commercial. The Windows installer is signed and has a published SHA-256. I would especially value feedback on whether the approval and audit model makes unattended local agents easier to trust.

Report

2mo ago

Forum Threads

p/chaseos-studio

•

1mo ago

What breaks when every AI agent starts with different context?

I kept seeing the same failure mode: the chat, coding agent and automation were all capable, but each started from a different version of the project.

That is why ChaseOS Studio V1.1.0 treats shared context as infrastructure. Its Graph connects projects, sources, workflows and agent activity inside one local-first operating layer, so each runtime can begin from the same inspectable project truth.

This 15-second film uses the real V1.1.0 release-lineage Graph view not a fabricated mock-up or a customer-performance claim:

https://x.com/chaseos_ai/status/...

p/chaseos-studio

•

2mo ago

Should an AI app update itself, or ask first?

ChaseOS Studio V1.0.6 now includes a signed in-app update handoff, but it does not silently replace the running application.

The operator sees the available version, chooses to update, and the updater verifies the published release before handing off to the signed installer. The same release also makes Cloud-key failures clearer, preserves the existing Hermes/OpenClaw configuration before changes, and keeps recoverable setup controls available.

For people building desktop AI tools: where do you draw the line between convenience and operator control? Would you allow silent background updates, or require an explicit approval when the application controls agent runtimes and project context?

Explore ChaseOS Studio V1.0.6: https://chaseos.ai/download

p/chaseos-studio

•

2mo ago

When does an installed AI agent become an operable system?

I have been working on this boundary in ChaseOS Studio V1.0.5. A successful install is only the start. Before I trust an agent with real work, I want to see its runtime, target host, configuration, linked context, approval requirements, and the evidence it writes back.

The new ChaseOS first-run path brings Hermes/OpenClaw controls, Windows/Ubuntu launch defaults, reversible Cloud configuration, Chat, the linked Graph, and explicit approval surfaces into one local workspace.

For people building agent products: where do you consider onboarding finished after installation, after the first successful task, or only after the user can inspect and govern the system?

Explore the current ChaseOS workspace: https://chaseos.ai/?utm_source=p...

View all

Forum Threads

p/chaseos-studio

•

1mo ago

What breaks when every AI agent starts with different context?

I kept seeing the same failure mode: the chat, coding agent and automation were all capable, but each started from a different version of the project.

This 15-second film uses the real V1.1.0 release-lineage Graph view not a fabricated mock-up or a customer-performance claim:

https://x.com/chaseos_ai/status/...

p/chaseos-studio

•

2mo ago

Should an AI app update itself, or ask first?

ChaseOS Studio V1.0.6 now includes a signed in-app update handoff, but it does not silently replace the running application.

Explore ChaseOS Studio V1.0.6: https://chaseos.ai/download

p/chaseos-studio

•

2mo ago

When does an installed AI agent become an operable system?

For people building agent products: where do you consider onboarding finished after installation, after the first successful task, or only after the user can inspect and govern the system?

Explore the current ChaseOS workspace: https://chaseos.ai/?utm_source=p...

View all