Computer commands and files
Found this helpful? Share it:
Found this helpful? Share it:
Every paired computer supports command execution through the daemon and a visual file browser. Run commands, navigate folders, edit files, and search content without leaving the app 💻
idapt sends a signed command to the paired daemon, and the daemon runs it locally as an allowed Unix user. Output streams back into the app as it runs.
Commands run only as the Unix users the computer allows, so a command can never do more than those accounts can. Pass a specific user when a task needs a particular account, otherwise the computer's default user is used.
Tmux gives an agent a persistent shell session for long-running work. The daemon runs tmux commands on the computer and returns structured captures, so a task can keep state across several commands, run background processes, and capture output later.
For one-shot commands, use normal command execution.
During a conversation the AI can run commands on your computers and read the output. Ask it to check logs, restart a service, run a build, or debug an issue, and it runs the commands and reports back.
The AI acts under the same run-as rules you do. It can only act as Unix users the computer allows, and never beyond what those accounts can do.
Click the Files tab on any computer to open the file browser. Navigate the remote file system by clicking through folders, just like a desktop file manager, and select a file to preview it. Text, configuration, log, and code files display with syntax highlighting.
The browser supports full file management through the daemon:
Read and edit file contents.
Create new files and folders.
Move and rename files.
Delete files and folders.
Every change happens directly on the remote computer, so what you see is the live state of the file system.
You can move files between your idapt Drive and a computer. Transfers stream through idapt's servers, so you do not need to open any port on the computer or copy files by hand.
Search a computer's files to find what you need quickly. Search by file name or within file contents, like running grep but with structured, easy-to-read results. The AI can search too, when it needs to find specific code, logs, or configuration.
Each computer has a logging level that sets how much of a run is kept. At the full level, idapt stores each command with its exit code and its output, so you can open the execution history and see exactly what happened and when. At the minimal level, no command output is stored, so the history shows that a command ran but not what it printed.
Raise the level when you want a complete record for debugging or auditing, and lower it when you would rather keep less on hand. If a computer stops responding, see Daemon troubleshooting.
Related articles
Computers
Pair your own machine or launch a cloud one, then let your AI run commands and work with files on it.
Cloud computers
Launch an on-demand cloud machine, understand what it costs per second, and suspend it when you're done.
Daemon troubleshooting
What to do when a paired computer goes offline, fails an update, blocks a capability, or won't reconnect.
Was this helpful?