Skip to content

Conversation

ashleyhindle
Copy link
Collaborator

@ashleyhindle ashleyhindle commented Aug 28, 2025

What & Why

  • Default process isolation to true - this gives the best experience and is stable
  • Adds tests to ensure process isolation works as expected

How I tested

Claude Code

These all worked as expected

Does the list-artisan-commands tool see new tools?

Can you help me debug an issue with the boost MCP? this requires a couple steps:

  1. Call list artisan commands, take note of them
  2. Add a new artisan command
  3. Call list artisan commands, see if it shows the new command
  4. Remove the artisan command
  5. Call list artisan commands, see if it's gone

Does the tinker tool see new classes?

Now I need to test the 'tinker' tool

  1. Create a new helper class with a static function that returns a string
  2. Use tinker to var_dump that class's static function return                                                                                                                                                                   This should verify if tinker has access to new code and isn't using cached bytecode right?

Does the tinker tool see new methods?

Let's test the 'tinker' tool again to see if it detects new methods.
1. Create a new helper class with a method that returns a string
2. Use tinker to var_dump the method's return
3. Update the helper class to change the method name and string returned
4. Use tinker to var_dump using new method name, verify it succeeds & the string is different

Does list env/config see new env and config values?

Let's test the list env and list config tools:
1. List config & env vars, keep a note of them
2. Use a shell tool to append a new ENV var to .env
3. Create a new config file with a config value that uses the new ENV var, with a very different default if it doesn't exist
4. Call list config & env vars
5. Does our new env key show up?
6. Does our new config key show up?
7. Is the config value the value from .env?

Notes/thoughts

  • I'd like the tests to be cleaner soon, but I'm glad they're there and showing it working

@ashleyhindle ashleyhindle marked this pull request as ready for review August 28, 2025 09:16
Don't pass env vars to tool executor from long running parent process, force child to get own env
@ashleyhindle ashleyhindle merged commit c2ac67c into main Aug 28, 2025
10 checks passed
@ashleyhindle ashleyhindle deleted the detect-env-changes-130 branch August 28, 2025 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Boost doesn't detect environment changes
2 participants