Use OpenMake by task, not by subsystem

Start in Chat. The sidebar carries the five places work lives — Chat, Agent Tasks, Custom Agents, Artifacts, and Admin — and Settings holds everything about how the workspace behaves.

The composer is the control surface: it shows how many tools are armed, which mode is active, which response style is selected, and which model will answer.

• Choose a model role before an expensive task rather than after it
• Use Agent Tasks to inspect long-running work instead of waiting in the chat thread
• Interface language follows your browser or your saved choice in Settings

The default local route uses qwen3.6-35b-a3b. Behaviour is controlled by orthogonal axes you can see — model, response style, mode, and custom agent — instead of hidden presets.

Model roles let an operator route agent work, research, spawned agents, review, judging, and thinking summaries to suitable models without handing every credential to every user. Chat and image requests keep their request path, while Discussion and Deep Research are intercepted before dispatch for their own pipelines.

• Style — Concise, Default, or Verbose
• Mode — Discussion, Thinking, Deep Research, Web, Agent, Image, Artifact, or Structured
• Thinking mode renders reasoning as a timeline with a one-line headline, and both are restored when you reopen the conversation

An agent task pursues a goal across multiple tool-calling turns. When the task sandbox is enabled, shell, Python, browser, file, and planning tools run in a Docker workspace; the Desktop local bridge is a separately enabled, confirmation-gated executor.

It reports honestly when it fails. An unfinished run is marked incomplete and judged rather than quietly reported as done, and deliverables can include .xlsx and PDF files with Korean and CJK fonts embedded.

• 18 built-in industry agents covering 100 specialists
• Custom agents are project-scoped personas, each optionally pinned to its own model
• Skills are reusable manifests with tool bindings — uploaded, imported from Git, or generated by the model
• Skill auto-selection reaches chat and agent tasks only when SKILL_AUTO_SELECT_ENABLED=true
• Tasks can be saved as templates or put on a recurring schedule

Deep Research fans out across web search, fetches the sources, verifies the claims against each other, and only then writes a cited synthesis. Since 1.12.0 it also pulls in configured skill knowledge and MCP tool evidence, so the report reflects your own connected sources rather than the open web alone.

NotebookLM grounding is the other half of the story. Pin one of your own notebooks from the composer and the answer is constrained by that material; the pin is scoped to a single conversation and the grounding prefix never pollutes stored messages or sidebar titles.

• The pipeline is visible: decompose the question, gather sources, cross-check, synthesize
• Reports keep numbered citations back to the sources that were actually fetched
• The NotebookLM connector uses your own Google session cookie, encrypted at rest and injected only when the server spawns
• Set the research scope before a long run — the cost is in the fan-out, not the writing

OpenMake ships 22 built-in MCP tools — web search, fact-check, scraping and crawling, image analysis, agent-task control, and git ingest among them — and connects external MCP servers from the catalog in Settings → Connectors.

Artifacts turn a result into something you can inspect. They render in a sandboxed iframe, can execute Python or JavaScript in Docker, and publish through a separate-origin viewer with a strict content security policy.

• Docker-sandboxed stdio servers run with --cap-drop ALL, a non-root user, memory limits, a network policy, and realpath-guarded mounts
• Remote MCP servers use SSE or Streamable HTTP; those network transports are not put into the stdio Docker sandbox
• A catalog-level tool allowlist keeps chat auto-exposure focused, while REST execution and the explicit tool picker retain full access
• The OpenAI-compatible API returns artifacts as a message.artifacts extension

Cross-conversation memory injects explicit long-term notes into the system prompt, and a per-session toggle lets you exclude them when a conversation should start clean. Custom instructions are always on by comparison.

Language, memory, provider keys, and privacy all live in Settings under the account that owns the workspace, so a user can change their own routing without touching anyone else's.

• System prompt assembly order: memory, then custom instructions, then style
• Memory is explicit — an entry exists because it was saved, not because a heuristic guessed
• Guests are limited to the default local model; external providers require signing in

OpenMake exposes an OpenAI-compatible endpoint at /api/v1/chat/completions, authenticated with API keys that carry their own role and rate policy. The optional Discord gateway bot is built on exactly that surface.

Usage is recorded per account and per model. External BYOK provider usage is explicitly exempt from the local token quota in 1.13.0, and the ChatGPT OAuth role path records usage so an operator can tell which route a request actually took.

• Issue API keys with a role and a rate policy rather than sharing a personal session
• publish_artifacts: true lets API clients that cannot publish receive share links
• Watch the per-model breakdown to confirm traffic is staying where you expect

The admin console is where an operator sees the system rather than the conversation: dashboards, analytics, metrics, MCP monitoring, agent learning, the audit log, alerts, the MCP catalog, and global model roles.

Privileged actions are audited, and the audit trail feeds the alert path — a context overflow, for example, produces both an audit record and a webhook alert rather than a silent failure.

• Set org-wide role defaults and register server-shared external keys with token budgets
• Review audit records for privileged actions and rate-limited routes
• Monitor migrations, model routes, connector health, and resource usage from one place

The shortcuts below are the ones the web application actually binds. Each is contextual — it works inside the surface it belongs to.

• Enter — send the message from the composer
• Shift + Enter — insert a new line without sending
• Up and Down arrows — move through composer suggestions
• Escape — close the composer mode sheet, or any open detail panel in Agent Tasks, Custom Agents, or Skill Library
• Ctrl/Cmd + Enter — send a steering message to a running agent task