Recommended update introducing scoped AI agents, reviewed automations, and chat
app integrations. Includes dependency security updates and all 0.9.6 fixes.
-
Agent characters — choose from 16 original flat bots with distinct silhouettes,
gazes and expressions. Give default specialists a stable individual look across
the switcher, automation setup and tool results, and preserve the chosen character
when saving a new agent. Keep the chat header to the agent's name and role. -
Monitoring AI shortcuts — prepare scoped repairs from the shorter Fix with AI
action on app issues and a read-only workspace health report from the Monitoring
header. Keep status labels in a dedicated column and move actions below details
when the list is narrow. -
Assistant action handoffs — offer a compact inline review when enabling saved
automations, approve the exact revisions together, and continue the task in the
same chat. Recheck existing permissions and reject stale batches atomically.
Clarify that authorized MCP actions should be executed and verified, not handed
back as manual instructions. Simplify the chat header and float the composer
above the transcript without reducing its scrolling area. -
AI Agents workspace — switch between the general assistant, specialists and
automations in a collapsible 340px right column. Resume each agent's last valid chat,
browse conversations from the header’s history drawer, and inspect automation runs with
their existing investigation chats. Use a right drawer on mobile and keep agent
configuration in the shared drawer. Simplify the conversation header and preserve
scoped navigation, fresh requests and paused flow controls. -
Automation editing — show Trigger, Investigate, Respond and Notify as compact
connected settings rows, with fields expanding in place and full-width hover/focus.
Keep saved summaries visible while fields load, and use matching skeletons across
the agents workspace, conversations and editors. Edit a selected automation inline
in AI Agents using the same forms, permissions and save checks as the dedicated
editor. Use one app/status line and Save/Cancel toolbar, and return to run history
after editing. Reuse the row summary in expanded chat previews. Chat-created flows
stay paused until reviewed. -
Investigate with AI — open a prepared assistant request from failed deployment
headers, failed app setup pages and active app issues. Keep the original app and
deployment context through setup, use existing permissions, and scope the handoff
to its originating account and workspace. Logs and errors stay out of shortcut URLs. -
Scoped assistant agents — create specialists with saved instructions, an AI
connection and named resource permissions. Assign tasks or select a specialist
in an automation. Each task uses one inspectable conversation, including live
follow-ups, through the existing Assistant and MCP execution path. Add agent and
automation tools to the normal API, inline task links, and paused flow drafts
for user review. Bound each task to its original authority; recheck scope changes,
deduplicate requests, and revoke temporary execution tokens on completion or agent edits.
Manage agents in an animated drawer, expand creation and editing across the screen,
choose a flat character avatar, and open scoped chats in the main assistant workspace.
The chat header identifies the active assistant or specialist and the current conversation.
Keep connection management in the overflow menu and Assistant settings. -
AI Agents introduction — show what agents can do through selectable deployment,
investigation and automation examples. Keep one enable action, a compact host choice
and original Codex/Claude Code marks. Put setup first on mobile and show a
permissions-shaped skeleton while access setup loads. -
Native harness identity — show Codex and Claude Code with their native marks
across the composer, connections, history and agent settings. Preserve the
harness’s original authentication prompts, including ChatGPT sign-in for Codex. -
Assistant live chat and composer — smooth incoming text and scrolling, expand
live thinking, and show animated tool activity with reduced-motion support. Attach,
paste or drop images with removable previews, and switch models between replies
in the same conversation. Images use Mindwire's conversation-bound uploads on the
selected agent host; size/type validation and existing workspace permissions apply.
Show immediate send progress and keep activity visible between replies and tool steps;
use a solid stop icon.
Clear the composer on send and reset conversation input to a medium-height, two-line field;
restore failed submissions with their original attachments for retry. -
Assistant Markdown — render streaming replies with Streamdown, syntax-highlighted
code, readable tables and nested lists across light, dim and dark themes. Keep copy
controls tied to completed text and retain safe links without loading model-supplied
images or executing raw HTML. -
Assistant access and tool results — stop offering instance-only diagnostics
to workspace-scoped MCP connections. Keep the shared instance authorization gate
for direct calls, and refresh completed chats after permission edits. Retire stale
access requests and carry the last request into a new chat as an unsent draft.
Add expandable tool activity, per-call request/result inspection, and inline app,
server, deployment, service and repository cards using the existing view/import flows. -
Assistant in chat apps — talk to your own Claude Code or Codex agent from Slack,
Discord, Telegram and Teams through the existing Assistant runtime and MCP grant.
Workspace allowance and personal opt-in start off. Conversations are isolated by
sender and chat; history, resume, new and stop reuse native conversations. Continue
chat-origin conversations in the dashboard with the same approved access. Choose
dedicated Assistant, deployment-command or combined bots.
Durable replies read the exact native turn, including after dashboard continuation,
and survive delivery retries without replaying turns. Access
changes stop further execution. Add settings and per-provider setup guidance;
preserve private command replies and assistant threads in the shared chat transport. -
Assistant automations — add Assistant settings and an opt-in flow editor for
failed deployments and confirmed service incidents. Investigate and notify,
request approval, or explicitly choose app recovery and repository permissions.
Support custom API endpoints and models, code fixes on new branches and draft PRs.
Each flow stays within existing Assistant consent; exact patches are reviewed
before approval and published through shared GitHub operations. Results appear in
the agent conversation, with optional existing notification channels.
Reuses MCP, deployment, jobs and notification paths, with private investigations,
fresh health verification, run history, cooldowns and daily limits. Duplicate
incidents and action retries cannot execute twice; changing access or pausing
invalidates pending work. Cloud agents remain on the chosen customer server. -
Chat app commands — connect Slack, Discord, Telegram or Microsoft Teams in Settings to
list projects, check deployments, open private logs, and confirm redeploys or restarts.
Each sender links their own account through the existing permission flow. Commands are
opt-in, use the normal deployment path without AI, and deduplicate provider retries.
Slack Socket Mode, Discord Gateway and Telegram polling work from Desktop or private
servers without a public URL. Connections report their status, reconnect and recover
durable cursors; Teams retains its public HTTPS webhook requirement. Bot connectivity
runs directly in OpenShip with encrypted credentials and a durable inbox, without
installing or requiring Mindwire. Only the optional assistant uses its agent runtime.
Add separate account-link instructions and URL messages, localized replies following each
user’s OpenShip language, and Telegram welcome, project and confirmation buttons. Share
project command syntax between CLI and chat through@repo/commands; preserve permission
checks and track individual reply messages through retries. -
Opt-in assistant — use Claude Code or Codex through Mindwire in the
Assistant tab, with streaming conversations, structured questions, tool results,
agent connections and private history. Inline permission review reuses the existing
MCP consent form; operations use the normal MCP permissions, deployment flows and audit
rules. Native tools are restricted, retries reuse request receipts, and changing
access requires a new conversation. Disabled by default; available on macOS and
Linux hosts. Cloud uses a private Mindwire profile on the chosen customer server;
Desktop can reuse local sign-in, while self-hosted and Cloud keep separate agent
credentials. Tenant checks, durable consent and renewable turn leases protect
conversations across API replicas. Agents can request additional access in the
conversation; users review it in the shared permission editor. Requests grant
nothing, retain current permissions until saved, and never retry a task automatically.
Remote assistant hosts tolerate slow startup and retain their private
connection record so a retry can reconnect to the same daemon. -
Release hardening — include the shared commands package in self-hosted source
distributions, keep repository changes explicitly classified as source writes,
report safe background failure summaries without logging native credentials,
and refresh the generated API and MCP references. Update compatible dependencies
for published security fixes while retaining the existing OAuth/MCP data model.
Implicit OAuth account linking now requires a verified local account as well
as a provider-verified email, preventing pre-registered account hijacking.
Migrate authenticator confirmation and lockout fields while preserving existing
active factors and unfinished enrollments, including older instance backups.
Preserve failed authenticator and recovery-code counters across denied requests,
so challenge attempt limits and account lockouts cannot be reset by transaction rollback.
Include the assistant type dependency in the public SDK and catalog new audit events. -
Deployment fixes — redact long clone tokens from stored errors and skip the
workspace dependency crawl when checking changes for Compose projects (#1546, #1547).