Think and decide
Chat
Use the model you want without moving the work.
Conversations live inside the same workspace as projects, notes, agents, and connected tools. Provider and model choice stay visible instead of becoming background routing.
Product
The workspace around the work.
Reforception is not six disconnected AI tools. It is one environment where conversation, planning, execution, knowledge, workers, services, and compute can share the same context and boundaries.
One product
The surface changes. The work does not.
Start in Chat, shape the job in Plan, hand bounded work to an agent in Build, keep what matters in Notes, and return later without rebuilding the context around whichever model happens to be strongest that day.
Product surfaces
Different views for different kinds of work.
Shape the work
Plan
Turn a goal into work you can inspect before execution.
Projects, milestones, dependencies, next actions, and planning assistance give structure to work before an agent touches a repository or machine.
Execute with boundaries
Build
Describe the outcome, choose a worker, and follow the result.
Build keeps repository context, the working conversation, the agent, changes, and deterministic checks together without making source code the primary interface.
Keep the context
Notes
Keep durable knowledge beside the work that produced it.
Markdown notes, folders, links, properties, tags, daily notes, and related knowledge stay available without becoming a separate productivity silo.
See the workforce
Agents
Know who is working, what they can do, and what they have done.
Worker state, assignment, execution policy, recorded runs, and current activity remain visible so automation does not turn into a mystery process.
Bring the system together
Connections + Host Agent
Connect intelligence, services, repositories, and compute.
Connections describe what is available. Host Agent extends bounded execution to machines you control. Capability and authority determine where each connection can actually be used.
The point
Your workspace should outlast your model choice.
Models, providers, and execution environments can change. Reforception is designed to keep the work, decisions, permissions, and evidence in a layer you control.