Bug Description
I am testing nanobot so to be enough reliable for me to use for my work, and I have assigned it the task to draft daily a short article for me to post on X, and I told it to save the draft into a file named "draft_x_post.txt" which was supposed to be saved inside its workspace, but for some reason it created a directory named "workspace" and saved the file inside that directory. Then I told it to save the file inside its root level (the root level of the actual .nanobot/workspace dir), and it reported being unable to reach that location.
Steps to Reproduce
- Ask to "Generate a daily X post rotating between the following topics: AI, web dev, SEO, music production, game dev, integrations. Then use the humanizer skill, save the draft into a "draft_x_post.txt" file, and send me a draft for review"
Expected Behavior
It should have saved the file at the workspace root level, instead it created a sub-workspace directory and saved the file inside there. Then it declared it couldn't reach the root level of workspace (see below)
Relevant Logs
nanobot Version
0.1.5 post3
Python Version
3.13
Operating System
Linux
Channel / Platform
Telegram
LLM Provider
Other (specify below)
Configuration (Optional)
Grok 4.1 fast non-reasoning
Additional Context
After my request, it generated the following job prompt: "Generate daily X post: Check rotation from memory (AI→web dev→SEO→music prod→game dev→integrations). Use web_search for cutting-edge trend. Draft 150-250 words, VERY PROFESSIONAL, no pitches/URLs/CTAs. Humanize with humanizer skill (strict: no em dashes). Write final draft to workspace/draft_x_post.txt. Verify write: exec 'ls -la workspace/draft_x_post.txt', confirm 'updated today' in message with timestamp. Message the draft here for review in chat -5248477503. If user says POST (exact), post via x-api skill and confirm. Rotate topic. Log post date/URL to memory."
Then I asked it to save the file at the root level of the workspace, not inside an additional "workspace" directory, and it replied: "MCP tools can't see it—path safety limits to /home/[my_user]/.nanobot/workspace.
I also asked it to verify the location of a file I wrote myself at the root level, and it replied: "Root draft_x_post.txt exists but can't access directly (safety guard blocks ls -la draft_x_post.txt)"
Bug Description
I am testing nanobot so to be enough reliable for me to use for my work, and I have assigned it the task to draft daily a short article for me to post on X, and I told it to save the draft into a file named "draft_x_post.txt" which was supposed to be saved inside its workspace, but for some reason it created a directory named "workspace" and saved the file inside that directory. Then I told it to save the file inside its root level (the root level of the actual .nanobot/workspace dir), and it reported being unable to reach that location.
Steps to Reproduce
Expected Behavior
It should have saved the file at the workspace root level, instead it created a sub-workspace directory and saved the file inside there. Then it declared it couldn't reach the root level of workspace (see below)
Relevant Logs
nanobot Version
0.1.5 post3
Python Version
3.13
Operating System
Linux
Channel / Platform
Telegram
LLM Provider
Other (specify below)
Configuration (Optional)
Grok 4.1 fast non-reasoningAdditional Context
After my request, it generated the following job prompt: "Generate daily X post: Check rotation from memory (AI→web dev→SEO→music prod→game dev→integrations). Use web_search for cutting-edge trend. Draft 150-250 words, VERY PROFESSIONAL, no pitches/URLs/CTAs. Humanize with humanizer skill (strict: no em dashes). Write final draft to workspace/draft_x_post.txt. Verify write: exec 'ls -la workspace/draft_x_post.txt', confirm 'updated today' in message with timestamp. Message the draft here for review in chat -5248477503. If user says POST (exact), post via x-api skill and confirm. Rotate topic. Log post date/URL to memory."
Then I asked it to save the file at the root level of the workspace, not inside an additional "workspace" directory, and it replied: "MCP tools can't see it—path safety limits to /home/[my_user]/.nanobot/workspace.
I also asked it to verify the location of a file I wrote myself at the root level, and it replied: "Root draft_x_post.txt exists but can't access directly (safety guard blocks ls -la draft_x_post.txt)"