These answers describe the shared Orutta model. Provider availability, models, limits, permissions, and session behavior can still vary by runtime, account, operating system, and release.

Still have a question?

Search the documentation and existing GitHub issues. When the answer depends on a specific failure, use the reporting guide rather than posting an unredacted transcript.

Diagnostics Report a problem

Frequently asked questions

What is Orutta?

Does Orutta include model access or a subscription?

Which providers are supported?

Why does Orutta not detect a provider that works in my terminal?

Why are models missing?

Does Orutta upload my repository to a Orutta cloud account?

Can I use a repository that is not on GitHub?

Can I use a folder that is not a Git repository?

When should I use a worktree?

Is a detached HEAD in a Orutta worktree an error?

What is the difference between a task, turn, and provider session?

How do I know whether a task is actually stuck?

Does interrupting a turn undo its changes?

Is the provider’s final message proof that the task is complete?

What is a provider handoff?

Can several agents work in parallel?

Can the browser keep working when another chat is active?

Why did a browser action time out but still change the page?

What are automations?

What is Studio?

What is the Agent Gateway?

What is External MCP?

Can External MCP expose Orutta over the network?

Where should I start when something fails?

Are Orutta diagnostics safe to post publicly?

What information belongs in a bug report?

What is the difference between stable behavior and current main?

Still have a question?