Talking to other sessions.

If you have Nilux open in two projects, say a backend and a frontend, the two sessions can work together. Nilux in one project can ask the session in the other a question and get back the finished answer. You can also hand a running session a task from outside, for example from a script.

This works only between sessions of your own account, on the same computer and under the same system user.

Ask another session

Just tell Nilux what you need from the other project:

Nilux finds the other session and sends the question. The other session does the work and sends back only the answer. In the other session you see the incoming message on its own line, so it is clear what it is doing and for whom.

Nilux contacts other sessions only when you ask, or when the task is clearly about another project.

See the running sessions

This lists the other Nilux sessions running on this computer, each with its address (usually the project folder's name), folder, model and git branch.

Send a task from the terminal

• A session that is idle starts on the task right away; a busy one reads it at its next step.
• Nothing comes back to the command. The message goes one way, and you follow the result in that session.
• For a longer text, put it in a file and use --file, or pipe it in: cat task.md | nilux send my-app.
• --from sets the sender name shown in the other session, for example --from nightly-build.

There is a limit on how many messages can be sent per hour, so a script cannot flood your sessions.