---
title: "What is Orylo?"
description: "A native Mac home for the agents and model APIs you already use."
locale: "en"
canonical: "https://orylo.io/en/docs/overview"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# What is Orylo?
A native Mac home for the agents and model APIs you already use.
## Your work, with your assistants
Orylo brings local Agents, model APIs, conversations, and tools into one native macOS app. Open a lightweight Composer beside your work, use the full conversation window, or capture an idea through the Notch.
You choose the Assistant and the context to share. Orylo is not a model subscription and does not replace an Agent’s own runtime, login, or usage limits.
## Choose the right entry point
| When you want to… | Use |
| --- | --- |
| Ask a question beside the current app | Composer |
| Follow several conversations or review work | The conversation window |
| Run a reusable action matched to your current context | Actions |
| Capture an idea while looking around | Notch and Narration |
| Create or configure Orylo features by describing what you need | Create with Chat |
| Continue working with your Mac from another device | Remote Web / Messages |
## Availability and the browser demo
Download the latest Orylo release for Apple silicon or Intel from the download page. [Orylo](https://orylo.io/en/download)
The browser demo uses sample content and simulated replies. It does not connect to your Agents, read your files, or grant desktop permissions. This guide describes the implemented Mac experience; available options can differ by Assistant.
## Continue exploring
- [Your first conversation](https://orylo.io/en/docs/quickstart)
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Privacy & data](https://orylo.io/en/docs/privacy-security)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
- [Set up Remote Access](https://orylo.io/en/docs/remote-access)
---
---
title: "Your first conversation"
description: "Set up one Assistant, add a little context, and send your first request."
locale: "en"
canonical: "https://orylo.io/en/docs/quickstart"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Your first conversation
Set up one Assistant, add a little context, and send your first request.
## Before you start
macOS 26 or later · Apple Silicon and Intel. Download the latest Orylo release for Apple silicon or Intel from the download page. [Orylo](https://orylo.io/en/download)
- For a local Agent, install it and complete its own sign-in first. Verify a request in that Agent before connecting it to Orylo.
- For a model API, have your provider endpoint and credentials ready. Provider access and usage charges are separate from Orylo.
- Sign in to Orylo when prompted to check your account access. Your account does not sync conversations or local files.
## Send a request
1. **Create an Assistant** — Open Settings and add an Agent Assistant or Chat Assistant. Run the connection check and enable the Assistant. If setup fails, keep your draft and resolve the connection first.
2. **Open Composer** — Use your configured Composer shortcut, or open Orylo from its Dock or menu bar entry. You can check and change the shortcut in Settings.
3. **Choose the context** — Select your Assistant. For a project-aware Agent, choose its workspace before the first message. Type a question and add a small text or file attachment.
4. **Review and send** — Check the Assistant, workspace, and attachments, then press Return. For example: “Summarize these notes into three next steps.”
## Check the result
Read the reply in the conversation window. Open Activity when you need to inspect tool work, and review any requested permissions before allowing them. A response saying a task is complete is not a substitute for checking the result.
Continue in the same conversation to keep its context. Closing the window preserves your draft and does not quit Orylo or necessarily stop work in progress.
## Continue exploring
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Text, files & context](https://orylo.io/en/docs/context-attachments)
- [Troubleshooting](https://orylo.io/en/docs/troubleshooting)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
---
---
title: "Connect an Assistant"
description: "Understand Agent and Chat Assistants, connection checks, and defaults."
locale: "en"
canonical: "https://orylo.io/en/docs/assistants"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Connect an Assistant
Understand Agent and Chat Assistants, connection checks, and defaults.
## Choose an Assistant type
| Type | Use it for | Keep in mind |
| --- | --- | --- |
| Agent Assistant | Project work with a local Agent such as Codex or Claude Code | Tools, files, and session capabilities depend on the Agent. |
| Chat Assistant | Conversations through a local or cloud model API | No Agent tools or workspace semantics. The provider defines model capabilities. |
## Connect and check
1. **Prepare the source** — Install and authenticate a local Agent using its publisher’s instructions, or configure a model provider. Orylo does not include a general third-party Agent installer.
2. **Create the Assistant** — Choose the source in Settings, give the Assistant a clear name, and set its instructions. You can also ask an already configured Agent Assistant to help with setup; inspect the proposed settings before saving.
3. **Verify availability** — Run the check. A successful check enables a newly created Assistant; a failed check keeps its configuration for troubleshooting. Recheck after fixing the source.
> **Connected does not mean unlimited access**
> An Agent connection does not prove that its provider sign-in, subscription, quota, or next request will succeed. Test provider access in the Agent itself if requests fail.
## Set reusable defaults
Save instructions, a default workspace where supported, and assigned Skills or MCP tools on the Assistant. Model and reasoning options appear only when supported by the source.
Defaults apply to new conversations. A conversation can keep its own model options; its workspace is fixed after the first message. A Chat Assistant can switch among enabled models from its provider within a conversation.
## Continue exploring
- [Use Skills](https://orylo.io/en/docs/skills)
- [Connect MCP tools](https://orylo.io/en/docs/mcp)
- [Troubleshooting](https://orylo.io/en/docs/troubleshooting)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
- [Orylo Intelligence](https://orylo.io/en/docs/orylo-intelligence)
---
---
title: "Create with Chat"
description: "Describe what you need, then create and refine Orylo configurations with an Agent."
locale: "en"
canonical: "https://orylo.io/en/docs/create-with-chat"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Create with Chat
Describe what you need, then create and refine Orylo configurations with an Agent.
## Turn a request into a saved configuration
Create with Chat opens an ordinary conversation with the appropriate built-in creator Skill selected and a draft ready to edit. It does not send the request automatically. Connection-oriented entries are called Connect with Chat.
Use it for a reusable Assistant, a contextual Action, a Skill, a Team or Team template, or a scheduled task. You can continue in the same conversation to refine supported settings.
| Where | What you can ask for |
| --- | --- |
| Assistants / Agents | Create an Assistant with instructions and existing resources, or connect an Agent. |
| Actions / Skills | Create an Action or Action Group, or author and import a complete Skill package. |
| Teams / Team Templates | Define a collaboration template and create a Team with eligible Agent Assistants. |
| Scheduled Tasks | Describe the request, execution target, time zone, and schedule. |
| MCP / Remote | Connect MCP tools, configure Remote Access, or help set up message channels. |
## Create, review, and try
1. **Have one Agent Assistant ready** — Set up and enable your first Agent Assistant manually. A Chat Assistant cannot run these configuration tools, even though a saved AI Action may use a Chat Assistant.
2. **Open the relevant creation menu** — In the feature’s add or creation menu, choose Create with Chat or Connect with Chat. For example, open Settings → Actions and its add menu. Manual creation remains available.
3. **Describe the outcome and boundaries** — For an Action, describe when it should appear, the input, the Assistant, and where the result should go. For a schedule, specify the time zone and target. Review the draft before sending.
4. **Review the actual saved result** — Check the returned settings or detail link. Continue the conversation for supported changes; test separately when ready. Saving an Action does not run it, creating a Team does not send a task, and saving a schedule is not Run Now.
## Start with a concrete request
Skill creation includes importing the validated package into Library. It does not automatically assign the Skill to an Assistant or overwrite another Skill with the same name. See [Skills](https://orylo.io/en/docs/skills).
- “Create an Action that rewrites selected text more clearly, preserves its language, and shows a preview instead of replacing it.”
- “Create a Skill for reviewing release notes and import it into my Library.”
- “Help connect an MCP server to Orylo, but let me review its source and permissions before installation.”
## Assistance is not blanket permission
Creator tools are enabled by the selected creator Skill in an ordinary conversation, not by every chat. Team runs, scheduled executions, and Action executions do not receive these configuration tools.
Logins, secret entry, macOS permission grants, and remote pairing approval remain your steps. Enter credentials in the native secure fields, not in chat. Installation, public exposure, and test messages require your authorization; a saved configuration or a green connection indicator is not proof of a successful real request.
## Continue exploring
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Context-aware Orylo Actions](https://orylo.io/en/docs/actions)
- [Use Skills](https://orylo.io/en/docs/skills)
- [Set up Remote Access](https://orylo.io/en/docs/remote-access)
---
---
title: "Compose a request"
description: "Use Composer for focused requests without losing your place."
locale: "en"
canonical: "https://orylo.io/en/docs/instant-chat"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Compose a request
Use Composer for focused requests without losing your place.
## Open Composer
Use the Composer shortcut configured in Settings. The quick input window normally appears beside the pointer; alternative positions are available in Settings. The Notch provides another entry to the new-conversation draft.
Opening Composer does not mean clipboard content is automatically sent. Review the visible text and attachments before sending.
## Write and refine
- Return sends. Shift, Option, or Control + Return inserts a new line. Confirming an input-method candidate does not send the request.
- Use Markdown for structure. Use @ to choose an available Skill or a Team member where supported.
- Use the + menu to add context or insert a Favorite Prompt. Prompts with variables ask for the required values before insertion; insertion does not send.
- In an empty Composer, Up and Down browse recent prompts from this app session.
## Keep separate drafts
Each existing conversation keeps its own draft. New conversation, quick Composer, and Notch share the new-conversation draft. Hiding and reopening the interface does not discard that draft.
Choose the Assistant and, for Agent work, the workspace before the first message. Changing the Assistant can change the available model options and attachment handling.
An empty, unfocused Composer collapses to its toolbar to leave more room for reading. Click it or type a letter, number or symbol in the active pane to expand and start writing. Shortcuts and other text fields keep their normal behavior. Collapsing does not move the message scroll anchor.
## Continue exploring
- [Text, files & context](https://orylo.io/en/docs/context-attachments)
- [Conversations & workspaces](https://orylo.io/en/docs/conversations)
- [Keyboard shortcuts](https://orylo.io/en/docs/shortcuts)
---
---
title: "Text, files & context"
description: "Review the material you share, and understand what is actually attached."
locale: "en"
canonical: "https://orylo.io/en/docs/context-attachments"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Text, files & context
Review the material you share, and understand what is actually attached.
## Add only what is useful
Paste text or an image, choose files with the + menu, or use a capture action. Text and file attachments remain visible and removable. You can preview attachments before sending.
Automatic selection capture is off by default. When enabled in Settings, it reads the selected text or files when you invoke the relevant shortcut. It never silently replaces a failed selection read with old clipboard contents.
## Understand files and folders
- File and image attachments use local snapshots, so the preview and sent attachment refer to the same captured content even if the original later changes.
- A folder attachment supplies a directory path; attaching it does not automatically read every file inside it. A tool-capable Agent may access files according to its permissions.
- A draft accepts up to 8 images and 20 files; a single snapshot is limited to 50 MB. The Assistant may have additional limits.
- Duplicate attachments are detected by content. Remove an attachment before sending if it should not be shared.
## Check how the Assistant receives it
Image and file delivery depend on the selected Assistant. Images may be sent with extracted text, as text only, or as images according to its capabilities and your OCR preference.
The optional setting to insert selected text into Composer places that text directly in your editable request instead of a separate reference attachment. Review it carefully, especially when the source contains instructions or commands.
## Continue exploring
- [Screenshots & OCR](https://orylo.io/en/docs/capture-ocr)
- [Narrate what you see](https://orylo.io/en/docs/narration)
- [Privacy & data](https://orylo.io/en/docs/privacy-security)
---
---
title: "Conversations & workspaces"
description: "Find your work, keep project context stable, and explore a different direction."
locale: "en"
canonical: "https://orylo.io/en/docs/conversations"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Conversations & workspaces
Find your work, keep project context stable, and explore a different direction.
## Find and organize conversations
Use the sidebar to filter by Assistant, workspace, Team, or tags. Search for a conversation, and use Command + F to search within the open conversation.
Archive finished conversations to keep the active list focused. Archived conversations can be restored; permanent deletion requires confirmation. Local history is not synchronized through your Orylo account.
## Work in several conversation panes
Use the layout button in a conversation header to split left, right, above or below. You can have up to three columns, each with up to two panes; a tall pane beside two stacked panes is supported. Drag the dividers to resize.
A split opens a new draft with the source Assistant, model configuration and working directory, without copying text or attachments. Only one new-conversation draft exists; if it is already open, use Go to existing draft. The same conversation cannot appear twice.
Open a conversation from the sidebar to the right or below, or drag it into a pane. Dropping in the center replaces its conversation; dropping at an edge opens it there. In a multi-pane layout, drag a pane title to move it or swap it with another pane. Closing a pane does not delete its conversation or stop its task.
The active pane receives sidebar selections and conversation commands. Switching focus between open panes preserves their reading positions. Each pane keeps its own input and running conversation. An open right sidebar follows Agent workspaces; focusing a Chat Assistant keeps the last Agent workspace visible. Inactive header actions appear on hover and work on the first click.
Each pane needs at least 450 × 450 points. Orylo expands the window when needed and takes back automatic expansion when panes close. The limit uses the display containing the window, including any open sidebars; it does not automatically narrow them. A split can be unavailable before six panes if space is insufficient. Full screen uses its existing size. Layout and drafts are restored on restart, adjusted to available space.
## Keep the workspace consistent
An Agent conversation keeps the workspace selected before its first message. Start a new conversation when you need a different directory. Chat Assistants do not have a workspace selector.
New conversations can inherit the current Assistant and options. Defaults on an Assistant are starting points, not a way to silently change the project behind an existing conversation.
## Follow work and permissions
The reply shows progress while the Assistant works. Activity holds tool details and supported follow-up questions. Selecting an answer does not submit it: review and explicitly send your answers.
Permission requests explain what is being allowed and its scope. Choose the narrowest suitable permission. Closing a question is not the same as denying a tool request.
## Explore a branch
Branch from a completed reply to try another direction or Assistant while keeping the original conversation. Recent context is passed automatically, without enabling Orylo Intelligence or generating a summary.
The full history stays saved locally. Local Agents can read a complete snapshot when needed. Chat Assistants receive a bounded excerpt with omissions marked; provide any essential missing details in your next message.
## Continue exploring
- [Review files & changes](https://orylo.io/en/docs/change-review)
- [Work with Teams](https://orylo.io/en/docs/teams)
---
---
title: "Review files & changes"
description: "Inspect an Agent’s work without treating every reported change as verified."
locale: "en"
canonical: "https://orylo.io/en/docs/change-review"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Review files & changes
Inspect an Agent’s work without treating every reported change as verified.
## Open the review sidebar
For an Agent conversation, open the right sidebar and choose Review changes or File explorer. Browse text, Markdown, images, and file differences without leaving the conversation.
The reader is not a file editor. Open a file in its default application when you need to edit it. Chat Assistants do not expose this project sidebar.
## Choose the scope
Do not use the Last turn view as proof of every filesystem change. Compare the working repository and inspect the result when completeness matters.
| Scope | What it shows |
| --- | --- |
| Last turn | Completed file changes reported by the Agent for that turn; this can be incomplete. |
| Uncommitted | The working repository’s uncommitted changes. |
| Unstaged | Changes not yet staged in Git. |
| Staged | Changes already staged in Git. |
## Use Git actions deliberately
The Git actions menu can refresh, stage or unstage all, commit, fetch, push, and pull. These actions apply to the full Git repository that contains the current workspace.
A commit includes only staged content. Pull is fast-forward only. Read the result and resolve conflicts rather than assuming a requested action succeeded.
## Continue exploring
- [Conversations & workspaces](https://orylo.io/en/docs/conversations)
- [Work with Teams](https://orylo.io/en/docs/teams)
- [Permissions & control](https://orylo.io/en/docs/permissions)
---
---
title: "Work with Teams"
description: "Give assistants distinct roles and follow their contributions in one place."
locale: "en"
canonical: "https://orylo.io/en/docs/teams"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Work with Teams
Give assistants distinct roles and follow their contributions in one place.
## Create a Team
1. **Choose a collaboration style** — Start with a built-in or saved template. Choose regular collaboration, Pair Review, or Moderated discussion according to the work.
2. **Assign assistants and roles** — Choose the actual Assistant for each role and inspect shared and role instructions. Pair Review needs exactly two participants.
3. **Check workspaces and start** — Set a default workspace and adjust individual member directories when needed. Existing member conversations keep their directories. Creating the Team does not itself send a task.
## Understand the modes
The collaboration mode is fixed when a Team is created. A Team can continue with new requests; you do not need a separate review stage to ask for another review.
| Mode | How work is shared |
| --- | --- |
| Collaboration | A coordinator and members divide a task and exchange results. |
| Pair Review | An author asks a reviewer for feedback and decides how to revise or summarize. |
| Moderated discussion | Participants exchange evidence and views; a moderator gathers conclusions and disagreements. |
## Follow individual contributions
Use the Team view and member conversations to inspect who is working and what each member produced. Open the relevant member when you need to reply directly or inspect its context.
A saved template describes reusable roles; it is not the same as a running Team. Template edits affect future Teams, not existing instances. Tool access still depends on each Assistant and its permissions.
## Continue exploring
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Conversations & workspaces](https://orylo.io/en/docs/conversations)
- [Review files & changes](https://orylo.io/en/docs/change-review)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
---
---
title: "Use Skills"
description: "Reuse instructions and working methods across your assistants."
locale: "en"
canonical: "https://orylo.io/en/docs/skills"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Use Skills
Reuse instructions and working methods across your assistants.
## Build a small, useful library
A Skill packages instructions and supporting resources for a particular job. Use Discovery to find supported local Agent skills, and Library to organize the Skills you bring into Orylo.
Inspect a Skill’s instructions and origin before using it. A Skill is not a security boundary and does not grant permissions or tools by itself.
## Use a Skill in a request
1. **Assign reusable Skills** — Choose the Skills an Assistant should have available in its settings. Keep the set relevant to that Assistant’s role.
2. **Select a Skill explicitly** — Use @ in Composer or the available Skill picker to reference a Skill in your request. The reference stays at the point where you inserted it.
3. **Review before sending** — Check the request and references. If the Skill needs a tool or file, make sure the chosen Assistant actually has access.
## Create and improve Skills
You can work with a configured Agent to create or refine a Skill for a repeated task. Review the resulting instructions and resources before adding or assigning it.
Changing a Skill does not retroactively change replies already generated. Test the revised Skill with a small request and inspect the result.
## Continue exploring
- [Connect MCP tools](https://orylo.io/en/docs/mcp)
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Context-aware Orylo Actions](https://orylo.io/en/docs/actions)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
---
---
title: "Connect MCP tools"
description: "Manage tool connections centrally and assign only what an Assistant needs."
locale: "en"
canonical: "https://orylo.io/en/docs/mcp"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Connect MCP tools
Manage tool connections centrally and assign only what an Assistant needs.
## Add a tool connection
In Settings, use MCP Servers to discover supported local configurations or add a server to Library. Review an imported JSON or Git configuration before accepting it.
Connection helpers can assist with finding and configuring a service. Enter credentials in the dedicated settings fields, not in a chat request. Installing an external server and authorizing its service remain separate steps.
## Test, enable, and assign
1. **Test the connection** — Confirm that the configured server responds. A saved configuration is not proof of a successful connection.
2. **Enable the server** — Check the exposed tools and any required credentials before enabling use.
3. **Assign to an Assistant** — Choose the Assistants and tools that may use the connection. Unassigned services are not made available to every conversation.
## Know the boundaries
Orylo-assigned MCP tools can coexist with an Agent’s own MCP setup. Removing access in Orylo does not automatically remove a separate connection configured directly in that Agent.
The current integration focuses on tools. Built-in MCP OAuth, Resources, Prompts, server package installation, and automatic multimodal attachment conversion are not provided. Follow the connected service’s privacy and authorization rules.
## Continue exploring
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Use Skills](https://orylo.io/en/docs/skills)
- [Privacy & data](https://orylo.io/en/docs/privacy-security)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
- [Orylo Computer Use](https://orylo.io/en/docs/computer-use)
---
---
title: "Orylo Computer Use"
description: "Let your assistants work with Mac apps and Chrome, with access you approve and control you can stop."
locale: "en"
canonical: "https://orylo.io/en/docs/computer-use"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Orylo Computer Use
Let your assistants work with Mac apps and Chrome, with access you approve and control you can stop.
## What it does
Computer Use lets an assigned Assistant inspect supported app interfaces, click controls, enter text, and work with Chrome tabs. It is built into Orylo; you do not need a separate Node or Bun installation. Available actions depend on the target app and the Assistant’s tool support.
## Enable it for an Assistant
Open Settings → MCP Servers → Library. Find Computer Use under Built into Orylo, enable it, and assign it to the Assistant you want to use. It is not assigned to every Assistant by default. Start a conversation with that Assistant and name the app and task clearly.
## Approve access
When the Assistant requests an app, review the application shown in the approval card. Approval applies to the current session. macOS Accessibility permission is needed for native interaction; screenshots and visual observation may also require Screen Recording permission. Grant these to Orylo in System Settings → Privacy & Security when prompted. For Chrome, also confirm remote-debugging access yourself. If Orylo opens Chrome’s remote-debugging settings, enable the option and complete Chrome’s confirmation.
## Preview and end control
While targets are active, use the screen icon beside Composer’s token usage to open previews. Switch between targets, or click a preview title to return to its app or tab. Closing the preview does not stop control. Use End Control to stop that target; stop the conversation to interrupt its current execution. Actions already performed are not undone. If you interact with the controlled app, subsequent automated input pauses until the interaction protection allows it to resume after a fresh observation.
## Observe changes
From Orylo 0.1.9, you can ask the Assistant to watch a selected app or browser tab and continue the conversation when a relevant change is detected. Specify the target, the condition, and what to do next. View active observation tasks from Composer, open their targets, or stop individual tasks. Closing the preview does not stop observation. Tasks do not survive an Orylo restart; visual observation may be unavailable for hidden or minimized windows.
## Try a clear, bounded request
“In Notes, read this draft and suggest three clearer headings. Do not edit it yet.” Or: “Watch this Chrome tab for the export to finish, then tell me. Do not download or submit anything.” These are example requests, not guarantees that every app or page supports the workflow.
## Privacy and troubleshooting
The selected Assistant may receive interface text and requested screenshots or observation images. Your configured Agent or model provider handles those inputs; Computer Use is not a promise of entirely local AI processing. Orylo Backend does not relay these Agent requests. If tools are missing, check the assignment and enabled tools. If access fails, check app approval, macOS permissions, and Chrome’s connection. Review any partial changes before retrying. Removing the MCP assignment revokes that Assistant’s access through Orylo; macOS permissions are managed separately in System Settings.
## Continue exploring
- [Connect MCP tools](https://orylo.io/en/docs/mcp)
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Permissions & control](https://orylo.io/en/docs/permissions)
- [Privacy & data](https://orylo.io/en/docs/privacy-security)
---
---
title: "Context-aware Orylo Actions"
description: "Make reusable actions appear in the right context, combine the inputs they need, and choose exactly how they run and deliver results."
locale: "en"
canonical: "https://orylo.io/en/docs/actions"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Context-aware Orylo Actions
Make reusable actions appear in the right context, combine the inputs they need, and choose exactly how they run and deliver results.
## Actions for your current context
An Orylo Action combines three decisions: when it is available, what it does, and where its result goes. The Action Bar matches your current context to each enabled Action’s rules; you do not need to copy everything into a new conversation first.
Context-aware means matching captured context to your configured rules—not continuously watching the screen or automatically running an Action. You choose which matching Action to run.
| Context | What it contributes |
| --- | --- |
| Selected text | The text you selected; useful for rewriting, translating, or Promptize. |
| Files, folders, or images | Selected files or images, or folder paths, according to the configured input. |
| Web page | The current page URL—not an automatic copy of the page body. |
| Focused window | App identity, the available window title, and an on-demand screenshot; capture requires permission. |
| Application | The active app identity, including an optional specific-app condition. |
## Decide when an Action appears
Choose a Primary Context: it is required and defines the main input. Add All Of conditions when every additional context must be present, or Any Of conditions when at least one alternative must be present. AI Actions receive all configured contexts that are actually available, not just the first matching alternative.
For example, require Selected Text plus Web Page to offer an Action only when text and a page URL are available together. To restrict an Action to a particular app, make Application a required condition and choose that app; an optional Application condition alone does not guarantee exclusivity.
These rules control availability. They do not grant file access or screen-recording permission. If an Action is missing, check its enabled state, required contexts, source app, and capture permissions.
## Choose the operation and result
For AI results, choose the result panel, clipboard, Composer, replacement of the original text selection, or no automatic delivery. Background command output can go to the panel, clipboard, or Composer; opening a new Terminal does not collect output into Orylo. Opening a web page simply opens the configured URL.
Customize the Action’s name, description, icon, enabled state, and ordering as well as its behavior. Review commands before running them: they execute on your Mac and are not made safe merely by being an Action.
| Operation | Customization and boundaries |
| --- | --- |
| AI Action | Choose an Assistant and instructions. It receives the primary and available configured extra contexts. Chat Assistants generate from supplied content; Agent Assistants may use their configured tools. |
| Open Web Page | Set a URL template. Selected text or a page URL can fill its encoded context placeholder. Extra conditions only decide availability; they are not passed into the URL. |
| Run Command | Set the script, working directory, timeout, and background or new Terminal execution. Only the primary input is passed as data; app/window inputs currently provide no context text to the script. |
## Create with Chat—or configure it yourself
1. **Describe the workflow** — Open Settings → Actions → add → Create with Chat. Specify the primary input, required context, operation, Assistant where needed, and delivery. You need an already working Agent Assistant for creation.
2. **Check the proposed definition** — Ask for a preview and confirm the matching conditions, instructions or command, target Assistant, and output destination. Save only the intended configuration; saving does not execute the Action.
3. **Try it on a small example** — Return to the intended app and context, open the Action Bar, and run the saved Action deliberately. Refine it in Settings or continue the creation conversation. Create Manually is also available.
## Organize choices with Action Groups
A Group is a menu of alternatives, not a sequence that runs every child. For example, a selected-text group can offer an AI explanation, a web search, and a local command. You open the group and choose one Action.
Children share the group’s input and appearance conditions, but may use different operations and result destinations. Groups cannot be nested. An entirely disabled group has no usable entry.
## Share and customize Action definitions
Actions and Action Groups support JSON import and export. Review an imported definition’s matching rules, instructions, commands, and output before using it. Assistant references must resolve on the receiving Mac; an identical display name is not enough.
The JSON format also supports exclusion conditions (None Of), which are not exposed in the current visual editor. A command with a fixed local working directory cannot currently be exported. Portable definitions do not include captured inputs, execution history, or your local ordering preferences.
## Run and follow an execution
1. **Bring the context** — Select the text, files, folder, or image you need, or focus the relevant app/window. Open the Action Bar with the shortcut configured in Settings.
2. **Choose a matching Action** — Inspect its intent before running. An AI Action uses a separate execution session, not your open conversation’s history. Do not assume it carries the context of a previous chat.
3. **Inspect progress and output** — Open Action Executions from the expanded Action Bar to view running and recent results, partial output, and errors. Hiding the bar does not cancel a run; explicitly stop it in the execution detail.
## Keep control of delivery and permissions
Automatic replacement is only available for an AI Action with selected text as its primary input. It depends on the source app and the original selection still being valid and editable. If delivery fails, inspect the retained result rather than rerunning a potentially side-effecting task.
Actions do not offer an interactive permission-approval flow. Requests requiring a new approval are not silently allowed; use a normal conversation for work that needs that interaction. Existing Agent permissions still matter.
Execution records are temporary for the current app session, not permanent conversation history, and do not survive an app restart. Copy or save results you need to keep. Optional Action suggestions are off by default and produce reviewable drafts, not automatically enabled or executed Actions.
## Continue exploring
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
- [Text, files & context](https://orylo.io/en/docs/context-attachments)
- [Use Skills](https://orylo.io/en/docs/skills)
- [Permissions & control](https://orylo.io/en/docs/permissions)
- [Orylo Intelligence](https://orylo.io/en/docs/orylo-intelligence)
---
---
title: "Schedule recurring work"
description: "Set up a local schedule and inspect each run separately."
locale: "en"
canonical: "https://orylo.io/en/docs/scheduled-tasks"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Schedule recurring work
Set up a local schedule and inspect each run separately.
## Create a schedule
Open Scheduled Tasks from the conversation sidebar. Use the + menu to create a task manually or through a setup conversation. Specify the request, Assistant, target conversation, time, and timezone.
Choose a one-time, daily, or weekly schedule, with a repeat limit or no fixed end. A run can use an existing conversation or start a new one. Saving an active schedule enables future triggers; it does not immediately run a test.
## Understand when work runs
Use a fixed timezone deliberately, especially when travelling. Verify the next scheduled time rather than assuming it follows your Mac’s current timezone.
> **Schedules run on your Mac, not in the cloud**
> Orylo must be running and the Mac must be awake. Missed runs are skipped by default; you can choose to catch up the most recent missed run within one hour.
## Pause and inspect
Pause a schedule to stop future triggers. A run already claimed can continue; stopping that run is a separate action.
Open run history to inspect success, failure, and the resulting conversation. A schedule’s active, paused, or completed state is distinct from the outcome of an individual run.
## Continue exploring
- [Conversations & workspaces](https://orylo.io/en/docs/conversations)
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Troubleshooting](https://orylo.io/en/docs/troubleshooting)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
---
---
title: "Orylo Intelligence"
description: "Let your Assistants handle the little things and make Orylo work better for you."
locale: "en"
canonical: "https://orylo.io/en/docs/orylo-intelligence"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Orylo Intelligence
Let your Assistants handle the little things and make Orylo work better for you.
## Set up Orylo Intelligence
Open Settings → Orylo Intelligence, select a feature, choose an Assistant, and enable it. Each feature has its own Assistant and optional Generation requirements for language, style, or emphasis. Leave requirements empty to use the built-in instructions.
Titles and tags are enabled by default, but still need a configured Assistant. The other features are off by default.
You can select a specific Assistant or follow the default Assistant. Open Assistant Settings to choose the model and its default reasoning effort; the available controls depend on the model. These are Assistant settings, so they also affect other uses of that Assistant. For separate settings, create an Assistant dedicated to Intelligence.
## Conversation titles
After the first message you send, Orylo creates a short title so conversations are easier to find. A title you set manually takes priority. If generation fails, the existing title stays.
- **Input:** An excerpt from the first message you send; attachment files are not read.
- **Output:** A descriptive title of up to 60 characters, based on the task or topic you want help with.
- **Assistant and reasoning:** Choose a Chat Assistant for this feature; Agent Assistants are also supported. In the selected Assistant’s settings, use a lower Reasoning Effort, such as Low, if the model offers it. If it does not, keep the available defaults.
## Existing tags
After a successful reply, Orylo can apply relevant tags from your existing tag list. Create tags first. It does not invent new tags or restore tags you removed manually; no matching tag is also a valid result.
- **Input:** Excerpts from up to six recent messages and your existing tag names.
- **Output:** A selection of relevant existing tags, or no tags when none fit.
- **Assistant and reasoning:** Choose a Chat Assistant for this feature; Agent Assistants are also supported. In the selected Assistant’s settings, use a lower Reasoning Effort, such as Low, if the model offers it. If it does not, keep the available defaults.
## Action suggestions
Enable this feature to find repeated workflows across new conversations in the same workspace. It needs evidence from at least two independent conversations and runs after inactivity, at most once per day. Existing Actions are considered so suggestions can improve an Action rather than duplicate it.
Review and edit suggestions in this feature’s settings. Continue with Action Creator to open a draft in an Agent chat, then send it and confirm the final configuration. A suggestion never automatically creates or runs an Action.
Generating the suggestion needs no tools. Creating the Action with Action Creator is a separate step that requires a tool-capable Agent Assistant.
- **Input:** Excerpts from up to 12 new conversations in the same workspace and the existing Actions catalog.
- **Output:** An editable proposal to create or improve an Action, with supporting conversation references; it is not an executable Action.
- **Assistant and reasoning:** Choose a Chat Assistant for this feature; Agent Assistants are also supported. In the selected Assistant’s settings, use a lower Reasoning Effort, such as Low, if the model offers it. If it does not, keep the available defaults.
## Next prompt suggestions
After a new successful reply, an eligible conversation with at least two completed replies may show a suggested next message in the empty input box. It follows your conversation language, including Chinese. Press Tab to turn it into an editable draft; it is not sent automatically. Typing takes priority.
Remote Web can display suggestions generated on your Mac; on mobile, tap the button to use the suggestion. Opening a conversation does not generate one. Suggestions can return when you reopen the same unchanged conversation during the current app session, but disappear when Orylo restarts.
- **Input:** Up to 12 recent completed messages in the current conversation, within a limited context budget.
- **Output:** One short next-message suggestion in the conversation’s language, or no suggestion when no useful next message is clear.
- **Assistant and reasoning:** Choose a Chat Assistant for this feature; Agent Assistants are also supported. In the selected Assistant’s settings, use a lower Reasoning Effort, such as Low, if the model offers it. If it does not, keep the available defaults.
## Privacy and troubleshooting
These features use limited conversation excerpts, not attachment contents or private Agent history. A remote model receives the text required for the selected feature; an on-device Assistant processes it on your Mac. Normal provider usage charges may apply.
If nothing appears, check that the feature is enabled and its Assistant is available, then check its trigger conditions in the information panel. No useful suggestion, insufficient context, or a failed request can produce no result. Intelligence failures do not block normal chat.
## Continue exploring
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Context-aware Orylo Actions](https://orylo.io/en/docs/actions)
- [Conversations & workspaces](https://orylo.io/en/docs/conversations)
---
---
title: "Use the Notch"
description: "Keep an idea or an Assistant’s progress close without opening a full window."
locale: "en"
canonical: "https://orylo.io/en/docs/notch"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Use the Notch
Keep an idea or an Assistant’s progress close without opening a full window.
## One entry, three views
The optional Notch entry brings together Composer, Narration, and an Assistant overview. It is an additional entry point, not a separate conversation system. You can use Orylo without a physical camera notch.
Composer in the Notch shares the new-conversation draft with quick Composer. Opening it does not switch an existing conversation in the work window or automatically capture the current selection.
## Check work at a glance
The Assistant overview shows available assistants and their active or unread work. Select an Assistant to compose, or a task to return to its conversation. Unavailable assistants are not listed in the overview.
Pin keeps the Notch open. Unpin releases that setting; moving the pointer away can then collapse it. Collapsing preserves an unfinished draft or Narration session.
## Move into a conversation
Send the reviewed draft to continue in the full conversation window. The Notch is for getting started and staying aware; longer replies, files, and Team work belong in the conversation.
## Continue exploring
- [Compose a request](https://orylo.io/en/docs/instant-chat)
- [Narrate what you see](https://orylo.io/en/docs/narration)
- [Conversations & workspaces](https://orylo.io/en/docs/conversations)
---
---
title: "Narrate what you see"
description: "Collect spoken notes and selected context while moving through your work."
locale: "en"
canonical: "https://orylo.io/en/docs/narration"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Narrate what you see
Collect spoken notes and selected context while moving through your work.
## Start a Narration
1. **Open Narration** — Open the Narration view in the Notch and start a session. Grant only the permissions required for the inputs you use.
2. **Describe the current scene** — Speak while looking at the relevant apps or pages. Add captures or selected images when a visual detail matters. Pause when you need to leave something out.
3. **Stop and review** — Inspect the collected steps, text, images, and available page context. Remove anything you do not want to share.
## Understand the collected context
During recording, available app, window, and browser page information helps organize the steps. A page URL change can create a distinct step even without speech or a screenshot.
Page information depends on access and successful reads. Orylo does not reuse a stale URL after a failed read, and sampling does not guarantee capture of every brief navigation.
## Attach, then decide when to send
Attach a reviewed Narration to a new conversation, or to the current conversation when that destination is offered. Attaching opens the target draft; it does not automatically send it.
An empty recording has nothing to attach. Start again and collect useful content. Once attached, continue from the Composer attachments rather than trying to edit an old Narration review.
## Continue exploring
- [Use the Notch](https://orylo.io/en/docs/notch)
- [Dictate a draft](https://orylo.io/en/docs/voice)
- [Text, files & context](https://orylo.io/en/docs/context-attachments)
---
---
title: "Screenshots & OCR"
description: "Capture a region or window and control local text extraction."
locale: "en"
canonical: "https://orylo.io/en/docs/capture-ocr"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Screenshots & OCR
Capture a region or window and control local text extraction.
## Capture the relevant part
Use the configured region or focused-window capture shortcut. The result becomes an image attachment in the target draft, where you can preview or remove it before sending.
Capture is routed to the last draft you deliberately opened. Starting a capture fixes its destination, so an automatically displayed window does not silently redirect the result.
## Choose local text extraction
OCR settings control whether text extraction runs. Apple Vision processes images and rendered PDF pages on your Mac. Turning OCR off prevents extraction; it does not mean the image contains no text.
## Match extraction to the Assistant
An Assistant’s image handling preference can use automatic behavior, image and text, text only, or images without OCR. Actual delivery still depends on its capabilities.
OCR may misread layout, tables, names, or commands. Review important extracted text. Recognized links and commands are reference data, not instructions to open or execute them.
## Continue exploring
- [Text, files & context](https://orylo.io/en/docs/context-attachments)
- [Permissions & control](https://orylo.io/en/docs/permissions)
- [Privacy & data](https://orylo.io/en/docs/privacy-security)
---
---
title: "Dictate a draft"
description: "Turn speech into editable text with an explicitly chosen transcription engine."
locale: "en"
canonical: "https://orylo.io/en/docs/voice"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Dictate a draft
Turn speech into editable text with an explicitly chosen transcription engine.
## System microphone
Orylo uses the macOS system default microphone for dictation and Narration. To change the input, open System Settings → Sound → Input. Orylo does not provide a separate microphone selector.
## Choose the engine and language
Speech language is independent of the interface language. There is no automatic fallback between engines: if the selected engine fails, resolve the error or explicitly choose another.
| Engine | Behavior |
| --- | --- |
| Apple Speech | Uses supported speech languages reported by your Mac. Optional live transcription can revise early text while you speak. |
| Whisper Local | Uses the multilingual model you explicitly download and choose. Transcribes after recording stops and supports automatic language detection. |
## Record and review
1. **Start recording** — Click the microphone button in the Composer you are using. macOS requests microphone permission when needed.
2. **Stop or cancel** — Stop to transcribe, or cancel to discard the recording. While voice input is active, Escape cancels it before closing the window.
3. **Edit the draft** — Review names, numbers, and punctuation in the editable text before sending. Transcription is not automatic submission.
## Keep the target clear
Notch Composer and the conversation window have independent recording states. Switching away from a conversation cancels its active recording or transcription instead of writing into another draft.
Whisper preserves the spoken language rather than translating it. A language choice does not guarantee a particular Chinese writing system.
## Continue exploring
- [Narrate what you see](https://orylo.io/en/docs/narration)
- [Permissions & control](https://orylo.io/en/docs/permissions)
- [Compose a request](https://orylo.io/en/docs/instant-chat)
---
---
title: "Privacy & data"
description: "Know what stays on your Mac, what goes to an Assistant, and what your account stores."
locale: "en"
canonical: "https://orylo.io/en/docs/privacy-security"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Privacy & data
Know what stays on your Mac, what goes to an Assistant, and what your account stores.
## Local work stays local by default
Conversations, attachment snapshots, local Assistant configuration, Teams and Actions are stored on your Mac. They are not synchronized through your Orylo account.
Local storage does not mean every Assistant is offline. An Agent or model provider can send your request to its own services according to its configuration and policies.
## When you send a request
Your chosen Assistant receives the request and the context supplied to it, including applicable instructions, selected attachments. Inspect the draft and Assistant configuration before sharing sensitive material.
Orylo’s account backend is not a proxy for Agent requests, replies, files, captures, or workspaces. External tools and providers apply their own privacy and retention rules.
## What online account services store
Orylo online services handle identity, purchase entitlement, device licensing, and feedback. Device records include an installation identifier, a public key, activation times, and the latest app and Mac configuration used for compatibility statistics.
Configuration includes macOS version, architecture and chip model, Mac model identifier, and app version/build. Orylo does not collect the hardware serial number or computer name for licensing. Device records are removed when the account is deleted.
## Share less, deliberately
Remove unnecessary attachments, and inspect tool permissions. Optional feedback diagnostics exclude prompts, replies, file paths, file contents, window titles, tokens, API keys, and environment variables.
Read the [Privacy Policy](https://orylo.io/en/privacy) for the formal terms. Deleting local content does not retract data already delivered to an external Agent or service.
## Continue exploring
- [Permissions & control](https://orylo.io/en/docs/permissions)
- [Account & devices](https://orylo.io/en/docs/account)
---
---
title: "Permissions & control"
description: "Understand macOS access and the separate permissions used by an Agent."
locale: "en"
canonical: "https://orylo.io/en/docs/permissions"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Permissions & control
Understand macOS access and the separate permissions used by an Agent.
## Grant system access when needed
Use System Settings → Privacy & Security to review or change access. Orylo reads the real macOS authorization state; it does not bypass system permissions.
| Permission | Why it is needed |
| --- | --- |
| Accessibility | Read the current selection for enabled context features and supported actions. |
| Microphone | Record voice drafts or spoken input. |
| Screen Recording | Capture screen regions or windows where macOS requires it. |
## Review Agent tool requests separately
An Agent can request permission to use tools, commands, directories, or hosts. Read the requested operation and choose a suitable scope: once, this session, always, or deny when those choices are offered.
Session permission is not shared across Team members. In the current implementation, the cross-conversation “always” grant is cleared when Orylo quits. Required input forms still need to be completed each time.
## Recover after changing a permission
1. **Check the exact permission** — Open the relevant Privacy & Security section and enable Orylo if you want that feature to work.
2. **Return to the source** — Select the text, focus the window, or open the Composer again. Do not assume a previous failed capture was retained.
3. **Retry the action** — Run the operation again. Some system changes require restarting the app. Managed-device restrictions may need help from your administrator.
## Continue exploring
- [Privacy & data](https://orylo.io/en/docs/privacy-security)
- [Context-aware Orylo Actions](https://orylo.io/en/docs/actions)
- [Troubleshooting](https://orylo.io/en/docs/troubleshooting)
- [Orylo Computer Use](https://orylo.io/en/docs/computer-use)
---
---
title: "Account & devices"
description: "Manage sign-in, access, and activated Macs without syncing your work."
locale: "en"
canonical: "https://orylo.io/en/docs/account"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Account & devices
Manage sign-in, access, and activated Macs without syncing your work.
## Use the same account
Use Apple or Google to sign in on the Mac and on the [account page](https://orylo.io/en/account). Complete authorization in your browser and return to the app when prompted.
Use the same sign-in identity for your entitlement. An Apple private relay address and a Google address are not automatically treated as the same account. There is no license-key entry step.
## Understand access
The first eligible sign-in starts a seven-day trial, once per account. When the trial ends, sending and the Action Bar require valid purchase access; history and settings remain available.
Provider subscriptions and API usage are separate. Orylo does not include model credits. Check the current purchase screen and [Terms of Service](https://orylo.io/en/terms) for the offer and refund conditions, rather than relying on a price copied into this guide.
The end of update eligibility is not the same as the end of a valid purchased right to use the covered version.
## Manage your Macs
A personal license allows up to two active Macs, with up to four activations in a rolling 30-day period, including the first two. During valid trial or purchased access, deactivate an old Mac on the account page, then use Refresh access in the app on the Mac you want to activate.
Deactivation does not refund an activation slot in the rolling count, erase local work, or immediately revoke an already cached offline verification. Offline access on a deactivated Mac can last until that verification expires, at most 72 hours. Trial expiry can end access earlier.
## Continue exploring
- [Your first conversation](https://orylo.io/en/docs/quickstart)
- [Privacy & data](https://orylo.io/en/docs/privacy-security)
- [Troubleshooting](https://orylo.io/en/docs/troubleshooting)
---
---
title: "Keyboard shortcuts"
description: "Keep frequent actions close and check configurable bindings in Settings."
locale: "en"
canonical: "https://orylo.io/en/docs/shortcuts"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Keyboard shortcuts
Keep frequent actions close and check configurable bindings in Settings.
## Check your global bindings
Composer, Actions, and capture shortcuts can be configured. Settings is the source of truth for your current bindings; change a shortcut if another app already uses it.
The app’s input hints show shortcuts you have not used yet. A shortcut shown in a screenshot or an older guide may not match your configuration.
## While composing
| Action | Keys |
| --- | --- |
| Send the request | Return |
| Insert a new line | ⇧ + Return |
| Cancel active voice input or hide the input window | Esc |
| Browse recent prompts in an empty Composer | ↑ + ↓ |
| Bold | ⌘ + B |
| Italic | ⌘ + I |
| Inline code | ⌘ + E |
## In the conversation window
Control + Option + D is not a global shortcut. Command + Q quits Orylo; closing a window does not.
| Action | Keys |
| --- | --- |
| Find in the conversation | ⌘ + F |
| Open the Orylo work window | ⌘ + 0 |
| Close the window without quitting | ⌘ + W |
| Toggle voice draft while Orylo has keyboard focus | ⌃ + ⌥ + D |
## Continue exploring
- [Compose a request](https://orylo.io/en/docs/instant-chat)
- [Conversations & workspaces](https://orylo.io/en/docs/conversations)
- [Dictate a draft](https://orylo.io/en/docs/voice)
---
---
title: "Set up Remote Access"
description: "Pair another device with the Orylo running on your Mac, over a trusted local network or your own HTTPS connection."
locale: "en"
canonical: "https://orylo.io/en/docs/remote-access"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Set up Remote Access
Pair another device with the Orylo running on your Mac, over a trusted local network or your own HTTPS connection.
## Remote Access is a connection to your Mac
Remote Access serves the Remote Web interface from your Mac. It is not the orylo.io browser demo, a hosted cloud Agent, or a remote-desktop screen-sharing service. Your Mac must remain online, awake, and running Orylo.
Open Settings → Remote. Remote Access controls browser connections; Messages controls message channels. Their switches are independent: closing Settings or disabling browser access does not stop message channels.
| Connection | Use and requirements |
| --- | --- |
| Local network | Phone and Mac must be mutually reachable on a trusted LAN. HTTP is unencrypted; do not expose it directly to the public internet. |
| Remote HTTPS | Use your own HTTPS proxy or tunnel to reach the Mac listener. Configuring an HTTPS address in Orylo does not install a proxy, create a certificate, or prove outside-network reachability. |
## Connect on your local network
1. **Enable Remote Access** — In the Mac settings, review the local address and port, acknowledge the unencrypted LAN connection, and enable access. Start with devices on the same reachable network.
2. **Pair the device** — Choose Pair a device, open the displayed invitation or QR code on the intended device, and approve that device on the Mac. Do not share the invitation publicly.
3. **Try a harmless request** — Open a conversation in Remote Web, verify its Assistant and workspace, and send a small test request. Check the actual reply; an available listener alone proves neither pairing nor Agent execution.
## Reach the Mac away from home
For HTTPS, first establish the Mac listener, then configure your proxy or tunnel and the exact external HTTPS origin in Remote settings. Preserve the external host and origin through the proxy; do not disable certificate or origin checks to fix connection errors.
Connect with Chat can help inspect configuration and prepare a proxy setup. You still authorize public exposure, enter secrets securely, and approve the device. Pair separately for the HTTPS address; a LAN pairing is not an HTTPS login.
Test from the intended external network, such as phone cellular data with Wi-Fi off. A request to the public URL from the Mac is not sufficient evidence that the phone can reach it.
## Understand authorization and disconnection
A paired Web device can access the whole conversation workspace, including existing, future, and archived conversations—not just one selected chat. Pair only trusted devices. Orylo account sign-in is separate from this device approval.
Revoke an unwanted device in Remote settings. Revocation removes that device’s access; it is not a request to cancel every task running on the Mac. Closing access does not delete native conversation history.
If the address changes, use the current address or IP fallback shown on the Mac and pair again when needed. Check sleep, network isolation, VPN routing, and proxy status before changing credentials. A last-connected time is not a live connectivity indicator.
## Continue exploring
- [Work in Remote Web](https://orylo.io/en/docs/remote-web)
- [Supported message channels](https://orylo.io/en/docs/message-channels)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
- [Privacy & data](https://orylo.io/en/docs/privacy-security)
---
---
title: "Work in Remote Web"
description: "Continue native Mac conversations from a phone or browser, with files, work review, and scheduled tasks."
locale: "en"
canonical: "https://orylo.io/en/docs/remote-web"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Work in Remote Web
Continue native Mac conversations from a phone or browser, with files, work review, and scheduled tasks.
## The same work, another entry point
After [pairing your device](https://orylo.io/en/docs/remote-access#pair-device), Remote Web uses the same conversations, Assistants, workspaces, history, and execution runtime as the Mac. It does not upload a second copy to the Orylo account backend.
Moving around the Web interface does not change the selected Mac conversation or overwrite its Composer draft. Sending a request or taking an explicit action does affect the target conversation on your Mac.
| Area | What you can do |
| --- | --- |
| Conversations | Browse, search, create, rename, archive or restore, and add/remove conversation tags. Choose from Assistants and workspaces already available on the Mac. |
| Composer | Send text and supported attachments; choose available model options, Skills, and favorite prompts. The selected Assistant determines what it can process. |
| Messages and control | Read and copy replies, preview attachments, stop a specific run, answer supported questions, and approve or deny supported requests once. |
| Work review | For Agent workspaces, inspect changes and preview files in the right sidebar. Available Git actions operate on the Mac repository; the file preview is not an editor. |
| Teams and branches | Read existing Team activity and member conversations. Fork an eligible completed reply with full history or an editable summary; Team creation and management remain on the Mac. |
| Scheduled tasks | Use the calendar and task details to create, edit, pause, resume, run, or delete tasks. They still execute through the Mac’s scheduler. |
## Continue a task from your phone
1. **Choose the conversation** — Open the left drawer and select the conversation, or create one with an available Assistant. A workspace is a directory on the Mac, not a folder on the phone.
2. **Add only the context you need** — Review the Assistant, model options, text, and attachments before sending. The plus menu offers attachments and available Library items. Check any displayed attachment limits.
3. **Review the result** — Follow the reply and inspect files or changes where supported. If a request needs an unsupported permission decision or configuration change, complete it on the Mac.
## Available features and limitations
Remote Web does not turn the phone into a remote desktop or provide arbitrary access to its files. File browsing is limited to the authorized Mac workspace. Git writes require explicit actions; inspect their scope before committing, pushing, or pulling.
Mac permissions and Agent policies still apply. The browser only offers supported one-time decisions, not a blanket permission override. If a network interruption leaves an operation uncertain, check the resulting state before repeating it.
Connection quality, mobile keyboards, attachments, and platform-specific behavior need verification on your actual devices; the website demo does not validate a real Remote connection.
## Continue exploring
- [Set up Remote Access](https://orylo.io/en/docs/remote-access)
- [Supported message channels](https://orylo.io/en/docs/message-channels)
- [Review files & changes](https://orylo.io/en/docs/change-review)
- [Schedule recurring work](https://orylo.io/en/docs/scheduled-tasks)
---
---
title: "Supported message channels"
description: "Reach Orylo through iMessage, Telegram, Discord, WeChat, Slack, or Feishu/Lark—with explicit chat authorization."
locale: "en"
canonical: "https://orylo.io/en/docs/message-channels"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Supported message channels
Reach Orylo through iMessage, Telegram, Discord, WeChat, Slack, or Feishu/Lark—with explicit chat authorization.
## Choose a channel
Open Settings → Remote → Messages. Each channel has its own switch and connection setup; it does not require Remote Web to be enabled. Your Mac must stay awake, connected, and running Orylo.
These are implemented channel integrations in the current Mac build, not a promise of universal platform availability. Provider policies, regional access, app installation, and permissions still apply. Verify setup and an actual round-trip with your own account.
| Channel | Setup | Conversation scope |
| --- | --- | --- |
| iMessage | Use Messages on this Mac, install the optional Orylo helper when prompted, and grant the required macOS permissions. | Explicitly connected one-to-one chats; it is not an inbox of all your Messages history. |
| Telegram | Add your bot credentials securely in the Mac settings; polling is used, not a webhook. | Approved bot direct messages; multiple bots can be configured. |
| Discord | Install your bot and enter its credentials securely; users must be able to message it. | Approved bot direct messages, not server-channel or group messages; multiple bots are supported. |
| Personal WeChat | Use the native iLink QR sign-in and confirm it in WeChat. | Authorized private chats, not WeChat groups; replies require a valid recent inbound context. |
| Slack | Install your Slack app with the required scopes/events and Socket Mode; Connect with Chat can help prepare the configuration. | Approved direct messages, plus explicitly approved channel @mentions with separate conversation threads. |
| Feishu / Lark | Configure the app’s permissions, events, credentials, and long connection for the correct region. | Approved private chats; platform or organization approval may be required. |
## Connect and verify one chat
Messages from an authorized chat use its linked native Orylo conversation. Changing the link does not rewrite the old history, and old chat history is not imported or replayed as fresh tasks. Use the channel’s help to see supported conversation-management commands; Slack private commands use the /orylo prefix.
1. **Prepare the channel** — Use its native setup for a token field or QR sign-in. For multi-step app permissions, installation, or diagnostics, choose Connect with Chat. Enter secrets only in secure native fields, not in the conversation.
2. **Authorize the intended contact** — For bot pairing, send a private message and compare the returned pairing code with the request on the Mac before approving. For iMessage, use its native new-chat flow. Select or create the intended Orylo conversation and confirm the Assistant and workspace.
3. **Send a fresh test request** — The initial bot pairing message is not executed or replayed as a task. After authorization, send a new harmless request and check the final reply. A connected transport or a successful test send does not prove the Agent can complete work.
## Slack channel mentions are an explicit exception
After you approve a Slack channel on the Mac, any member of that channel can invoke Orylo with an @mention. Each thread gets its own native conversation, and replies stay in that thread. Decide whether that channel-wide access is appropriate before approving it.
Orylo does not import channel history or send ordinary channel messages or unmentioned thread replies to the Agent. A channel thread cannot be linked to an existing conversation and does not accept private-chat management commands. Disconnecting one thread revokes that bot’s connections for the whole channel; native history is preserved.
Slack may require broader platform scopes than Orylo’s message-processing rules. Orylo can fetch a single thread-root message to label the thread; it does not pass that root message to the Agent as context. Review the app’s actual requested permissions before installation.
## Know what crosses the channel
Channels deliver final text replies rather than token-by-token output. Supported incoming attachments depend on the channel and the Assistant; a failed required attachment rejects the input rather than silently sending its caption alone. Do not assume every native attachment or rich result can be delivered back through every platform.
Message channels do not grant automatic approval for Agent permission requests. Complete unsupported approvals on the Mac; an ordinary “yes” message is not permission to bypass them. Use Remote Web when you need its supported interactive controls.
Only authorized chats are connected, but messages you send and replies delivered through a platform also pass through that platform. Orylo’s local-first storage does not make an external message service local or guarantee end-to-end encryption. Disabling a channel stops that entry, not the native Mac app or all its tasks.
## Continue exploring
- [Set up Remote Access](https://orylo.io/en/docs/remote-access)
- [Work in Remote Web](https://orylo.io/en/docs/remote-web)
- [Create with Chat](https://orylo.io/en/docs/create-with-chat)
- [Permissions & control](https://orylo.io/en/docs/permissions)
---
---
title: "Troubleshooting"
description: "Start with the failing step, preserve your draft, and check the result before retrying."
locale: "en"
canonical: "https://orylo.io/en/docs/troubleshooting"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Troubleshooting
Start with the failing step, preserve your draft, and check the result before retrying.
## The Assistant connects but cannot answer
1. **Test the source** — For a local Agent, make one request in its own CLI or client. Check its sign-in, API credentials, subscription, and quota there.
2. **Recheck in Orylo** — Open the Assistant’s settings, inspect the failure reason, and rerun the check after fixing the source. Verify the configured model and options.
3. **Use a small request** — Try plain text without attachments. Add the original context back gradually to distinguish a connection failure from an unsupported input or size limit.
## Selection, screenshots, or voice are missing
- Confirm automatic selection capture is enabled if that is the feature you expect; it is off by default.
- Check the relevant macOS permission and retry from the source app. Clipboard content is not a fallback for an unreadable selection.
- For speech, verify the explicitly chosen engine, supported language, and downloaded Whisper model. Orylo does not silently switch engines.
- For OCR, verify the global switch and Assistant image preference. Review the original image when extraction fails.
## A scheduled task did not run
Check that Orylo was running, the Mac was awake, the schedule was enabled, and its timezone and next run were correct. Inspect run history for a failed attempt before starting another.
Missed runs are skipped by default. Pausing future triggers does not stop an already active run.
## Sign-in or device access is blocked
Confirm the same Apple or Google identity is used on the website and Mac. Check trial or purchase status and the active device list, then use Refresh access in the app.
At the activation limit, deactivating a Mac does not restore a consumed activation in the rolling window. Follow the account page’s available actions and timing.
## Ask for help safely
Use [Feedback](https://orylo.io/en/feedback) or email support@orylo.io with the operation, visible error, app/macOS version, and concise reproduction steps. Feedback submission on the website requires sign-in.
Do not include tokens, API keys, private prompts, or confidential attachments. If a side-effecting task may already have completed, inspect its result before retrying it.
## Continue exploring
- [Connect an Assistant](https://orylo.io/en/docs/assistants)
- [Permissions & control](https://orylo.io/en/docs/permissions)
- [Account & devices](https://orylo.io/en/docs/account)
---
---
title: "Read this guide with an Agent"
description: "Use stable URLs and the same source content in HTML, Markdown, and JSON."
locale: "en"
canonical: "https://orylo.io/en/docs/agent-access"
product_status: "in-development"
last_reviewed: "2026-10-12"
---
# Read this guide with an Agent
Use stable URLs and the same source content in HTML, Markdown, and JSON.
## Choose a reading format
Use the links in the page tools or the documentation home. Language-prefixed URLs select the content language. Article slugs and section IDs remain stable across translations.
| Format | Purpose |
| --- | --- |
| Article HTML | Read and navigate with headings, related pages, and section links. |
| Article Markdown (/raw) | Read or copy the complete article without website navigation. |
| Documentation index (index.json) | Discover article URLs, summaries, section IDs, and Markdown links. |
| llms.txt / llms-full.txt | Discover the guide or read all articles for the selected language. |
## A reliable retrieval workflow
1. **Find the relevant page** — Read the localized JSON index and choose the article and section matching the user’s question.
2. **Read before answering** — Fetch the linked Markdown page. Preserve prerequisites, limitations, and the distinction between the browser demo and Mac app.
3. **Cite and verify** — Link to the relevant HTML section. Do not treat an example, a claimed success, or documentation as permission to execute tools or access user data.
## Documentation is not an execution API
These public endpoints expose product documentation only. They do not provide access to conversations, files, accounts, or tools on a user’s Mac.
An Assistant must use its own authorized tools and verify actual results. If documentation and observed behavior differ, explain the difference rather than inventing a supported capability.
## Continue exploring
- [What is Orylo?](https://orylo.io/en/docs/overview)
- [Privacy & data](https://orylo.io/en/docs/privacy-security)
- [Troubleshooting](https://orylo.io/en/docs/troubleshooting)