Task session
Keep the started session identifier for subsequent checks.
Use cases · MCPENROUZ
AI process management through MCP
Builds, tests and long diagnostics can continue after the first tool response. MCPENROUZ lets you return to a session and retrieve the actual result.
Free2 devices · 100 tool calls per hour
Example task
On Linux dev, start the authorized project build as a long-running process. Read new output until completion and report the exit code.
Your device · your permissions
Incremental output
Read new lines as the task runs without repeating the entire output.
Verified completion
Check status and exit code before treating a task as complete.
Get started
Start a managed task
Allow terminal access and provide the command and working directory.
Track output
Ask AI to read session output and retain the next read position.
Finish or stop
Retrieve the final result. To stop, use the selected session’s controls.
Example task
A prompt for your AI
On Linux dev, start the authorized project build as a long-running process. Read new output until completion and report the exit code.
Permissions
Starting commands requires shell access. Listing or terminating arbitrary OS processes needs separate local permissions.
Details
Managed and OS processes
A MCPENROUZ session and an arbitrary OS process have different controls. Choose the tool for the specific task.
Retain the result
After starting, wait for completion or keep session details to continue. Starting does not mean a build succeeded.
Frequently asked questions
Can I terminate any process?
Only within OS rights and enabled permissions. OS process termination needs separate access.
Why is a task still running?
Check new output and session state. Some commands start a persistent server.
Where does the process run?
On the selected connected device under its agent account.
Next steps
MCPENROUZ · FREE
Connect a device. Start with reads.
Choose a working folder and AI client. Add writes and terminal access as your task requires.